app/test: update skipped count when setup returns skipped
PATCH 1/1 app/test: update skipped count when setup returns skipped
If the setup function returns TEST_SKIPPED, the logs would say the test case is skipped while the summary count would consider it under failed cases. Address this by counting such test cases under 'skipped'.
--- app/test/test.c | 2 ++ 1 file changed, 2 insertions(+)
app/test/test.c +2 -0
@@ -358,6 +358,8 @@ unit_test_suite_runner(struct unit_test_suite *suite) suite->failed++; }else if (test_success == -ENOTSUP ) { suite->unsupported++; + }else if (test_success ==TEST_SKIPPED ) { + suite->skipped++; }else { suite->failed++; }
Signature · 1 line
2.7.4
Quoted 7 lines
Subject: [PATCH] app/test: update skipped count when setup returns skipped
If the setup function returns
TEST_SKIPPED, the logs would say the test case is skipped while the summary count would consider it under failed cases. Address this by counting such test cases under 'skipped'.Signed-off-by Anoob Joseph <[email protected]>
Thomas Monjalon
Applied25/05/2022 08:10, Akhil Goyal:
Quoted 8 lines
Quoted 7 lines
Subject: [PATCH] app/test: update skipped count when setup returns skipped
If the setup function returns
TEST_SKIPPED, the logs would say the test case is skipped while the summary count would consider it under failed cases. Address this by counting such test cases under 'skipped'.Signed-off-by Anoob Joseph <[email protected]>Acked-by Akhil Goyal <[email protected]>
Applied, thanks.