Lines Matching +refs:test +refs:fail

2 This directory is for regression test programs.
4 A regression test program is one that will exercise a particular bit of the
8 can contain more than one test, and can be implemented in any scripting
11 The test protocol is quite simple.  At its most basic, each .t file should, 
18 Each test should produce a single line of output.  This line should start
24 to indicate whether or not the test succeeded.  'n' is the test's number.
26 considered to be the name of the test.  Naming tests is optional, but 
29 A test may be written which is conditional, and may need to be skipped.
31 A test may be skipped by printing '# skip Reason for skipping' after the
32 test name.  For example,
36 A test may be flagged as 'todo'.  This indicates that you expect the test
37 to fail (perhaps because the necessary functionality hasn't been written
38 yet).  'todo' tests are expected to fail, so when they start working the
39 test framework can alert you to this happy occurrence.  Flag these tests 
40 with a '# TODO' comment after the test name
42     not ok 1 - infiniteloop # TODO write test for an infinite loop
61 utility resides in src/usr.bin/uuencode so its regression test resides in
65 CVS keywords in test data files, use a .in suffix for input files and
74 Please make a subdir per other regression test, and add a brief description to
81 pipe		Pipe code regression test
87 date		Date(1) + format string regression test