Lines Matching full:test

29 .Nm atf-test-case
30 .Nd generic description of test cases
33 .Em test case
38 Given this, test cases are very fine-grained, but they attempt to group
41 A test case is defined by three components regardless of the language it is
46 properties to describe what the test case does and how it behaves.
47 In other words: it defines the test case's
54 is the test case itself.
55 It executes all actions needed to reproduce the test, and checks for
62 the exit status of the test case.
63 It can be used to undo side-effects of the test case.
64 Note that almost all side-effects of a test case are automatically cleaned
68 It is extremely important to keep the separation between a test case's
72 the header are met and when the user specifies that test case.
74 At last, test cases are always contained into test programs.
75 The test programs act as a front-end to them, providing a consistent
78 Upon termination, a test case reports a status and, optionally, a textual
79 reason describing why the test reported such status.
80 The caller must ensure that the test case really performed the task that its
81 status describes, as the test program may be bogus and therefore providing a
85 The possible exit status of a test case are one of the following:
88 The test case expects to terminate abruptly.
90 The test case expects to exit cleanly.
92 The test case expects to exit with a controller fatal/non-fatal failure.
93 If this happens, the test program exits with a success error code.
95 The test case expects to receive a signal that makes it terminate.
97 The test case expects to execute for longer than its timeout.
99 The test case was executed successfully.
100 The test program exits with a success error code.
102 The test case could not be executed because some preconditions were not
108 a message describing why the test was skipped.
109 The test program exits with a success error code.
111 An error appeared during the execution of the test case.
114 a message describing why the test failed.
115 The test program exits with a failure error code.
120 results comes when writing test cases that verify known failures caused,
124 result is trying to cover is fixed, then the test case will be reported as
132 to the caller; the caller must verify that the test case did actually terminate
135 Test cases are free to print whatever they want to their
142 This is specially important for long test cases.
144 Test cases will log their results to an auxiliary file, which is then
145 collected by the test program they are contained in.
147 APIs to implement the test cases.
149 The standard input of the test cases is unconditionally connected to
152 The following metadata properties can be exposed via the test case's head:
158 A brief textual description of the test case's purpose.
165 If set to true, specifies that the test case has a cleanup routine that has
167 This property is automatically set by the framework when defining a test case
173 The test case's identifier.
174 Must be unique inside the test program and should be short but descriptive.
179 A whitespace separated list of architectures that the test case can be run
186 to execute the test case.
187 If any of the required variables is not defined, the test case is
192 Specifies the minimum amount of available disk space needed by the test.
205 test case.
207 If any of the required files is not found, the test case is
213 A whitespace separated list of machine types that the test case can be run
218 Specifies the minimum amount of physical memory needed by the test.
231 the test case.
236 If any of the required programs is not found, the test case is
242 The required privileges to execute the test case.
248 If the test case is running as a regular user and this property is
250 the test case is
253 If the test case is running as root and this property is
257 configuration property is set; otherwise the test case is
264 Specifies the maximum amount of time the test case can run.
269 test program.
271 Can optionally be set to zero, in which case the test case has no run-time
281 be specified at will by the test case.
282 The runtime engine should propagate these properties from the test case to
283 the end user so that the end user can rely on custom properties for test case
287 Every time a test case is executed, several environment variables are
288 cleared or reseted to sane values to ensure they do not make the test fail
315 The test program always creates a temporary directory
316 and switches to it before running the test case's body.
317 This way the test case is free to modify its current directory as it
324 Test cases are always executed with a file creation mode mask (umask) of
326 The test case's code is free to change this during execution.
328 .Xr atf-test-program 1