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

Improve error descriptions #106

Closed
Nylle opened this issue Aug 22, 2024 · 1 comment
Closed

Improve error descriptions #106

Nylle opened this issue Aug 22, 2024 · 1 comment
Assignees

Comments

@Nylle
Copy link
Owner

Nylle commented Aug 22, 2024

When trying to create an instance of a class, we use multiple approaches, including but not limited to

  • finding a public constructor
  • finding a public factory-method

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.

@Nylle Nylle self-assigned this Aug 22, 2024
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
@jk-idealo
Copy link
Collaborator

Fixed since version 2.11.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants