-
Notifications
You must be signed in to change notification settings - Fork 575
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 stateful documentation #3881
Conversation
Is there a CI tag I can add so that it doesn't waste time running CI apart from the doc build? I'm not sure how to run the doc build locally either, as it doesn't appear to follow the usual Sphinx layout I'm familiar with. |
The pyodide run failed in a way I can only describe as "flaky":
Is this worth doing something about? (Like, filing a bug report, I mean.) |
Including The Pyodide build is a bit slower than the others, so I'm not particularly surprised to see such issues... I'd just ignore for now, it seems rare and the build is not required so it shouldn't block us. I'll track in our "make CI faster" issue #3524 if it keeps happening. |
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.
Thanks Anne! I think this will be a great improvement for people getting started with stateful testing ❤️
thanks, looking into it! |
In #3511, a number of issues with the stateful documentation are raised. Some are simple confusion, some are outright errors in the documentation. This PR makes no code changes but attempts to clarify and correct the documentation to better explain how hypothesis works.
Rendered docs: https://hypothesis--3881.org.readthedocs.build/en/3881/stateful.html#rule-based-state-machines