Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
F
frama-c
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Container Registry
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
pub
frama-c
Commits
2e74a63b
Commit
2e74a63b
authored
4 years ago
by
Roma Auguste
Browse files
Options
Downloads
Patches
Plain Diff
dev manual: ptests: "plug-in" is not a valid plug-in name
parent
9eabb46f
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/developer/advance.tex
+8
-8
8 additions, 8 deletions
doc/developer/advance.tex
with
8 additions
and
8 deletions
doc/developer/advance.tex
+
8
−
8
View file @
2e74a63b
...
...
@@ -699,14 +699,14 @@ Ok = 16 of 16
sequences. These options are detailed in Section~
\ref
{
ptests:options
}
.
\begin{example}
If the code of plug-in
\texttt
{
plug
-
in
}
has changed, a typical sequence of tests
If the code of plug-in
\texttt
{
plugin
}
has changed, a typical sequence of tests
is the following one.
\begin{shell}
\$
./bin/ptests.opt plug
-
in
\$
./bin/ptests.opt -update plug
-
in
\$
./bin/ptests.opt plugin
\$
./bin/ptests.opt -update plugin
\$
make tests
\end{shell}
So we first run the tests suite corresponding to
\texttt
{
plug
-
in
}
in order to
So we first run the tests suite corresponding to
\texttt
{
plugin
}
in order to
display what tests have been modified by the changes. After checking the
displayed differences, we validate the changes by updating the
oracles
\index
{
Oracle
}
. Finally we run all the test suites
\index
{
Test!Suite
}
in
...
...
@@ -715,8 +715,8 @@ order to ensure that the changes do not break anything else in \framac.
\begin{example}
For adding a new test, the typical sequence of command is the following.
\begin{shell}
\$
./bin/ptests.opt -show tests/plug
-
in/new
_
test.c
\$
./bin/ptests.opt -update tests/plug
-
in/new
_
test.c
\$
./bin/ptests.opt -show tests/plugin/new
_
test.c
\$
./bin/ptests.opt -update tests/plugin/new
_
test.c
\$
make tests
\end{shell}
We first ask
\ptests
to print the output of the test on the command line, check
...
...
@@ -832,7 +832,7 @@ base. Common cases include:
This is possible with option
\texttt
{
-config
}
of
\ptests
, which takes as
argument the name of a special test configuration, as in
\begin{shell}
\$
./bin/ptests.opt -config <special
_
name> plug
-
in
\$
./bin/ptests.opt -config <special
_
name> plugin
\end{shell}
Then, the directives for this test can be found:
...
...
@@ -860,7 +860,7 @@ configuration: \lstinline+/* run.config* +.
All operations for this test configuration should take option
\texttt
{
-config
}
in argument, as in
\begin{shell}
\$
./bin/ptests.opt -update -config <special
_
name> plug
-
in
\$
./bin/ptests.opt -update -config <special
_
name> plugin
\end{shell}
\begin{important}
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment