apache / apache/maven-surefire
[SUREFIRE-528] Splitting tests names in two categories : success and failure
- Dominant language
- Java
- Stars
- 461
- Forks
- 588
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 19
Description
**[Emmanuel Lécharny](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=elecharny)** opened **[SUREFIRE-528](https://issues.apache.org/jira/browse/SUREFIRE-528?redirect=false)** and commented
We have to check all the *.txt files to find the ones which contain some errors. The fact that failed tests are listed before does not help a lot when you have hundred of tests run with sometime lot of logs.
I would rather propose that we either create two sub-directories (failure/success) or that we postfix tests.
A good example :
...
Tests run: 197, Failures: 1, Errors: 0, Skipped: 0
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] There are test failures.
Please refer to /home/elecharny/apacheds/mina/trunk/core/target/surefire-reports for the individual test results.
...
Would be better to have :
Please refer to /home/elecharny/apacheds/mina/trunk/core/target/surefire-reports/failure for the individual test failures.
---
**Affects:** 2.0 (2.2 plugin)
**Issue Links:**
- [SUREFIRE-726](https://issues.apache.org/jira/browse/SUREFIRE-726) Test list preprocessor support for tests to be run
- [SUREFIRE-726](https://issues.apache.org/jira/browse/SUREFIRE-726) Test list preprocessor support for tests to be run
(_**"depends upon"**_)
Contributor guide
Research direction
Start by inspecting the current report output under target/surefire-reports and how Surefire presents failed tests and logs. Compare the proposed failure/success directories with postfixing test reports; the work is done when failed reports are easy to locate and the generated guidance points to their location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100