Replies: 1 comment
-
A |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello!
I didn't want to raise as an issue for a few reasons, but sought to try and understand first more context.
I find annoying sometimes identifying which test step has failed in a test, and to some degree which test scenario (when gherkin terminal reporter is off) as the link between an error and the step/scenario within the feature file that it originates from are not clear when running from the IDE.
Is there a possibility of linking the top of the backtrace to the originating step in the scenario's feature file? I am not sure of the difficulties in doing so and haven't dug around to see if I'm honest, so thought I would ask.
Happy to have a look if some pointers are given as this is a part of Cucumber Java I miss when diagnosing errors.
Example current backtrace:
Beta Was this translation helpful? Give feedback.
All reactions