-
Notifications
You must be signed in to change notification settings - Fork 595
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
Use a dedicated TestResult object instead of keeping ConjectureData around #1820
Conversation
Is #411 still relevant here, or is it fine for this type to be named |
If it's something we should avoid doing, it would be good to add a linter for it (in another PR). The specific reason to avoid this no longer applies to modern versions of Pytest, but it's a good general principle and we do support and test against older versions where it would matter. |
Oh yeah, that's a good shout. It's not fine and I'll change the name. |
3b71149
to
4cb61c1
Compare
One thing worth noting is that currently we have some methods which this would catch, and those aren't problems as long as they don't belong to a class named An alternative way we could lint this is that we could check that there are no globals in a Hypothesis test package that start with Test or test and come from a Hypothesis module and aren't the stateful testing |
|
09361cd
to
6c415c1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than that possible tweak to coverage, this all looks good to me.
The main motivation for doing this was memory usage, but I think it actually makes the API much cleaner to have a logical distinction between its data and its result, and it's something I've vaguely felt I should do for a while but never got around to.