I'm submitting a ...
What is the current behavior?
allure-cucumber(1/2/3)-jvm interprets an exceptions (RuntimeException for example) as FAILED, but allure-junit(4/5) interprets it as BROKEN.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
Just run a simple junit and cucumber projects based on suitable allure plugin.
You can catch this projects here
https://github.com/kosteman/allure-junit5
https://github.com/kosteman/allure-cucumber2
and execute it with
mvn clean test allure:serve
What is the expected behavior?
allure-cucumber(1/2/3)-jvm interprets an exceptions as BROKEN
What is the motivation / use case for changing the behavior?
everywhere should be the same behavior
Please tell us about your environment:
| Allure version |
2.7.0 |
| Test framework |
Junit@5.2.0 |
| Test framework |
Cucumber@2.4.0 |
| Allure integration |
allure-cucumber2-jvm@2.7.0 |
| Allure integration |
allure-junit5@2.7.0 |
| Generate report using |
allure-maven@2.9 |
| Other |
maven-surefire-plugin@2.22.1 |
I'm submitting a ...
What is the current behavior?
allure-cucumber(1/2/3)-jvm interprets an exceptions (RuntimeException for example) as FAILED, but allure-junit(4/5) interprets it as BROKEN.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
Just run a simple junit and cucumber projects based on suitable allure plugin.
You can catch this projects here
https://github.com/kosteman/allure-junit5
https://github.com/kosteman/allure-cucumber2
and execute it with
mvn clean test allure:serveWhat is the expected behavior?
allure-cucumber(1/2/3)-jvm interprets an exceptions as BROKEN
What is the motivation / use case for changing the behavior?
everywhere should be the same behavior
Please tell us about your environment: