Lines Matching full:command
35 name: Descriptive name that explains the command under test
41 dependsOn: Same as 'skip', but the value is executed as a command. The test
42 is skipped when the command returns non-zero.
43 category: A list of single-word descriptions covering what the command
45 setup: The list of commands required to ensure the command under test
46 succeeds. For example: if testing a filter, the command to create
49 Each command can be a string to be executed, or a list consisting
50 of a string which is a command to be executed, followed by 1 or
51 more acceptable exit codes for this command.
52 If only a string is given for the command, then an exit code of 0
54 cmdUnderTest: The tc command being tested itself.
55 expExitCode: The code returned by the command under test upon its termination.
57 verifyCmd: The tc command to be run to verify successful execution.
58 For example: if the command under test creates a gact action,
61 verifyCmd to prove the command under test succeeded. This pattern
70 Each command can be a string to be executed, or a list consisting
71 of a string which is a command to be executed, followed by 1 or
72 more acceptable exit codes for this command.
73 If only a string is given for the command, then an exit code of 0
89 It's possible to include acceptable exit codes with the setup/teardown command
91 individual command into a list, with the command being first, followed by all
92 acceptable exit codes for the command.