Skip to contentSkip to conversation

app/test: update skipped count when setup returns skipped

PATCH Applied Anoob Joseph 3 participants 3 messages May 24, 2022 – Jun 7, 2022

lore
Share & tools
lore
#0 lore raw

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
index 5194131..f4d2854 100644
@@ -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
Acked-by on v1 1/1
#1 lore raw
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'.

#2 lore raw

25/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'.

Applied, thanks.