Open drathier opened 7 years ago
There is also lobo, and I honestly have no idea why it's necessary over what we provide. You also missed elm-verify-examples which is in the README already.
But yes, I think this is a good idea. I think the "strategies" should be meatier ideas than "use this library. Logically this means that if we are going to mention other libraries, they should get a section to themselves.
However, I kind of like the idea of "recommended" libraries over a comprehensive list. Another possibility is to have a GitHub pages page where we can update the table independently of the release cycle.
However, I kind of like the idea of "recommended" libraries over a comprehensive list.
Yeah - the alternative would get out of hand pretty quickly.
Personally I'm comfortable recommending the ones we currently list, but there aren't any others that have crossed the threshold for me. I know they're out there, but I don't feel confident enough to recommend them at this point.
I'd recommend the elm-verify-examples
, but not for example my elm-architecture-test
right now. (I'd feel more confident if we let the situation around Fuzz.andThen
, test-update
etc. stabilize and converge into something that doesn't have the warts we currently know it has :) ).
Do we want a list/table of packages that provide additional functionality on top of elm-test? Right now, we're mentioning elm-html-test and elm-testable under "Application-specific techniques", but there are two more I think should be mentioned.
update
function with randomMsg
.