Lines Matching full:run

19 *  The kernel must have the appropriate infrastructure enabled to run all tdc
24    modules.  To check what is required in current setup run:
28    In the current release, tdc run will abort due to a failure in setup or
29    teardown commands - which includes not being able to run a test simply
31    handled in a future version - the current workaround is to run the tests
35 BEFORE YOU RUN
51 commands being tested must be run as root.  The code that enforces
59 to tdc when starting a test run; the veth pair will still be created
62 Running tdc without any arguments will run all tests. Refer to the section
63 on command line arguments for more information, or run:
66 tdc will list the test names as they are being run, and print a summary in
75 One run of tests is considered a "test suite" (this will be refined in the
85 The setup and teardown stages can run zero or more commands.  The setup
88 can be run next.  These two stages require any commands run to return
91 The execute and verify stages each run one command.  The execute stage
96 Each of the commands in any stage will run in a shell instance.
101 A test that runs inside a namespace (requires "nsPlugin") will run in parallel
104 Tests that use netdevsim or don't run inside a namespace run serially with regards
113 the tests to be run. These values are used in the tc commands that will be
125 Run tdc.py -h to see the full list of available arguments.
135 and name them according to the order you want them to run. This is not
136 necessary if a test case being run requires a specific plugin to work.
151 This base class supplies "hooks" to run extra functions.  These hooks are as follows:
181 plugins.  It will be detected at run time and invoked at the