bazel-contrib / bazel-contrib/rules_scala
test.xml output from scala_junit_test is lacking in detail
Open
Nobody has claimed this yet.
- Dominant language
- Starlark
- Stars
- 384
- Forks
- 292
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 46
Description
JUnit test class with 6 test methods, in which 1 fails gives the following output:
$ cat bazel-testlogs/foo/bar/test/test.xml
<?xml version=1.0 encoding=UTF-8?>
<testsuites>
<testsuite name=foo/bar/test tests=1 failures=0 errors=1>
<testcase name=foo/bar/test status=run>
<error message=exited with error code 1></error>
</testcase>
</testsuite>
</testsuites>
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.
Research direction
Start at the scala_junit_test rule and reproduce the sample test.xml output from the issue. Trace how test failures are collected and serialized, then add coverage for the six-method, one-failure case; done means the XML reports the individual test failure details rather than only an exit code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- build-system, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100