Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

allure shows improper test case count for JUNIT testsuites #618

Closed
1 of 3 tasks
mailtosoma opened this issue Oct 5, 2017 · 0 comments
Closed
1 of 3 tasks

allure shows improper test case count for JUNIT testsuites #618

mailtosoma opened this issue Oct 5, 2017 · 0 comments
Assignees
Labels
theme:readers type:improvement Change that improves some user experience but can't be considered as a new feature

Comments

@mailtosoma
Copy link

mailtosoma commented Oct 5, 2017

I'm submitting a ...

  • bug report
  • feature request
  • support request => Please do not submit support request here, see note at the top of this template.

What is the current behavior?

I executed junit test cases and got the xml output. I passed that as input to allure, noted improper test case count. When a test case is executed on different product versions, it generates testsuites, each test suite executes same test case, but on different version. allure displays them as 1, and in fact I believe the first test case was shown as retries

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

What is the expected behavior?

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Allure version 2.2.0
Test framework [email protected]
Allure adaptor [email protected]
Generate report using [email protected]

Other information

@baev baev added the type:improvement Change that improves some user experience but can't be considered as a new feature label Oct 8, 2017
@baev baev self-assigned this Oct 8, 2017
@baev baev closed this as completed in a36769a Oct 8, 2017
@baev baev removed the work:review label Oct 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
theme:readers type:improvement Change that improves some user experience but can't be considered as a new feature
Projects
None yet
Development

No branches or pull requests

2 participants