Lines Matching refs:in
20 unit tests. See the config file in this directory for minimum required
23 * All tc-related features being tested must be built in or available as
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
31 handled in a future version - the current workaround is to run the tests
39 in the tdc_config.py file. Find the 'TC' entry in the NAMES dictionary and
57 network namespace and creates a veth pair which may be used in those test
66 tdc will list the test names as they are being run, and print a summary in
69 the failed test in the TAP output.
75 One run of tests is considered a "test suite" (this will be refined in the
76 future). A test suite has one or more test cases in it.
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
112 your needs. Any value in the NAMES dictionary can be altered without affecting
113 the tests to be run. These values are used in the tc commands that will be
119 The NAMES values are used to substitute into the commands in the test cases.
131 was in the tdc.py script has been moved into the plugins.
133 The plugins are in the directory plugin-lib. The are executed from
146 The plugins are a subclass of TdcPlugin, defined in TdcPlugin.py and
148 distinguished from each other in the python program by their module
156 adjust-command (runs in all stages and receives the stage name)
159 This allows you to dump out the list of skipped tests in the event of a
178 To write a plugin, you need to inherit from TdcPlugin in
180 implementation file in plugin-lib, and add a symbolic link to it from
182 appropriate times. There are a few examples in the plugin-lib
188 sets up a network namespace and runs all commands in that namespace,
189 while also setting up dummy devices to be used in testing.
191 runs each command in the execute stage under valgrind,
193 This plugin will output an extra test for each test in the test file,
208 Netdev 1.2 Tokyo in October 2016.