rust - generate correct xml reports
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
Research direction
Start by locating the Rust XML report generation entry point and how tests under a Bazel target are grouped into a single suite. Reproduce the current report, then verify that each test in the suite is represented separately in the generated XML.
Written by the indexing model from the issue text.
Description
currently all tests under bazel target are treated as 1 test. Each test under single test suite should be splitted
- Dominant language
- Python
- Stars
- 5
- Forks
- 38
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 22
Contributor guide
No contributing guide indexed for this repository
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 eclipse-score/reference_integration
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
eclipse-score/reference_integration#264 · 1 comment ·
-
bug
eclipse-score/reference_integration#259 · 6 comments · 1 assignee ·
-
v0.8
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
v0.8
Difficulty 4/5 3-5 days Newbie friendliness 38/100
eclipse-score/reference_integration#244 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
All issues in eclipse-score/reference_integration
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100