Nessa Jane Marin

@justincampbell I really like that you didn't try to tackle generating random data first in generative... I could see someone working on your typical Ruby web app getting really far...

Turning this into a checklist: - [ ] Generative should give the user data generation capability out of the box - [ ] Generative should require another gem to accomplish...

Started on a gem to generate random data: https://github.com/levionessa/degenerate

@arronmabrey thanks for the feedback. I'm definitely not opposed to this... I would say though in other generative testing libraries in other languages I don't have that and it doesn't...

Cool. Haven't been watching for it in Degenerate so let me know if you notice any random data not working out this way.

Just want to track some thoughts... Getting ready soon to implement _something_ for shrinking and might take a stab at more composable generators... I noticed Rantly is doing roughly what...

More notes... seems like the part that's like rantly is straight forward enough... the tricker part of me is how to hijack the running of an example and rescue from...

@justincampbell some half-baked ideas I haven't really explored yet: 1. Create a subclass of `RSpec::Core::Example`. Something like `GenerativeExample` and write something like an `ExampleGroup.check` method that would replace `it`... Not...

1. Something else involving using a custom method instead of an example group method....

@justincampbell I can confirm this has been fixed since `command-and-rake-task` has been merged. See https://github.com/levionessa/rb-fizzbuzz/blob/master/spec/fizz_buzz_spec.rb. I through a `binding.pry` into the example based test and it only executed once.