Closed mbigras closed 6 years ago
I'm not overly familiar with the codebase so I'm not sure of the feasibility, but I like the idea! :)
@mbigras, Would you be willing to work on a PR for this?
I'm working on a fix for this right now. Will submit a PR when I'm ready. :)
The PR to resolve this has been merged, so I'll close this off.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Summary
Thank you for this project!
I'm having an issue when using
cucumber --format stepdefs
when there is a typo in my step. The cucumber --format stepdefs stack trace is too harsh and doesn't provide guidance to a solution. Issues #953 and #955 point out a problem with using the--format stepdefs
flag but don't clarify the problem or provide a solution.The work around solution is:
Main idea
Steps to Reproduce (for bugs)
Context & Motivation
Showing a user a 40 line stack trace for making a typo in the step definition is too harsh and not helpful.
Your Environment
Also, there is a repo I put together that will also reproduce the error: https://github.com/mbigras/cukular_bomb
Stack trace for reference