[tracker/wip/carlosg/junit: 10/15] tests: Specify 'tap' format for JUnit generation
- From: Carlos Garnacho <carlosg src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [tracker/wip/carlosg/junit: 10/15] tests: Specify 'tap' format for JUnit generation
- Date: Sat, 12 Dec 2020 19:25:28 +0000 (UTC)
commit 763b4a85560d873c96df370a503a662fd86affe3
Author: Carlos Garnacho <carlosg gnome org>
Date: Thu Dec 10 16:54:15 2020 +0100
tests: Specify 'tap' format for JUnit generation
This lets the generated JUnit file handle all GLib tests transparently,
at the individual testcase level. The functional tests don't output
TAP, so are seen as a big blob instead...
tests/meson.build | 1 +
1 file changed, 1 insertion(+)
---
diff --git a/tests/meson.build b/tests/meson.build
index 562204efe..5f5855d70 100644
--- a/tests/meson.build
+++ b/tests/meson.build
@@ -32,6 +32,7 @@ foreach t: tests
test(test_name, test_exe,
env: test_env,
timeout: test_timeout,
+ protocol: 'tap',
suite: test_suite,
is_parallel: test_is_parallel)
endforeach
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]