Lines Matching refs:command

35 name:         Descriptive name that explains the command under test
36 category:     A list of single-word descriptions covering what the command
38 setup:        The list of commands required to ensure the command under test
39               succeeds. For example: if testing a filter, the command to create
42 	      Each command can be a string to be executed, or a list consisting
43 	      of a string which is a command to be executed, followed by 1 or
44 	      more acceptable exit codes for this command.
45 	      If only a string is given for the command, then an exit code of 0
47 cmdUnderTest: The tc command being tested itself.
48 expExitCode:  The code returned by the command under test upon its termination.
50 verifyCmd:    The tc command to be run to verify successful execution.
51               For example: if the command under test creates a gact action,
54               verifyCmd to prove the command under test succeeded. This pattern
63 	      Each command can be a string to be executed, or a list consisting
64 	      of a string which is a command to be executed, followed by 1 or
65 	      more acceptable exit codes for this command.
66 	      If only a string is given for the command, then an exit code of 0
82 It's possible to include acceptable exit codes with the setup/teardown command
84 individual command into a list, with the command being first, followed by all
85 acceptable exit codes for the command.