diff options
| author | Lucas Bates <lucasb@mojatatu.com> | 2019-02-28 17:38:40 -0500 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2019-03-01 23:05:06 -0800 |
| commit | 255c1c7279abf991113e7c9c29f91e9f1a5776a9 (patch) | |
| tree | 4f6240e2b26aebed6b08666983290e33b345761c /tools/testing/selftests/tc-testing/creating-testcases/AddingTestCases.txt | |
| parent | 745732c8ecf89ad60f7e393094d4993284bd1869 (diff) | |
tc-testing: Allow test cases to be skipped
By adding a check for an optional key/value pair to the test case
data, individual test cases may be skipped to prevent tdc from
aborting a test run due to setup or teardown failure.
If a test case is skipped, it will still appear in the results
output to allow for a consistent number of executed tests in each
run. However, the test will be marked as skipped.
This support for skipping extends to any plugins that may generate
additional results for each executed test.
Signed-off-by: Lucas Bates <lucasb@mojatatu.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/testing/selftests/tc-testing/creating-testcases/AddingTestCases.txt')
| -rw-r--r-- | tools/testing/selftests/tc-testing/creating-testcases/AddingTestCases.txt | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/tools/testing/selftests/tc-testing/creating-testcases/AddingTestCases.txt b/tools/testing/selftests/tc-testing/creating-testcases/AddingTestCases.txt index 17b267dedbd9..a28571aff0e1 100644 --- a/tools/testing/selftests/tc-testing/creating-testcases/AddingTestCases.txt +++ b/tools/testing/selftests/tc-testing/creating-testcases/AddingTestCases.txt @@ -33,6 +33,11 @@ Each test case has required data: id: A unique alphanumeric value to identify a particular test case name: Descriptive name that explains the command under test +skip: A completely optional key, if the corresponding value is "yes" + then tdc will not execute the test case in question. However, + this test case will still appear in the results output but + marked as skipped. This key can be placed anywhere inside the + test case at the top level. category: A list of single-word descriptions covering what the command under test is testing. Example: filter, actions, u32, gact, etc. setup: The list of commands required to ensure the command under test |