-
Notifications
You must be signed in to change notification settings - Fork 12
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
Add new article: "Property Testing with Complex Inputs" #30
base: master
Are you sure you want to change the base?
Conversation
A brief guide on how to create complex inputs for property tests. Covers: `from_type`, `assume`, `filter`, `builds`, `register_type_strategy`, `composite`, and `data`.
As part of issue HypothesisWorks#29
Oh wait, it's Jekyll-inspired and doesn't need Ruby One sec |
It's actual-Jekyll, but we've got a dockerized build which should handle installing everything in a container (assuming it hasn't bitrotted. It's been a while since we've built the site) |
Build process doesn't work at all on windows, going to reinstall WSL2 and see if that does it |
It's giving me an error saying there's no docker daemon. Do I need to know how to use Docker to run this, or is the makefile supposed to take care of all of this for me? |
I've tried using docker and also tried building it natively and keep running into issues. At this point I'm going to admit that I don't think I'll be able to do this without help. |
What do you think about hosting it on my blog for now and rehost it on the hypothesis site later? |
@hwayne - I can now merge things onto the website, and I'm happy to fix any formatting issues live after merge (I do intend to fix the bitrot and get PR preview builds working, but no need to wait for this). Are you happy for me to publish this as-is, or is there anything you'd like to change? |
This adds a new article to the site, a guide to making complex inputs, like inputs that satisfy preconditions or use other inputs. Two notes: