This is a tracking issue for libtest's JUnit reporter.
Add an alternative formatter to libtest. The formatter produces valid xml that later can be interpreted as JUnit report. Report can be consumed by Continuous Integration tools like Jenkins.
Public API
Run test binary with --format=junit argument.
Steps / History
Unresolved Questions
timestamp is required by schema, but every viewer/parser ignores it. Attribute is not set to avoid depending on chrono;
- Each test suite (doc tests, unit tests and each integration test) must be run separately. This due to a fact that from
libtest perspective each one of them is a separate invocation.
libtest doesn't know what is the name of integration binary is being run, so in the report it just says integration for all of them.
- No test cases in src/test or otherwise validating output format correctness.
This is a tracking issue for libtest's JUnit reporter.
Add an alternative formatter to libtest. The formatter produces valid xml that later can be interpreted as JUnit report. Report can be consumed by Continuous Integration tools like Jenkins.
Public API
Run test binary with
--format=junitargument.Steps / History
Unresolved Questions
timestampis required by schema, but every viewer/parser ignores it. Attribute is not set to avoid depending on chrono;libtestperspective each one of them is a separate invocation.libtestdoesn't know what is the name of integration binary is being run, so in the report it just saysintegrationfor all of them.