We need to evaluate and compare Rust test runners, particularly focusing on the ability to generate JUnit XML format reports for integration with CI systems.
Context:
-
We currently use cargo test for running Rust tests.
-
There is interest in cargo-nextest, a next-generation test runner, which claims to offer enhanced features and JUnit XML output.
-
The main goal is to determine which tool is the best fit for our workflows, especially considering requirements for JUnit XML reports and any implications for tool qualification or certification.
Tasks:
Compare the features of cargo test and cargo-nextest, with emphasis on:
-
JUnit XML output support and compatibility
-
CI/CD integration ( GitHub Actions)
-
Performance and reliability
-
Any considerations for qualification/certification in regulated environments
-
Try out cargo-nextest in one of our Rust projects and generate a sample JUnit XML report.
-
Summarize pros/cons and recommend the best approach for our needs.
We need to evaluate and compare Rust test runners, particularly focusing on the ability to generate JUnit XML format reports for integration with CI systems.
Context:
We currently use cargo test for running Rust tests.
There is interest in cargo-nextest, a next-generation test runner, which claims to offer enhanced features and JUnit XML output.
The main goal is to determine which tool is the best fit for our workflows, especially considering requirements for JUnit XML reports and any implications for tool qualification or certification.
Tasks:
Compare the features of cargo test and cargo-nextest, with emphasis on:
JUnit XML output support and compatibility
CI/CD integration ( GitHub Actions)
Performance and reliability
Any considerations for qualification/certification in regulated environments
Try out
cargo-nextestin one of our Rust projects and generate a sample JUnit XML report.Summarize pros/cons and recommend the best approach for our needs.