bazelbuild / bazelbuild/rules_java
Extending BazelTestRunner to Add Custom Metadata to JUnit XML
- Dominant language
- Starlark
- Stars
- 103
- Forks
- 102
- PR merge metrics
- No merged PRs in 30d
Description
I've been working on extending the BazelTestRunner to add custom metadata (properties) to the JUnit XML generated by Stripe's Java tests, but I'm hitting a roadblock.
The most promising approach I've found involves using the TestPropertyExporter singleton instance, but I'm uncertain about how it's meant to be used. Additionally, when looking into the Bazel codebase, I noticed that the method testEmittedProperty() in TestSuiteModel.java seems related, but it isn't being called anywhere.
Any advice or alternative suggestions would be appreciated.
Contributor guide
Research direction
Start by tracing BazelTestRunner and the TestPropertyExporter singleton, then inspect TestSuiteModel.java and the unused testEmittedProperty() method. Determine how custom properties should flow into the JUnit XML and identify the relevant Java test coverage. Done means Stripe's Java test output includes the requested metadata and verifies it reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100