Lines Matching +full:user +full:- +full:defined

29 .Nm atf-test-case
34 is a piece of code that stress-tests a specific feature of the software.
35 This feature is typically self-contained enough, either in the amount of
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
48 .Em meta-data ,
50 .Sx Meta-data
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
69 header and body well-defined, because the header is
71 parsed, whereas the body is only executed when the conditions defined in
72 the header are met and when the user specifies that test case.
75 The test programs act as a front-end to them, providing a consistent
76 interface to the user and several APIs to ease their implementation.
86 .Bl -tag -width expectedXfailureXX
92 The test case expects to exit with a controller fatal/non-fatal failure.
141 to keep the user informed of their actions.
151 .Ss Meta-data
153 .Bl -tag -width requireXmachineXX
159 Will be shown to the user in reports.
185 A whitespace separated list of configuration variables that must be defined
187 If any of the required variables is not defined, the test case is
233 user's
238 .It require.user
248 If the test case is running as a regular user and this property is
256 .Sq unprivileged-user
271 Can optionally be set to zero, in which case the test case has no run-time
274 .It X- Ns Sq NAME
278 A user-defined property named
283 the end user so that the end user can rely on custom properties for test case
291 .Bl -tag -width LCXMESSAGESXX
328 .Xr atf-test-program 1