Extending BazelTestRunner to Add Custom Metadata to JUnit XML
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- java
- Domain
- build-system, testing-qa
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.
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.
- Dominant language
- Starlark
- Stars
- 103
- Forks
- 102
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bazelbuild/rules_java
-
P4
Difficulty 4/5 3-5 days Newbie friendliness 55/100
bazelbuild/rules_java#360 · 4 comments · 2 reactions ·
-
P4
Difficulty 5/5 Over a week Newbie friendliness 35/100
bazelbuild/rules_java#354 · 8 comments ·
-
P3 question
Difficulty 3/5 1-2 days Newbie friendliness 45/100
bazelbuild/rules_java#339 · 1 comment ·
-
P3
Difficulty 4/5 3-5 days Newbie friendliness 35/100
bazelbuild/rules_java#325 · 8 comments ·
-
P4
Difficulty 4/5 3-5 days Newbie friendliness 35/100
bazelbuild/rules_java#316 · 2 reactions ·
All issues in bazelbuild/rules_java
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oSoWoSo/vOid_Community_repOsitory#147 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
agentic-workflows cascade-suspected
Difficulty 1/5 Under an hour Newbie friendliness 88/100