I think I’m building on something you convinced me of if I say that the fact that basically none of the Ruby or JS frameworks is built for unit testing (without the DB or DOM as dependencies) makes it really hard to integrate a pure TDD unit testing workflow into them.https://twitter.com/searls/status/1137057803468759041 …
-
-
Replying to @noelrap
I wrote teenytest—that's JS! How do you think Minitest falls short in Ruby?
4 replies 0 retweets 0 likes -
Replying to @searls
For me, Minitest falls short most often because I reach for mock tools that aren’t there. (I also think RSpec’s CLI tools are better). But those are both at the margin, if you like Minitest, that’s great. Using either one is better than using neither one.
2 replies 0 retweets 0 likes -
yes the mocking in rspec is second to none; I copied it for jstest but almost nobody uses that
1 reply 0 retweets 0 likes -
Replying to @mountain_ghosts @noelrap
Wow, really? rspec-mocks is one of the worst, net harmful test double libraries I've ever seen. Way overbroad in its feature set and all the defaults and opinions are (IMO) focused on hacking up implementation details rather than outside-in TDD
2 replies 0 retweets 1 like -
I respectfully disagree here. I could see the argument that some of its defaults were chosen poorly, but I've always found it to be best in class for what it's trying to do, and I'm always missing the ease of use of its API in other languages
1 reply 0 retweets 0 likes -
Completely fair. And for the record I feel badly for even sending that broadside on a Friday afternoon because I lack the energy to follow through with my point-by-point dissertation on why I believe what I do. Some other time maybe. Have a great weekend everyone, bye!
2 replies 0 retweets 1 like
Enjoy your weekend 
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.