-
-
Notifications
You must be signed in to change notification settings - Fork 190
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
Clean validation of Tavern files is required to allow using it in a productive way #724
Comments
hsq125
changed the title
Errors in Tavern files are not properly indicated to user, which makes it a nightmare to use.
Clean validation of Tavern files is required to allow using it in a productive way
Oct 19, 2021
This is partially the reason I'm switching to using jsonschema in the next release, it should be able to provide more useful errors like
For the time being you can also use the pytest |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm stuck for hours with a simple test with one config file and one external stage file.
Each time there is a single mistake, I'm left with a stack trace of 500 line without clear indication about what is wrong.
This is just an example, but Tavern crashes here and there depending on the issue. That is not possible to use this in a productive way.
The text was updated successfully, but these errors were encountered: