I had just created yesterday names constants, and after creating it was meaningful, but hard and ugly to read. So I just refactored to your proposed Arbitrary.Pattern.
Glad you found it useful! I'm a big fan of ARBITRARY. Though when I find there are too many or they are shared between tests, then there's a deeper problem - and it's time to fix that.
I love this approach Arlo -- so much more productive than using an extra layer of indirection such as Cucumber.
I also really liked your use of an Arbitrary namespace to make it clear what's inessential gubbins just to make the test compile.
And finally I like your use of images for the code snippets, instead of Substack's terrible code blocks. I'm definitely going to steal that idea 🙂
Awesome and thanks so much for this feedback! Agreed that Substack's code blocks are pretty terrible - glad to inspire :)
Thanks, Arlo,
For that very practical inspiration.
I had just created yesterday names constants, and after creating it was meaningful, but hard and ugly to read. So I just refactored to your proposed Arbitrary.Pattern.
Better to read and more cohesive. Thx
Glad you found it useful! I'm a big fan of ARBITRARY. Though when I find there are too many or they are shared between tests, then there's a deeper problem - and it's time to fix that.