You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Environment (please complete the following information)
multiple-cucumber-html-reporter: 3.9.0
Node.js version: 20.11.1
NPM version: 10.2.4
Platform name and version: Windows 10
Cucumber version: latest
Config of multiple-cucumber-html-reporter
cucumberReporter JSON generated using playwright config. Used Reporter.ts to generate the custom report based on the JSON created
Describe the bug
Feature file names with more than 68 characters is crashing the test report
To Reproduce
Steps to reproduce the behavior:
Created a new feature file with Feature name more than 68 character long.
Created a new test scenario under the feature file.
Executed the feature file using the custom report generator.
Successfully generated the report and able to see the summary page which list the names of features that are executed.
Click on the feature name with more than 68 character long.
Error displayed saying file not found.
Tried executing with shorter name for feature name and the report works as expected without any issues.
[Include code or an example repository that can easily be set up]
Expected behavior
Report able to navigate to the feature summary page.
Log
If applicable, add logs to help explain your problem. If you don't have logs, enable 'debug:true' in the config and paste the log here.
Please use proper markdown to style it
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Environment (please complete the following information)
Config of multiple-cucumber-html-reporter
cucumberReporter JSON generated using playwright config. Used Reporter.ts to generate the custom report based on the JSON created
Describe the bug
Feature file names with more than 68 characters is crashing the test report
To Reproduce
Steps to reproduce the behavior:
Tried executing with shorter name for feature name and the report works as expected without any issues.
[Include code or an example repository that can easily be set up]
Expected behavior
Report able to navigate to the feature summary page.
Log
If applicable, add logs to help explain your problem. If you don't have logs, enable 'debug:true' in the config and paste the log here.
Please use proper markdown to style it
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: