- Timestamp:
- Dec 12, 2008, 10:09:19 PM (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/test/README
r1641 r1642 66 66 typical usage. 67 67 68 69 70 68 Tests shall return 0 at success and -1 otherwise (see 69 test::Suite::return_value()). If the test should be skipped for some 70 reason it shall return 77. 71 71 72 72 When a test is run without verbose flag, it should be silent also at … … 74 74 test::Suite class (see functions err() and out()). 75 75 76 If a test grows large, avoid having several tests in one long 77 main. It creates long correlations and complicates debugging and 78 extending the test. If you don't want to split the test into several 79 files, split the test into several independent sub-functions. 76 If a test needs a data file, place the data in directory 77 'test/data'. However, you should feel free to re-use the data files 78 already there. It should be possible to run test from any directory, 79 in particular from builddir in a VPATH build. To achieve this, use 80 test::Suite::filename() to get the absolute path to the file. 81 82 If a test grows large, avoid having several tests in one long 83 main. It creates long correlations and complicates debugging and 84 extending the test. If you don't want to split the test into several 85 files, split the test into several independent sub-functions. 80 86 81 87
Note: See TracChangeset
for help on using the changeset viewer.