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

When only one test is running allure report for allure-hermione generates result with all tests in the project #757

Closed
alenamakarovaya opened this issue Aug 22, 2023 · 0 comments · Fixed by #758
Assignees
Labels
theme:hermione type:bug Something isn't working

Comments

@alenamakarovaya
Copy link

Describe the bug
When only one test is running allure report generates result with all test in project
Running test has result(failed/passed) and other tests are skipped on 2.5.0 version of allure-hermione
It can affect statistic of tests and load for processes will increase

To Reproduce
Steps to reproduce the behavior:

  1. It can be reproduced in repo https://github.com/fortrest-jr/allure-tests/tree/Steps on branch Steps
  2. Switch to branch Steps
  3. npm i
  4. npm run test -- --grep 3
  5. Create allure report

Expected behavior
Report has only one passed test

Actual behavior
Report has 4 tests: 1 passed, 3 skipped

Screenshots
image

Additional context
Problem became with new release 2.5.0

@alenamakarovaya alenamakarovaya changed the title When only one test is running allure report for allure-hermione generates result with all test in project When only one test is running allure report for allure-hermione generates result with all tests in the project Aug 22, 2023
@epszaw epszaw self-assigned this Aug 22, 2023
@epszaw epszaw added type:bug Something isn't working theme:hermione labels Aug 22, 2023
@baev baev closed this as completed in #758 Sep 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
theme:hermione type:bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants