Lines Matching refs:test
1 Guidelines for test developers
7 For any test that you want to perform, you write a script located in
8 `test/recipes/`, named `{nn}-test_{name}.t`,
12 Please note that if a test involves a new testing executable, you will need to
13 do some additions in test/build.info. Please refer to the section
14 ["Changes to test/build.info"](README.md#changes-to-testbuildinfo) below.
19 A test executable is named `test/{name}test.c`
21 A test recipe is named `test/recipes/{nn}-test_{name}.t`, where `{nn}` is a two
42 A recipe that just runs a test executable
51 simple_test("test_{name}", "{name}test", "{name}");
53 `{name}` is the unique name you have chosen for your test.
55 The second argument to `simple_test` is the test executable, and `simple_test`
56 expects it to be located in `test/`
61 A recipe that runs a more complex test
85 # test feature 1
90 # test feature 2
93 Changes to test/build.info
96 Whenever a new test involves a new test executable you need to do the
98 test):
102 * create a three line description of how to build the test, you will have
104 basic test framework:
110 Generic form of C test executables
117 int testresult = 0; /* Assume the test will fail */
120 observed = function(); /* Call the code under test */
124 testresult = 1; /* Mark the test case a success */
132 ADD_TEST(my_test); /* Add each test separately */
140 You should use the `TEST_xxx` macros provided by `testutil.h` to test all failure
158 Note that the test infrastructure automatically sets up all required environment
