[tracker/wip/carlosg/junit: 14/15] tests: Use TapTestRunner in functional tests if available




commit 11d1313712d82f5a6c50dd28bbbabc7fa425c56c
Author: Carlos Garnacho <carlosg gnome org>
Date:   Sat Dec 12 20:15:26 2020 +0100

    tests: Use TapTestRunner in functional tests if available
    
    We want to unify test outputs into a format that we can convert to
    JUnit. As the GLib tests already output TAP, and meson converts TAP
    to JUnit, add optional support so our functional tests also output
    TAP.
    
    This is meant to be enabled in CI.

 tests/functional-tests/fixtures.py | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)
---
diff --git a/tests/functional-tests/fixtures.py b/tests/functional-tests/fixtures.py
index 8c16b40b4..3488ae51e 100644
--- a/tests/functional-tests/fixtures.py
+++ b/tests/functional-tests/fixtures.py
@@ -63,7 +63,15 @@ def tracker_test_main():
                             handlers=[handler_stderr, handler_stdout],
                             format='%(message)s')
 
-    ut.main(verbosity=2)
+    runner = None
+
+    try:
+        from tap import TapTestRunner
+        runner = TapTestRunner()
+    except Exception:
+        log.info('No TAP test runner found')
+
+    ut.main(testRunner=runner, verbosity=2)
 
 
 class TrackerSparqlDirectTest(ut.TestCase):


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]