Ministry of Testing have announced the next 30 days of testing challenge. There are 30 activities that have to be completed before the end of March. I’ve created a page within my blog detailing the progress. I’m not going to do all the tasks in order, as some can only be done at work.
The theme of the 30 day challenge is testability so this weeks list is going to include several articles and blog posts on the subject. There are likely to be more over the next few weeks. One of the tasks in the challenge is to share a blog post that relates to testability. A list of all blog posts that I read on Testability will also be shared here.
Test Talks podcast – Front-end architecture making way for testing with Fabio Nolasco
Fabio Nolasco describes his career as a front end developer and the importance of a front-end architect as well designed architecture can help make the software more testable.
The good, the bad, and the buggy – It’s a Match!
A discussion on how technology has been used in the online dating industry including the development of UI patterns like swipe right/swipe left, made popular by Tinder.
Guilty Tester – Episode 10 – All by myself
No guest for this episode, the host answers questions that he’s been asked on twitter including the very intriguing questions “Are testers courageous?”
Blogs and Articles
Why you don’t need a hero
Michael “Fritz” Fritzius discusses the difference between the hero and the guide when it comes to introducing Test Automation to an organization.
Automated test debugging cheat sheet
A list of common issues that arise when developing and running automated tests. Is the problem with the system under test, test environment or the automated test itself?
Giving feedback is hard. Really hard
In this article, Tom Sommer provides some really useful advice on how to give feedback when working in Agile and Scrum teams.
Do software testers need to know how to code?
A blog post written by John Kensinger was shared on linkedin this week in which he gave an answer to this question. Unsurprisingly, a lot of people commented giving their own opinion. This isn’t the first time this question has been asked and it most certainly won’t be the last. Here are a few blog posts which offer different answers:
- John Kensinger, test.io
- Michael Bolton, developsense.com
- Paul Maxwell-Walters , Paul’s Testing Rants (includes several more links to blogs that discuss the question).
Heuristics of Software Testability
James Bach describes the 5 different types of “testabilities”, discusses some interesting testability dynamics and provides some guide words to use when analyzing testability.
Dimensions of Testability
A model developed by Ben Kelly and Maria Kedemo that delves even deeper into the subject of testability than James Bach’s model, demonstrating how broad and diverse the subject can be.
Four (and more) questions for testers to ask
(At least) four things for Testers to do in planning meetings
Testability cannot be achieved unless the testers have the right information. These 2 blog posts by Michael Bolton that discuss the what testers should be doing and what questions they should be asking. These can help improve the testability of a software application.
Another article by Michael Bolton which responds to a question that asks if there is an example of testability that doesn’t involve improving the ability to automate.
Testability vs Automatability
A blog post by the ‘evil tester’ (or Alan Richardson) who differentiates between testability and automatability (or automatizability, but he finds this harder to pronounce). This includes a 5 minute video which is worth a watch.
Feel free to recommend anything that you think is of interest.
Main image taken from http://www.publicdomainpictures.net