linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
To: "Masahiro Yamada" <masahiroy@kernel.org>,
	"Nathan Chancellor" <nathan@kernel.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Willy Tarreau" <w@1wt.eu>,
	"Thomas Weißschuh" <linux@weissschuh.net>,
	"Brendan Higgins" <brendan.higgins@linux.dev>,
	"David Gow" <davidgow@google.com>, "Rae Moar" <rmoar@google.com>,
	"Shuah Khan" <shuah@kernel.org>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Nicolas Schier" <nicolas.schier@linux.dev>
Cc: "Christophe Leroy" <christophe.leroy@csgroup.eu>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
	linux-doc@vger.kernel.org,
	"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Subject: [PATCH v2 05/11] kunit: tool: Add test for nested test result reporting
Date: Mon, 07 Apr 2025 09:42:42 +0200	[thread overview]
Message-ID: <20250407-kunit-kselftests-v2-5-454114e287fd@linutronix.de> (raw)
In-Reply-To: <20250407-kunit-kselftests-v2-0-454114e287fd@linutronix.de>

Currently there is no test validating the result reporting from nested
tests. Add one, it will also be used to validate upcoming changes to the
nested test parsing.

Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
---
 tools/testing/kunit/kunit_tool_test.py                           | 9 +++++++++
 .../kunit/test_data/test_is_test_passed-failure-nested.log       | 7 +++++++
 2 files changed, 16 insertions(+)

diff --git a/tools/testing/kunit/kunit_tool_test.py b/tools/testing/kunit/kunit_tool_test.py
index 5ff4f6ffd8736de3fca17dd9fcceabd7a68f9f98..755dc24350a76306a5b76998646e56fb3e386232 100755
--- a/tools/testing/kunit/kunit_tool_test.py
+++ b/tools/testing/kunit/kunit_tool_test.py
@@ -165,6 +165,15 @@ class KUnitParserTest(unittest.TestCase):
 		self.assertEqual(kunit_parser.TestStatus.FAILURE, result.status)
 		self.assertEqual(result.counts.errors, 0)
 
+	def test_parse_failed_nested_tests_log(self):
+		nested_log = test_data_path('test_is_test_passed-failure-nested.log')
+		with open(nested_log) as file:
+			result = kunit_parser.parse_run_tests(file.readlines(), stdout)
+		self.assertEqual(kunit_parser.TestStatus.FAILURE, result.status)
+		self.assertEqual(result.counts.failed, 2)
+		self.assertEqual(kunit_parser.TestStatus.FAILURE, result.subtests[0].status)
+		self.assertEqual(kunit_parser.TestStatus.FAILURE, result.subtests[1].status)
+
 	def test_no_header(self):
 		empty_log = test_data_path('test_is_test_passed-no_tests_run_no_header.log')
 		with open(empty_log) as file:
diff --git a/tools/testing/kunit/test_data/test_is_test_passed-failure-nested.log b/tools/testing/kunit/test_data/test_is_test_passed-failure-nested.log
new file mode 100644
index 0000000000000000000000000000000000000000..835816e0a07715a514f5f5afab1b6250037feaf4
--- /dev/null
+++ b/tools/testing/kunit/test_data/test_is_test_passed-failure-nested.log
@@ -0,0 +1,7 @@
+KTAP version 1
+1..2
+not ok 1 subtest 1
+    KTAP version 1
+    1..1
+        not ok 1 test 1
+not ok 2 subtest 2

-- 
2.49.0


  parent reply	other threads:[~2025-04-07  7:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07  7:42 [PATCH v2 00/11] kunit: Introduce UAPI testing framework Thomas Weißschuh
2025-04-07  7:42 ` [PATCH v2 01/11] kbuild: userprogs: add nolibc support Thomas Weißschuh
2025-05-26 14:19   ` Nicolas Schier
2025-05-26 14:40     ` Thomas Weißschuh
2025-05-27 14:01       ` Nicolas Schier
2025-04-07  7:42 ` [PATCH v2 02/11] kbuild: introduce CONFIG_ARCH_HAS_NOLIBC Thomas Weißschuh
2025-05-26 14:20   ` Nicolas Schier
2025-04-07  7:42 ` [PATCH v2 03/11] kbuild: doc: add label for userprogs section Thomas Weißschuh
2025-04-07  7:42 ` [PATCH v2 04/11] kbuild: introduce blob framework Thomas Weißschuh
2025-05-26 14:21   ` Nicolas Schier
2025-04-07  7:42 ` Thomas Weißschuh [this message]
2025-04-07  7:42 ` [PATCH v2 06/11] kunit: tool: Don't overwrite test status based on subtest counts Thomas Weißschuh
2025-04-07  7:42 ` [PATCH v2 07/11] kunit: tool: Parse skipped tests from kselftest.h Thomas Weißschuh
2025-04-07  7:42 ` [PATCH v2 08/11] kunit: Introduce UAPI testing framework Thomas Weißschuh
2025-04-07  7:42 ` [PATCH v2 09/11] kunit: uapi: Add example for UAPI tests Thomas Weißschuh
2025-05-26 14:22   ` Nicolas Schier
2025-05-26 14:50     ` Thomas Weißschuh
2025-05-27 13:56       ` Nicolas Schier
2025-05-27 14:51         ` Thomas Weißschuh
2025-04-07  7:42 ` [PATCH v2 10/11] kunit: uapi: Introduce preinit executable Thomas Weißschuh
2025-05-26 14:22   ` Nicolas Schier
2025-04-07  7:42 ` [PATCH v2 11/11] kunit: uapi: Validate usability of /proc Thomas Weißschuh
2025-05-26 14:19 ` [PATCH v2 00/11] kunit: Introduce UAPI testing framework Nicolas Schier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250407-kunit-kselftests-v2-5-454114e287fd@linutronix.de \
    --to=thomas.weissschuh@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=brendan.higgins@linux.dev \
    --cc=christophe.leroy@csgroup.eu \
    --cc=corbet@lwn.net \
    --cc=davidgow@google.com \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --cc=nicolas.schier@linux.dev \
    --cc=rmoar@google.com \
    --cc=shuah@kernel.org \
    --cc=w@1wt.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).