linux/tools/testing/kunit/test_data/test_skip_tests.log

TAP version 14
1..2
    # Subtest: string-stream-test
    1..3
    ok 1 - string_stream_test_empty_on_creation
    ok 2 - string_stream_test_not_empty_after_add
    ok 3 - string_stream_test_get_string
ok 1 - string-stream-test
    # Subtest: example
    1..2
    # example_simple_test: initializing
    ok 1 - example_simple_test
    # example_skip_test: initializing
    ok 2 - example_skip_test # SKIP this test should be skipped
ok 2 - example
kunit: tool: Support skipped tests in kunit_tool Add support for the SKIP directive to kunit_tool's TAP parser. Skipped tests now show up as such in the printed summary. The number of skipped tests is counted, and if all tests in a suite are skipped, the suite is also marked as skipped. Otherwise, skipped tests do affect the suite result. Example output: [00:22:34] ======== [SKIPPED] example_skip ======== [00:22:34] [SKIPPED] example_skip_test # SKIP this test should be skipped [00:22:34] [SKIPPED] example_mark_skipped_test # SKIP this test should be skipped [00:22:34] ============================================================ [00:22:34] Testing complete. 2 tests run. 0 failed. 0 crashed. 2 skipped. Signed-off-by: David Gow <davidgow@google.com> Reviewed-by: Daniel Latypov <dlatypov@google.com> Reviewed-by: Brendan Higgins <brendanhiggins@google.com> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org> 2021-06-24 23:58:13 -07:00			`TAP version 14`
			`1..2`
			`# Subtest: string-stream-test`
			`1..3`
			`ok 1 - string_stream_test_empty_on_creation`
			`ok 2 - string_stream_test_not_empty_after_add`
			`ok 3 - string_stream_test_get_string`
			`ok 1 - string-stream-test`
			`# Subtest: example`
			`1..2`
			`# example_simple_test: initializing`
			`ok 1 - example_simple_test`
			`# example_skip_test: initializing`
			`ok 2 - example_skip_test # SKIP this test should be skipped`
			`ok 2 - example`