Lines Matching full:test

33 .Nd Test suite description files
49 A test suite is a collection of test programs and is represented by a
50 hierarchical layout of test binaries on the file system.
51 Any subtree of the file system can represent a test suite, provided that it
54 which are the test suite definition files.
58 is a Lua script whose purpose is to describe the structure of the test
79 .Ss Test suite definition
82 registers any test programs,
85 must define the name of the test suite the test programs belong to by using the
89 The test suite name provided in the
95 to pass to the test programs at run time.
96 .Ss Test program registration
99 can register test programs by means of a variety of
101 functions, all of which take the name of a test program and a set of
102 optional metadata properties that describe such test program.
104 The test programs to be registered must live in the current directory; in
107 calls cannot reference test programs in other directories.
112 .Em ATF test programs
121 of the test program and a collection of optional metadata settings for all
122 the test cases in the test program.
123 Any metadata properties defined by the test cases themselves override the
127 .Em Plain test programs
128 are those that return 0 on success and non-0 on failure; in general, most test
130 thus also qualify as plain test programs.
136 of the test program, an optional
138 name that overrides the global test suite name, and a collection of optional
139 metadata settings for the test program.
141 .Em TAP test programs
142 are those that implement the Test Anything Protocol.
148 of the test program and a collection of optional metadata settings for the
149 test program.
151 The following metadata properties can be passed to any test program definition:
154 Whitespace-separated list of machine architecture names allowed by the test.
155 If empty or not defined, the test is allowed to run on any machine
161 Whitespace-separated list of machine platform names allowed by the test.
162 If empty or not defined, the test is allowed to run on any machine
168 Custom variable defined by the test where
185 Textual description of the test.
190 The name of the execution environment to be used for running the test.
197 The default environment which runs the test as a usual child process.
203 It creates a temporary jail to run the test and its optional cleanup logic
220 Otherwise, such aspects as parallel test execution and sub-jails spawned
221 by specific test cases should be considered.
226 .Va test program path
230 .Va test case name .
234 is an example for /usr/tests/sys/netpfil/pf/pass_block:v4 test case.
240 Additional test-specific whitespace-separated parameters of
243 to create a temporary jail within which the test is run.
265 If true, indicates that this test program cannot be executed along any other
267 Test programs that affect global system state, such as those that modify the
277 Whitespace-separated list of configuration variables that the test requires
283 Amount of available disk space that the test needs to run successfully.
287 Whitespace-separated list of paths that the test requires to exist before
293 Amount of physical memory that the test needs to run successfully.
299 binaries that the test requires to exist before it can run.
304 If empty, the test has no restrictions on the calling user for it to run.
307 the test needs to not run as root.
310 the test must run as root.
315 Amount of seconds that the test is allowed to execute before being killed.
321 To reference test programs in another subdirectory, a different
333 test suite definition.
334 Therefore, each subdirectory in a test suite must include its own
359 in a test suite: the user has to be able to run the test suite from any
363 Every system has a top directory into which test suites get installed.
366 Within this directory live test suites, each of which is in an independent
371 Kyua allows running all the installed test suites at once in order to
431 It provides a test suite definition and registers a couple of different test
443 It introduces some metadata properties to the test program definitions and
475 The following example configures the test to be run within a temporary jail
490 A test case itself may have no requirements in superuser privileges,
494 being running with root privileges, and the test is skipped otherwise with
505 .Ss Connecting disjoint test suites
506 Now suppose you had various test suites on your file system and you would
509 The test suites we would like to connect live under
530 file to drive the execution of the integrated test suite:
534 test_suite('test-all-the-things')