@DataProviders are very useful indeed. They allow you to run the same test with different parameter values. JUnit 4 has something like this, but TestNGs implementation is a lot easier to use.
Bamboo should count the produced test results accordingly.
At the moment test cases are only distinguished by their testcase name. parameters are not taken into account.
- causes
-
BAM-6990 Need to handle duplicate test results from testng reports gracefully
- Closed
-
BDEV-1046 Failed to load
- duplicates
-
BAM-2627 Incorrect JUnit test count when multiple tests have the same name
-
- Closed
-
- is cloned from
-
-
- Closed
-
- mentioned in
-
Page
Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[BAM-4188] Count ALL test results of TestNG @DataProvider feature to run the SAME TC with different parameters.
rohit.sharma - can you please create support ticket on https://support.atlassian.com/browse/BSP and please attach:
- screenshots of your tasks configurations (especially Maven and TestNG tasks)
- TestNG report files and their locations
- logs from the build
- screenshot of the "Tests" build result screen
also please mention my name in the ticket so Support Team can redirect this issue to me.
Cheers,
Krystian
rohit.sharma I've contacted a developer to confirm this. Ill post back here as soon as I know more.
Rohit Sharma
added a comment - This is still not fixed. We are using 4.4.1 build 3502 but I still see the same issue
Rohit Sharma
added a comment - This is still not fixed. We are using 4.4.1 build 3502 but I still see the same issue We use the testNG 'data provider' capability with some tests. The 'data provider' will run the same test multiple times with different input data, and thus we get the same test run multiple times. Net result, we have 363 tests, but Bamboo is only reporting 103 tests.
One way or another, this needs to be fixed.
Ulrich Kuhnhardt [Atlassian]
added a comment - https://support.atlassian.com/browse/BSP-1952 
We seem to be running into the same problem (in 4.4.2). The information above states that the fix went into version 4.4 which to me implies that it should also be fixed in 4.4.2. Which versions did this fix go into ?
Thanks