Tester's Digest

A weekly source of software testing news


ISSUE #59 - May 19, 2018

Should developers do testing? If your answer is ‘yes’, how do you teach developers to test? The advice is out there. Note, we are not covering how to teach TDD, that’s a separate topic; TDD is not “testing”, it’s a development technique. We are also not talking about unit tests, which all developers should absolutely employ. This discussion is about manual / exploratory / end-to-end testing of features as they get built.

Topic: Teaching Developers To Test

Can developers test? Yes; but there will be a learning curve.


There are innate reasons why developers might perform poorly at testing, if not specifically trained, and they can take certain steps to improve.


A life coach for software developers (that’s a distinct career path now!) targets his post at developers to explain value of testing as a risk reduction mechanism, gives a clear explanation of why taking those extra 10 minutes to test your own code before checking it in can save a lot of time.


Why should the test team teach developers to test their code, how to do it, and what outcomes to expect:


When test engineers act like quality coaches, the successful approach is being more like Batman than like Superman:


Can developers replace testers on agile teams? This report references large studies, makes mixed conclusions: some data indicates that agile teams without dedicated testers perform better on both quality and velocity metrics, other results suggest that having testing professionals on the team is beneficial. (Side note: I wish they’d tested the scrolling on that embedded frame, it’s a dog).


One way to turn developers into testers is through use of a service like RainforestQA where devs author end-to-end testcases which are then executed by a testing crowd through the platform, removing a lot of the work. This case study is from a team that works in this mode without a dedicated QA team. (Full disclosure: I use RainforestQA, but in conjunction with an in-house quality engineering team.)


A great list of resources structured as a pathway to learning testing for non-testers.



Developer of a testing tool tells an ironic tale of failing to test his code properly before an important demo…


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 testersdigest@mehras.net