Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Gherkin parser to give more meaningful error messages about file typos #963

Open
plocket opened this issue Jan 6, 2025 · 0 comments
Labels
enhancement New feature or request ? question Further information is requested

Comments

@plocket
Copy link
Collaborator

plocket commented Jan 6, 2025

The current cucumber messages about invalid feature files are confusing to authors. Since we're adding the Gherkin parser library for our constrained random answers generators Step, we could use it to pre-run it for all tests, catch the errors, and add give better descriptions before re-throwing the errors.

Do this before generating any files.

Make into new issue: Potentially, we could also use this to skip erroring files and still run the files that don't have errors. We can take a poll sometime on whether that would be useful to authors.

@plocket plocket added enhancement New feature or request ? question Further information is requested labels Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request ? question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant