Lines Matching refs:test

4  * running, result logging and clean up of a test suite, taking care
5 * of all the scaffolding. A test suite is a sequence of very targeted
8 * A unit test is abstracted as a unit_test_t structure, consisting of
9 * a test function and a logging identifier. A test suite is a suite_t
12 * Test suites are created dynamically. Each of its unit test runs in
14 * running before and after each test. The parent process will log a
17 * results are then aggregated and logged, and finally the test suite
22 * flexibility. In our particular case, a unit test is logged as a
23 * Testbot Test Case ([BEGIN]/[PASS]/[FAIL], and a test suite is
27 * The included test suites cover the various pipe buffer operations
60 /* Type for test, fixture set up and fixture tear down functions. */
63 /* Unit test structure. */
66 test_fn_t test;
103 /* Individual test result logging. */
160 /* Handler for test time out. */
168 /* Run a test with fixture set up and teardown, while enforcing the
182 unit_test->test();
219 /* Run a test in its own process, and report the result. */
239 /* Run each test in a suite, and report the results. */
328 /* Setters and getters for various test framework global
329 * variables. Should only be used outside of the test, set up and tear
332 /* Time out constraint for running a single test. */
343 /* Expected signal for a test, default is 0. */
494 /* Arrays for test suite loops */
669 /* Pipes unit test functions */
846 { "9. test moving data " ,test_pipe_moving_data }
852 do_nothing, "pipe create base test "