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

More useful reports on internal errors #2105

Closed
Stranger6667 opened this issue Mar 18, 2024 · 0 comments
Closed

More useful reports on internal errors #2105

Stranger6667 opened this issue Mar 18, 2024 · 0 comments
Labels
UX: Reporting Output readability UX: Usability Enhances user experience

Comments

@Stranger6667
Copy link
Member

Coming from #2073

Currently, some internal errors may mimic schema errors and it is confusing. It would be much more useful to distinguish 2 cases and report them properly:

  • Schema validation is disabled and Schemathesis tried to work with the schema as if it is a valid one and it led to an internal error. This one should have a proper error and the reason why it happened. I think the code could be more defensive and check the presence of some keys and report them as schema errors, distinguishing recoverable and non-recoverable
  • Actual internal errors when Schemathesis does not work properly while accessing the schemas.
@Stranger6667 Stranger6667 added UX: Reporting Output readability UX: Usability Enhances user experience labels Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
UX: Reporting Output readability UX: Usability Enhances user experience
Projects
None yet
Development

No branches or pull requests

1 participant