Skip to content

Tracking Issue for libtest's JUnit reporter #85563

Open
@andoriyu

Description

@andoriyu

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-libtestArea: `#[test]` / the `test` libraryC-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCT-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions