enhancementhelp wantedscope:assertions
Repository metrics
- Stars
- (20,600 stars)
- PR merge metrics
- (No merged PRs in 30d)
Description
It seems like the only problem with #1094 is providing detailed error output when a custom assertion fails. Everything else is straightforward. What if t.fail() could accept an object to use for creating an AssertionError? The fields could be message, actual, expected, and format that will specifying which formatting function to use for setting the values field on the error object. Could also add an optional assertion field for a custom assertion name.
Would this be compatible with #2435?
If there's interest, I can submit a PR for this.