James Whittaker tweeted:
My updated take @esconfs is that if you are still concentrating on testing then you are doing development all wrong. Test is dead.
— James Whittaker (@docjamesw) January 15, 2016
The short answer is: Testing as activity is not dead.
Testing like we used to in the 20th century should be dead, but is not.
In an Agile team there are more/better unit tests and with prototyping and early involvement of users functional testing becomes less of an activity performed by testers. Arguably tester as seperate role could be dying. But that is not my perception or experience.
Testers now are much more technical savvy. They have to be.
Since we mostly work in Agile teams the testing role has changed.
So let us focus on the team. An Agile team is not a team of some generic designers/developers/testers blended into one entity. It is a team of specialist.
We have UI-specialists, performance specialists, data(base) specialists and, yes, Testing specialists.
As part of the development team our activities have changed and include coaching developers, risk analysis, end-to-end testing activities and more often than not involves specializing in one of the areas like test automation, security or performance.
So a seperate test organization that receives software and performs tests on them?
Yes, that testing is (or should be) dead. It is outdated and does not deliver the quallity we demand.
Testing as specialist activity in a team? Not dead and probably will be around for a while.
So where I disagree with Whittaker is that he assumes that tester as role is dead and that testing activities will magically be done by others like developers and users – who in reality will be unable to see beyond their own horizon.
Testing activities are here to stay – and so are the professionals who are best suited to perform them.