Lines Matching full:test

33 .Nm atf-test-case
34 .Nd generic description of test cases
37 .Em test case
42 Given this, test cases are very fine-grained, but they attempt to group
45 A test case is defined by three components regardless of the language it is
50 properties to describe what the test case does and how it behaves.
51 In other words: it defines the test case's
58 is the test case itself.
59 It executes all actions needed to reproduce the test, and checks for
66 the exit status of the test case.
67 It can be used to undo side-effects of the test case.
68 Note that almost all side-effects of a test case are automatically cleaned
72 It is extremely important to keep the separation between a test case's
76 the header are met and when the user specifies that test case.
78 At last, test cases are always contained into test programs.
79 The test programs act as a front-end to them, providing a consistent
82 Upon termination, a test case reports a status and, optionally, a textual
83 reason describing why the test reported such status.
84 The caller must ensure that the test case really performed the task that its
85 status describes, as the test program may be bogus and therefore providing a
89 The possible exit status of a test case are one of the following:
92 The test case expects to terminate abruptly.
94 The test case expects to exit cleanly.
96 The test case expects to exit with a controller fatal/non-fatal failure.
97 If this happens, the test program exits with a success error code.
99 The test case expects to receive a signal that makes it terminate.
101 The test case expects to execute for longer than its timeout.
103 The test case was executed successfully.
104 The test program exits with a success error code.
106 The test case could not be executed because some preconditions were not
112 a message describing why the test was skipped.
113 The test program exits with a success error code.
115 An error appeared during the execution of the test case.
118 a message describing why the test failed.
119 The test program exits with a failure error code.
124 results comes when writing test cases that verify known failures caused,
128 result is trying to cover is fixed, then the test case will be reported as
136 to the caller; the caller must verify that the test case did actually terminate
139 Test cases are free to print whatever they want to their
146 This is specially important for long test cases.
148 Test cases will log their results to an auxiliary file, which is then
149 collected by the test program they are contained in.
151 APIs to implement the test cases.
153 The standard input of the test cases is unconditionally connected to
156 The following meta-data properties can be exposed via the test case's head:
162 A brief textual description of the test case's purpose.
169 If set to true, specifies that the test case has a cleanup routine that has
173 This property is automatically set by the framework when defining a test case
179 The test case's identifier.
180 Must be unique inside the test program and should be short but descriptive.
185 A whitespace separated list of architectures that the test case can be run
192 to execute the test case.
193 If any of the required variables is not defined, the test case is
200 test case.
202 If any of the required files is not found, the test case is
208 A whitespace separated list of machine types that the test case can be run
213 Specifies the minimum amount of physical memory needed by the test.
226 the test case.
231 If any of the required programs is not found, the test case is
237 The required privileges to execute the test case.
243 If the test case is running as a regular user and this property is
245 the test case is
248 If the test case is running as root and this property is
253 configuration property is set; otherwise the test case is
260 Specifies the maximum amount of time the test case can run.
265 test program.
267 Can optionally be set to zero, in which case the test case has no run-time
277 be specified at will by the test case.
278 The runtime engine should propagate these properties from the test case to
279 the end user so that the end user can rely on custom properties for test case
283 Every time a test case is executed, several environment variables are
284 cleared or reseted to sane values to ensure they do not make the test fail
311 The test program always creates a temporary directory
312 and switches to it before running the test case's body.
313 This way the test case is free to modify its current directory as it
320 Test cases are always executed with a file creation mode mask (umask) of
322 The test case's code is free to change this during execution.
325 .Xr atf-test-program 1 ,