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
I just discovered the test.step feature. It's really nice and helps me having a nice and tidy report. Unfortunately, every test.step() even the one in Typescript decorator are showing code snippets.
This results in a weird and messy report at the end.
I'm suggesting to add a parameter whether to decide if we want it or not in the HTML report. Or disable the code snippets for test.step by default
Example
This example show the wrong behavior. The right example would be just a dropdown with the step name in it
Motivation
I think test.step is a great feature for keeping an HTML report tidy, without using any BDD/Cucumber methods in the project. But with the code displayed, it looks a bit complicated and unreadable, which defeats the whole purpose of the feature.
The text was updated successfully, but these errors were encountered:
Totally agree with @Sedatyf.
Do like this feature for my reports but what a mess to have the code detail.
May we have at least a reporter option to deactivate ✂️
🚀 Feature Request
I just discovered the
test.step
feature. It's really nice and helps me having a nice and tidy report. Unfortunately, every test.step() even the one in Typescript decorator are showing code snippets.This results in a weird and messy report at the end.
I'm suggesting to add a parameter whether to decide if we want it or not in the HTML report. Or disable the code snippets for
test.step
by defaultExample
This example show the wrong behavior. The right example would be just a dropdown with the step name in it
Motivation
I think
test.step
is a great feature for keeping an HTML report tidy, without using any BDD/Cucumber methods in the project. But with the code displayed, it looks a bit complicated and unreadable, which defeats the whole purpose of the feature.The text was updated successfully, but these errors were encountered: