allure-framework / allure-framework/allure-java

If classes with the same names are used in the tests run by TestNG, then only the last result will be recorded.

Open
#632 2 comments 1 reaction 0 assignees View on GitHub
Dominant language
Java
Stars
376
Forks
240
Avg merge
1d 7h
Merged PRs (30d)
45

Description

**Describe the bug**
My project Selenide+TestNG+Allure+Maven
I use TуstNG suites, which have test classes with the same names.
The tests pass successfully, but the Allure report contains only a report on tests from the last TestSuite, for tests with the same class names.

**To Reproduce**
There are two test suite

















In maven pom.xml


src/test/java/ru/ga/TestsSuite1.xml
src/test/java/ru/ga/TestsSuite2.xml


start test maven command

mvn clean test

result in maven

[INFO] Results:

[INFO]

**[INFO] Tests run: 16, Failures: 0, Errors: 0, Skipped: 0**

[INFO]

[INFO] ------------------------------------------------------------------------

[INFO] BUILD SUCCESS

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 02:22 min

[INFO] Finished at: 2021-08-19T06:47:46+03:00

[INFO] -------

**Tests run: 16 that**

- parametrized for 2 runs
- parametrized for 2 runs
- parametrized for 2 runs

In Allure report

see Screenshots

**Expected behavior**
test results with the same class names should not overwrite results

**Screenshots**
![image001 (2)](https://user-images.githubusercontent.com/41778132/130007648-473824c0-f89d-458c-8cb4-9daa8704c0f8.png)

**Desktop (please complete the following information):**
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]

**Smartphone (please complete the following information):**
- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]

**Additional context**
Add any other context about the problem here.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue with the two TestNG suite XML files described in the report and run `mvn clean test`. Inspect the TestNG integration and Allure result identity handling; done means all 16 executed tests remain separately represented in the Allure report instead of results from duplicate class names overwriting one another.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.