Lines Matching +full:use +full:- +full:cases
1 tdc - Linux Traffic Control (tc) unit testing suite
3 Author: Lucas Bates - lucasb@mojatatu.com
10 ------------
24 * All tc-related features being tested must be built in or available as
26 ./tdc.py -c
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
37 --------------
44 using the -p option when running tdc:
45 ./tdc.py -p /path/to/tc
49 -----------
51 To use tdc, root privileges are required. This is because the
56 Tests that use a network device should have nsPlugin.py listed as a
59 cases. To disable execution within the namespace, pass the -N option
65 ./tdc.py -h
74 -------------------------
77 future). A test suite has one or more test cases in it.
81 - setup
82 - execute
83 - verify
84 - teardown
100 USER-DEFINED CONSTANTS
101 ----------------------
106 executed as part of the test. More will be added as test cases require.
111 The NAMES values are used to substitute into the commands in the test cases.
115 ----------------------
117 Run tdc.py -h to see the full list of available arguments.
119 usage: tdc.py [-h] [-p PATH] [-D DIR [DIR ...]] [-f FILE [FILE ...]]
120 [-c [CATG [CATG ...]]] [-e ID [ID ...]] [-l] [-s] [-i] [-v] [-N]
121 [-d DEVICE] [-P] [-n] [-V]
126 -h, --help show this help message and exit
127 -p PATH, --path PATH The full path to the tc executable to use
128 -v, --verbose Show the commands that are being run
129 -N, --notap Suppress tap results for command under test
130 -d DEVICE, --device DEVICE
131 Execute test cases that use a physical device, where
134 -P, --pause Pause execution just before post-suite stage
137 select which test cases: files plus directories; filtered by categories
140 -D DIR [DIR ...], --directory DIR [DIR ...]
142 (default [tc-tests])
143 -f FILE [FILE ...], --file FILE [FILE ...]
145 -c [CATG [CATG ...]], --category [CATG [CATG ...]]
149 -e ID [ID ...], --execute ID [ID ...]
150 Execute the specified test cases with specified IDs
153 select action to perform on selected test cases
155 -l, --list List all test cases, or those only within the
157 -s, --show Display the selected test cases
158 -i, --id Generate ID numbers for new test cases
163 -N, --no-namespace
169 -V, --valgrind Run commands under valgrind
173 -------------------
178 The plugins are in the directory plugin-lib. The are executed from
179 directory plugins. Put symbolic links from plugins to plugin-lib,
185 bjb@bee:~/work/tc-testing$ ls -l plugins
187 lrwxrwxrwx 1 bjb bjb 27 Oct 4 16:12 10-rootPlugin.py -> ../plugin-lib/rootPlugin.py
188 lrwxrwxrwx 1 bjb bjb 25 Oct 12 17:55 20-nsPlugin.py -> ../plugin-lib/nsPlugin.py
189 -rwxr-xr-x 1 bjb bjb 0 Sep 29 15:56 __init__.py
198 pre- and post-suite
199 pre- and post-case
200 pre- and post-execute stage
201 adjust-command (runs in all stages and receives the stage name)
203 The pre-suite hook receives the number of tests and an array of test ids.
207 The pre-case hook receives the ordinal number and test id of the current test.
209 The adjust-command hook receives the stage id (see list below) and the
210 full command to be executed. This allows for last-minute adjustment
215 - pre (pre-suite)
216 - setup
217 - command
218 - verify
219 - teardown
220 - post (post-suite)
224 TdcPlugin.py. To use the plugin, you have to put the
225 implementation file in plugin-lib, and add a symbolic link to it from
227 appropriate times. There are a few examples in the plugin-lib
230 - rootPlugin.py:
232 - nsPlugin.py:
235 - valgrindPlugin.py
243 - buildebpfPlugin.py:
248 ----------------
252 Jamal Hadi Salim, for providing valuable test cases