Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
pike
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD 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
pikelang
pike
Commits
54a45ee2
Commit
54a45ee2
authored
22 years ago
by
Martin Nilsson
Browse files
Options
Downloads
Patches
Plain Diff
Content
Rev: refdoc/chapters/testsuite.xml:1.11
parent
1230adb7
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
refdoc/chapters/testsuite.xml
+52
-27
52 additions, 27 deletions
refdoc/chapters/testsuite.xml
with
52 additions
and
27 deletions
refdoc/chapters/testsuite.xml
+
52
−
27
View file @
54a45ee2
...
@@ -21,8 +21,13 @@
...
@@ -21,8 +21,13 @@
<dd>
Runs the test suite with the flags "
<tt>
-a -v
</tt>
", without
<dd>
Runs the test suite with the flags "
<tt>
-a -v
</tt>
", without
installing a new test Pike binary.
</dd>
installing a new test Pike binary.
</dd>
<dt>
testsuites
</dt>
<dd>
Creates testsuite files in the build tree from the
testsuite.in-files in the src/ and lib/ trees.
</dd>
<dt>
verify
</dt>
<dt>
verify
</dt>
<dd>
Runs the
<tt>
tinstall
</tt>
and
<tt>
just_verify
</tt>
targets.
</dd>
<dd>
Runs the
<tt>
testsuites
</tt>
,
<tt>
tinstall
</tt>
and
<tt>
just_verify
</tt>
targets.
</dd>
<dt>
verify_installed
</dt>
<dt>
verify_installed
</dt>
<dd>
Runs the test suit with the flags "
<tt>
-a -v
</tt>
", with the
<dd>
Runs the test suit with the flags "
<tt>
-a -v
</tt>
", with the
...
@@ -39,14 +44,14 @@
...
@@ -39,14 +44,14 @@
suite with the flags "
<tt>
-v -v -a
</tt>
".
</dd>
suite with the flags "
<tt>
-v -v -a
</tt>
".
</dd>
<dt>
gdb_verify
</dt>
<dt>
gdb_verify
</dt>
<dd>
Runs the test suite inside of gdb. The test suite is started
<dd>
Runs the test suite inside of gdb. The test suite is started
with the flags "
<tt>
-v -v -a
</tt>
".
</dd>
with the flags "
<tt>
-v -v -a
</tt>
".
</dd>
</dl>
</dl>
<p>
It is possible to alter the flags given to the
<p>
It is possible to alter the flags given to the
<tt>
test_install
</tt>
program by using the
<tt>
TESTARGS
</tt>
make variable.
</p>
<tt>
test_install
</tt>
program by using the
<tt>
TESTARGS
</tt>
make
variable.
</p>
<example>
<example>
make verify TESTARGS="-a -v4 -l2 -t1 -c1 -m"
make verify TESTARGS="-a -v4 -l2 -t1 -c1 -m"
...
@@ -74,9 +79,10 @@ make verify TESTARGS="-a -v4 -l2 -t1 -c1 -m"
...
@@ -74,9 +79,10 @@ make verify TESTARGS="-a -v4 -l2 -t1 -c1 -m"
make testsuites
make testsuites
</example>
</example>
<p>
The testsuite files have now appeared in build/
<i>
arch
</i>
in locations
<p>
The testsuite files have now appeared in build/
<i>
arch
</i>
in
corresponding to where they lived in the pike tree, except those from the lib/
locations corresponding to where they lived in the pike tree, except
hierarchy; those end up in build/
<i>
arch
</i>
/tlib.
</p>
those from the lib/ hierarchy; those end up in
build/
<i>
arch
</i>
/tlib.
</p>
<p>
The test_pike.pike program takes the following attributes.
</p>
<p>
The test_pike.pike program takes the following attributes.
</p>
...
@@ -173,27 +179,46 @@ Total tests: 1 (0 tests skipped)
...
@@ -173,27 +179,46 @@ Total tests: 1 (0 tests skipped)
</pre>
</pre>
</dd>
</dd>
<!--
<dt>
-p, --prompt
</dt>
-p, --prompt The user will be asked before every test is run.
<dd>
The user will be asked before every test is run.
</dd>
-sX, --start-test=X Where in the testsuite testing should start, e.g. ignores X
tests in every testsuite.
<dt>
-sX, --start-test=X
</dt>
-eX, --end-after=X How many tests should be run.
<dd>
Where in the testsuite testing should start, e.g. ignores X
-f, --fail If set, the testsuite always fails.
tests in every testsuite.
</dd>
-lX, --loop=X The number of times the testsuite should be run. Default is
1.
<dt>
-eX, --end-after=X
</dt>
-tX, --trace=X Run tests with trace level X.
<dd>
How many tests should be run.
</dd>
-c[X], --check[=X] The level of extra pike consistency checks performed.
1 _verify_internals is run before every test.
<dt>
-f, --fail
</dt>
2 _verify_internals is run after every compilation.
<dd>
If set, the test program exits on first failure.
</dd>
3 _verify_internals is run after every test.
4 An extra gc and _verify_internals is run before
<dt>
-lX, --loop=X
</dt>
every test.
<dd>
The number of times the testsuite should be run. Default is 1.
</dd>
X<0 For values below zero, _verify_internals will be run
before every n:th test, where n=abs(X).
<dt>
-tX, --trace=X
</dt>
-m, --mem, --memory Print out memory allocations after the tests.
<dd>
Run tests with trace level X.
</dd>
-T, --notty Format output for non-tty.
-d, --debug Opens a debug port.
<dt>
-c[X], --check[=X]
</dt>
-->
<dd>
The level of extra pike consistency checks performed.
<matrix>
<r><c>
1
</c><c>
_verify_internals is run before every test.
</c></r>
<r><c>
2
</c><c>
_verify_internals is run after every compilation.
</c></r>
<r><c>
3
</c><c>
_verify_internals is run after every test.
</c></r>
<r><c>
4
</c><c>
An extra gc and _verify_internals is run before
every test.
</c></r>
<r><c>
X
<
0
</c><c>
For values below zero, _verify_internals will be run
before every n:th test, where n=abs(X).
</c></r>
</matrix>
</dd>
<dt>
-m, --mem, --memory
</dt>
<dd>
Prints out memory allocations after the tests.
</dd>
<dt>
-T, --notty
</dt>
<dd>
Format output for non-tty.
</dd>
<dt>
-d, --debug
</dt>
<dd>
Opens a debug port.
</dd>
</dl>
</dl>
...
...
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