ISSUE #12 - Apr 23, 2017
Today’s theme is unit tests, a huge space, so don’t expect exhaustive coverage!
Why unit tests are worth the trouble:
A developer’s approach to writing (mostly unit) tests:
Unit test tips from everydayunittesting.com which is a blog and a book “being written in an agile manner”:
If your unit tests are difficult to write, that is a signal of poor design:
Test smells, i.e. markers of poor quality in your test code (not just for unit tests):
Always test these conditions or inputs: null, zero, one, many, too many. Obvious? I should hope so. But you still gotta do it. Every time.
A classic on using mock objects in your tests:
Best practices specific to RSpec, Ruby’s BDD test framework:
Google’s analysis of the degree of flakiness in their corpus of 4.2 million tests, broken down by test size/type. They find that “large” tests, i.e. end-to-end/integration tests, are the flakiest at 14% bogus failure rate over a week, compared to “small” (unit) tests at only 0.5%, and conclude that one needs to weigh whether to write a “large” test at all, and be careful if doing so.
While it’s still April, this April’s Fools post on reducing your MTTR for production incidents was the best. Achieve zero MTTR through skipping the investigation and resolution stages and simply auto-closing the tickets as soon as they are opened. Can be applied to bugs, too!
If you received this email directly then you’re already signed up, thanks! Else if this newsletter issue was forwarded to you and you’d like to get one weekly, then you can subscribe at http://testersdigest.mehras.net
If you come across content worth sharing, please send me a link at firstname.lastname@example.org