-
Notifications
You must be signed in to change notification settings - Fork 2
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
Improve error descriptions #106
Labels
Comments
Nylle
added a commit
that referenced
this issue
Aug 22, 2024
jk-idealo
added a commit
that referenced
this issue
Aug 23, 2024
Also, chained assertions. Refs: #106
Nylle
added a commit
that referenced
this issue
Aug 25, 2024
akutschera
pushed a commit
that referenced
this issue
Aug 25, 2024
akutschera
pushed a commit
that referenced
this issue
Aug 25, 2024
Also, chained assertions. Refs: #106
akutschera
pushed a commit
that referenced
this issue
Aug 25, 2024
Fixed since version 2.11.0. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When trying to create an instance of a class, we use multiple approaches, including but not limited to
If all those strategies fail, we throw an exception only telling the user that the final step failed. In order to investigate what's wrong with the class, one has to debug into Fixture.
As a user I would like to see the outcome of all intermediate steps, e.g. if no factory-method was found and the fixturing fails, I'd like to see that also no constructor was found, etc.
The text was updated successfully, but these errors were encountered: