I'm submitting a ...
What is the current behavior?
Current behavior: To create the json file name in allure-results folder, allure use feature description and scenario name to generate it.
The problem it's longer than 254 character, the file will not be generated and the scenario will not appear in the result.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
On mac, create a scenario with a 254 character name. Run the test. No result in allure-result.
What is the expected behavior?
The scenario should appear in the report (or at least I should have some error message to know that scenario is ignored).
The first solution I am thinking of is to use a UUID on the scenario name instead of the feature/scenario name. It will also remove the issue with the '/' character.
What is the motivation / use case for changing the behavior?
We shouldn't have to worry about the length of the feature/scenario name.
Please tell us about your environment:
| Allure version |
2.4.1 |
| Test framework |
cucumber jvm |
| Allure integration |
allure-cucumber-jvm@2.0-BETA19 |
| Generate report using |
allure@2.4.1 |
Other information
I'm submitting a ...
What is the current behavior?
Current behavior: To create the json file name in allure-results folder, allure use feature description and scenario name to generate it.
The problem it's longer than 254 character, the file will not be generated and the scenario will not appear in the result.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
On mac, create a scenario with a 254 character name. Run the test. No result in allure-result.
What is the expected behavior?
The scenario should appear in the report (or at least I should have some error message to know that scenario is ignored).
The first solution I am thinking of is to use a UUID on the scenario name instead of the feature/scenario name. It will also remove the issue with the '/' character.
What is the motivation / use case for changing the behavior?
We shouldn't have to worry about the length of the feature/scenario name.
Please tell us about your environment:
Other information