Lines Matching refs:test
4 Sparse has a number of test cases in its validation directory. The test-suite
6 embedding tags in C comments in the test cases.
13 Name of the test. This is the only mandatory tag.
17 A description of what the test checks.
24 run the test-case.
33 Ignore the test if the current architecture (as returned by ``uname -m``)
38 Ignore the test if the given condition is false when evaluated as a
43 Ignore the test if the given condition is false when evaluated
68 Mark the test as being known to fail.
91 Using test-suite
94 The test-suite script is called through the check target of the Makefile. It
95 will try to check every test case it finds (``find validation -name '*.c'``).
96 It can be called to check a single test with::
99 $ ./test-suite single preprocessor/preprocessor1.c
104 Writing a test
107 The test-suite comes with a format command to make a test easier to write::
109 test-suite format [-a] [-l] [-f] file [name [cmd]]
117 The output of the test-suite format command can be redirected into the
118 test case to create a test-suite formatted file.::
120 $ ./test-suite format bad-assignment.c Assignment >> bad-assignment.c
138 You can define the check-command you want to use for the test.::
140 $ ./test-suite format -a validation/preprocessor2.c "Preprocessor #2" \