Tracking Issue for libtest's JUnit reporter · Issue #85563 · rust-lang/rust (original) (raw)

Skip to content

Navigation Menu

• • GitHub Copilot Write better code with AI
  • GitHub Advanced Security Find and fix vulnerabilities
  • Actions Automate any workflow
  • Codespaces Instant dev environments
  • Issues Plan and track work
  • Code Review Manage code changes
  • Discussions Collaborate outside of code
  • Code Search Find more, search less
• Explore
  • Learning Pathways
  • Events & Webinars
  • Ebooks & Whitepapers
  • Customer Stories
  • Partners
  • Executive Insights
• • GitHub Sponsors Fund open source developers
  • The ReadME Project GitHub community articles
• • Enterprise platform AI-powered developer platform
• Pricing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Description

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

• Implementation: feat(libtest): Add JUnit formatter #84568 Use as_secs_f64 in JunitFormatter #86359
• Final commenting period (FCP)
• Stabilization PR

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.