diff options
| author | Dylan Baker <dylan@pnwbakers.com> | 2020-04-22 12:25:49 -0700 |
|---|---|---|
| committer | Dylan Baker <dylan@pnwbakers.com> | 2020-04-23 13:26:01 -0700 |
| commit | 7b7f93a09f90c93d94e4a78ddc1dd766f05bf4a9 (patch) | |
| tree | 506a32461fce0b777f627ec069bab542e48d27cb /docs/markdown | |
| parent | 0c3bb15357419d3cc7a453da25b349a9c34e391d (diff) | |
| download | meson-7b7f93a09f90c93d94e4a78ddc1dd766f05bf4a9.zip meson-7b7f93a09f90c93d94e4a78ddc1dd766f05bf4a9.tar.gz meson-7b7f93a09f90c93d94e4a78ddc1dd766f05bf4a9.tar.bz2 | |
mtest: Generate a JUnit xml result file
JUnit is pretty ubiquitous, lots of services and results viewers
understand it, in particular gitlab and jenkins know how to consume
JUnit xml. This means projects using CI services can have their test
results consumed automatically.
Fixes: #6972
Diffstat (limited to 'docs/markdown')
| -rw-r--r-- | docs/markdown/snippets/junit_result_generation.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/markdown/snippets/junit_result_generation.md b/docs/markdown/snippets/junit_result_generation.md new file mode 100644 index 0000000..fbe910b --- /dev/null +++ b/docs/markdown/snippets/junit_result_generation.md @@ -0,0 +1,4 @@ +## Meson test now produces JUnit xml from results + +Meson will now generate a JUnit compatible XML file from test results. it +will be in the meson-logs directory and is called testlog.junit.xml. |