ISSUE #47 - February 11, 2018
You can’t test the quality in, they say. So how do we get to build software at a better quality level? We examine some techniques for writing better code: code reviews (duh), writing good commit messages and error messages, pairing and mobbing approaches. Tell your developers, and keep in mind that test code is code, so let’s practice what we preach.
Tips for better code review process. The romance analogy is cheesy (yet suitable for the upcoming Valentine’s day!), don’t let it throw you off, it gets good later on.
How to write better commit messages, which then help code review and make later “git blame” useful:
How to write good error messages:
How to build Web APIs for success, principles from Salesforce, including “Trust in Acceptance Tests” (BDD style) and “Log, Monitor and Alert” – I couldn’t agree more.
Nice little rant imploring developers to deliver software that’s challenging for testers to find bugs in:
Pair programming has promise of delivering a higher quality product with increased velocity in the long run. This article is a how-to guide:
While this paper outlines costs (15% increase in development time) and benefits: “improves design quality, reduces defects, reduces staffing risk, enhances technical skills, improves team communications and is considered more enjoyable”
Tester-developer pairing technique promises benefits in learning on both sides, earlier bug discovery, and more maintainable automated tests:
Mobbing technique with both programmers and testers participating can “turn programmers into better testers, and improve any testers capabilities”.
Worth learning: On more effective ways of presenting test information to others, based on data visualization principles from Edward Tufte, the god of viz:
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