Skip to content

libtest output for common CI systems #51924

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
lzybkr opened this issue Jun 29, 2018 · 1 comment
Closed

libtest output for common CI systems #51924

lzybkr opened this issue Jun 29, 2018 · 1 comment
Labels
A-libtest Area: `#[test]` / the `test` library C-feature-request Category: A feature request, i.e: not implemented / a PR.

Comments

@lzybkr
Copy link
Contributor

lzybkr commented Jun 29, 2018

It would be useful if libtest would write a file in a format supported by CI systems.

Based on AppVeyor and VSTS, it looks like junit or xunit3 could be good choices.
@lzybkr lzybkr mentioned this issue Jun 29, 2018
Closed
@stokhos stokhos added C-feature-request Category: A feature request, i.e: not implemented / a PR. A-libtest Area: `#[test]` / the `test` library labels Jun 30, 2018
@daxpedda daxpedda mentioned this issue Dec 27, 2018
Closed
@johnterickson johnterickson mentioned this issue Feb 5, 2019
Closed
This was referenced Feb 20, 2019
Closed
Open
@Mark-Simulacrum
Copy link
Member

I think this is out of scope for libtest which tries to be pretty minimal, but piping libtest's JSON output (#49359) to some other command should be feasible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-libtest Area: `#[test]` / the `test` library C-feature-request Category: A feature request, i.e: not implemented / a PR.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@lzybkr @Mark-Simulacrum @stokhos