| README (228975) | README (263152) |
|---|---|
| 1$FreeBSD: head/tools/regression/README 228975 2011-12-30 00:04:11Z uqs $ | 1$FreeBSD: head/tools/regression/README 263152 2014-03-14 06:29:43Z glebius $ |
| 2 3This directory is for regression test programs. 4 5A regression test program is one that will exercise a particular bit of the 6system to check that we have not reintroduced an old bug. 7 8Tests should be implemented in files with a .t extension. Each .t file 9can contain more than one test, and can be implemented in any scripting --- 13 unchanged lines hidden (view full) --- 23 not ok n 24 25to indicate whether or not the test succeeded. 'n' is the test's number. 26Anything after this on the line (up to the first '#' if present) is 27considered to be the name of the test. Naming tests is optional, but 28encouraged. 29 30A test may be written which is conditional, and may need to be skipped. | 2 3This directory is for regression test programs. 4 5A regression test program is one that will exercise a particular bit of the 6system to check that we have not reintroduced an old bug. 7 8Tests should be implemented in files with a .t extension. Each .t file 9can contain more than one test, and can be implemented in any scripting --- 13 unchanged lines hidden (view full) --- 23 not ok n 24 25to indicate whether or not the test succeeded. 'n' is the test's number. 26Anything after this on the line (up to the first '#' if present) is 27considered to be the name of the test. Naming tests is optional, but 28encouraged. 29 30A test may be written which is conditional, and may need to be skipped. |
| 31For example, the netatalk tests require 'options NETATALK' in the kernel. | 31For example, the netinet tests require 'options INET' in the kernel. |
| 32A test may be skipped by printing '# skip Reason for skipping' after the 33test name. For example, 34 | 32A test may be skipped by printing '# skip Reason for skipping' after the 33test name. For example, 34 |
| 35 ok 1 - netatalk # skip 'options NETATALK' not compiled in | 35 ok 1 - netinet # skip 'options INET' not compiled in |
| 36 37A test may be flagged as 'todo'. This indicates that you expect the test 38to fail (perhaps because the necessary functionality hasn't been written 39yet). 'todo' tests are expected to fail, so when they start working the 40test framework can alert you to this happy occurrence. Flag these tests 41with a '# TODO' comment after the test name 42 43 not ok 1 - infiniteloop # TODO write test for an infinite loop --- 46 unchanged lines hidden --- | 36 37A test may be flagged as 'todo'. This indicates that you expect the test 38to fail (perhaps because the necessary functionality hasn't been written 39yet). 'todo' tests are expected to fail, so when they start working the 40test framework can alert you to this happy occurrence. Flag these tests 41with a '# TODO' comment after the test name 42 43 not ok 1 - infiniteloop # TODO write test for an infinite loop --- 46 unchanged lines hidden --- |