Thus, to evaluate any testing strategy, you cannot just evaluate how it finds bugs. You also must evaluate how it enables developers to fix (and even prevent) bugs. Via: http://googletesting.blogspot.co.uk/2015/04/just-say-no-to-more-end-to-end-tests.html Of course, J. B. Rainsberger has been saying this for years. But it’s nice to see Google reinforcing it.
A walkthrough of getting an initial smoke test in place. Covers Rack::Test, OmniAuth, email_spec, Capybara, and more.
Sometimes on RubyTapas I serialize larger projects into bite-sized pieces. In this episode, you can see a slice of the outside-in TDD process I use as I develop part of my gem-love project. You’ll see me thinking about messages before objects, a la POODR, and using WebMock to fake out a not-yet-existent server.
At the borders of our systems, mockist testing hits a point of diminishing returns. In this free episode we take a look at when to stop mocking and start integration testing.
I have a few ongoing miniseries in RubyTapas. In this, the second installment of a miniseries chronicling the creation of a Rubygems plugin and an associated server, I touch on a number of topics including acceptance testing, the shellwords standard library, the TDD rhythm, and the DataMapper ORM.