Lines Matching full:run
20 * The kernel must have the appropriate infrastructure enabled to run all tdc
25 modules. To check what is required in current setup run:
29 In the current release, tdc run will abort due to a failure in setup or
30 teardown commands - which includes not being able to run a test simply
32 handled in a future version - the current workaround is to run the tests
36 BEFORE YOU RUN
52 commands being tested must be run as root. The code that enforces
60 to tdc when starting a test run; the veth pair will still be created
63 Running tdc without any arguments will run all tests. Refer to the section
64 on command line arguments for more information, or run:
67 tdc will list the test names as they are being run, and print a summary in
76 One run of tests is considered a "test suite" (this will be refined in the
86 The setup and teardown stages can run zero or more commands. The setup
89 can be run next. These two stages require any commands run to return
92 The execute and verify stages each run one command. The execute stage
97 Each of the commands in any stage will run in a shell instance.
105 the tests to be run. These values are used in the tc commands that will be
117 Run tdc.py -h to see the full list of available arguments.
128 -v, --verbose Show the commands that are being run
144 Run tests from the specified file(s)
146 Run tests only from the specified category/ies, or if
161 options for nsPlugin (run commands in net namespace)
164 Do not run commands in a network namespace.
167 options for valgrindPlugin (run command under test under Valgrind)
169 -V, --valgrind Run commands under valgrind
180 and name them according to the order you want them to run. This is not
181 necessary if a test case being run requires a specific plugin to work.
196 This base class supplies "hooks" to run extra functions. These hooks are as follows:
226 plugins. It will be detected at run time and invoked at the