summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDaniel Latypov <dlatypov@google.com>2022-10-28 14:02:55 -0700
committerShuah Khan <skhan@linuxfoundation.org>2022-10-31 02:47:07 -0600
commit3ffdcf7e3b7dff04b055771c03c9646aa383cc1e (patch)
treed8b61357a879cce4a6a61c29072f7baa5ecd84f6
parent8f8b51f7d5c8bd3a89e7ea87aed2cdaa52ca5ba4 (diff)
downloadlinux-3ffdcf7e3b7dff04b055771c03c9646aa383cc1e.tar.bz2
kunit: tool: make unit test not print parsed testdata to stdout
Currently, if you run $ ./tools/testing/kunit/kunit_tool_test.py you'll see a lot of output from the parser as we feed it testdata. This makes the output hard to read and fairly confusing, esp. since our testdata includes example failures, which get printed out in red. Silence that output so real failures are easier to see. Signed-off-by: Daniel Latypov <dlatypov@google.com> Reviewed-by: David Gow <davidgow@google.com> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
-rwxr-xr-xtools/testing/kunit/kunit_tool_test.py6
1 files changed, 6 insertions, 0 deletions
diff --git a/tools/testing/kunit/kunit_tool_test.py b/tools/testing/kunit/kunit_tool_test.py
index e2cd2cc2e98f..a6e53945656e 100755
--- a/tools/testing/kunit/kunit_tool_test.py
+++ b/tools/testing/kunit/kunit_tool_test.py
@@ -80,6 +80,9 @@ class KconfigTest(unittest.TestCase):
self.assertEqual(actual_kconfig, expected_kconfig)
class KUnitParserTest(unittest.TestCase):
+ def setUp(self):
+ self.print_mock = mock.patch('kunit_printer.Printer.print').start()
+ self.addCleanup(mock.patch.stopall)
def assertContains(self, needle: str, haystack: kunit_parser.LineStream):
# Clone the iterator so we can print the contents on failure.
@@ -485,6 +488,9 @@ class LinuxSourceTreeTest(unittest.TestCase):
class KUnitJsonTest(unittest.TestCase):
+ def setUp(self):
+ self.print_mock = mock.patch('kunit_printer.Printer.print').start()
+ self.addCleanup(mock.patch.stopall)
def _json_for(self, log_file):
with open(test_data_path(log_file)) as file: