Last week, I featured Anne-Marie Charrett's article on 3 amigos in Agile. This time, she shared more about the modern version where the QA role differs from the traditional one. I found it both interesting and accurate.
Some may say testing is all about the automation nowadays but this is far from the truth. Edward Kelly explains why the balance between manual and automated efforts is the key to successful testing in Agile.
Gone are the days where companies will hire a horde of testing specialists who act as a safety net, waiting for code to be tossed over the proverbial wall by developers to perform validation before a release can happen.
So what do "the days" look like now? I liked Jeff Sing's explanation of the modern approach to Quality Engineering.
A great addition to that is Janet Gregory's article about Testing From A Holistic Point Of View.
There have been several of articles written on how Google tests software (mainly based on the famous book) but these lessons are so valuable, they're well worth repeating. Here Dilusha Kumarage did a great job describing the key concepts.
What if…? What else? What happens when…? Who is this for? Why is it designed like this? When can this be used? How can this function be used differently than expected? What value does it provide? To whom?
In most cases, only checking that requirements are met is simply not enough testing. So these are just a few questions that Maria Kedemo advises testers to ask while testing.
Testability is one of these things that's much easier to be built-in rather than built on top of implementation. Gregory Paciga explains why it's not a trivial problem and what a tester can do to help developers care for that.