apache / apache/maven-surefire

[SUREFIRE-1336] Sure-Fire test run totals don't match TestNG report on failure.

Open
#2,353 0 comments 0 reactions 0 assignees View on GitHub
bug priority:minor
Dominant language
Java
Stars
461
Forks
588
Avg merge
1d 8h
Merged PRs (30d)
19

Description

**[Jeff Vincent](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=predatorvi)** opened **[SUREFIRE-1336](https://issues.apache.org/jira/browse/SUREFIRE-1336?redirect=false)** and commented

One of my TestNG test classes has 2 multi-threaded test methods that use DataProviders to feed in unique parameter values. In total, I have a test run that runs a total of 530,000 unique test instances between the two test methods.

In all test output files (XML, HTML, etc.), the test totals are correct (530,000 total, 22 failed, 529,978 passed.) The first test method runs 10,000 times, the 2nd test method runs 520,000 times. If all 520,000 pass, it reports 520,000 test cases succeed, but if any one of the iterations fail (or even multiple failures), then it only reports the single test method as a failure which is not accurate.

It seems that it isn't counting failures the same as it counts successes.

---

**Affects:** 2.19.1

**Attachments:**
- [testng-console.png](https://issues.apache.org/jira/secure/attachment/12853799/testng-console.png) (_12.61 kB_)
- [testng-reportnghtml.png](https://issues.apache.org/jira/secure/attachment/12853798/testng-reportnghtml.png) (_17.28 kB_)

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue with the described multi-threaded TestNG methods and DataProviders, using 530,000 instances with failing iterations. Compare the console totals against the XML and HTML reports; done means failure counts and test totals remain accurate when one or more iterations fail.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.