Lines Matching full:command
35 name: Descriptive name that explains the command under test
41 category: A list of single-word descriptions covering what the command
43 setup: The list of commands required to ensure the command under test
44 succeeds. For example: if testing a filter, the command to create
47 Each command can be a string to be executed, or a list consisting
48 of a string which is a command to be executed, followed by 1 or
49 more acceptable exit codes for this command.
50 If only a string is given for the command, then an exit code of 0
52 cmdUnderTest: The tc command being tested itself.
53 expExitCode: The code returned by the command under test upon its termination.
55 verifyCmd: The tc command to be run to verify successful execution.
56 For example: if the command under test creates a gact action,
59 verifyCmd to prove the command under test succeeded. This pattern
68 Each command can be a string to be executed, or a list consisting
69 of a string which is a command to be executed, followed by 1 or
70 more acceptable exit codes for this command.
71 If only a string is given for the command, then an exit code of 0
87 It's possible to include acceptable exit codes with the setup/teardown command
89 individual command into a list, with the command being first, followed by all
90 acceptable exit codes for the command.