Testing is dead. Gantt, the cascading lifecycle, design (and UML) are all dead. Processes (CMMI), methodologies (except Scrum), software engineering (software is art!)…. even agility is dead. This is the trend in software quality, but is it the way to go? ”.
This is how he opened his presentation Javier Garzas, Director of the company Kybele Consulting and Professor at the Rey Juan Carlos University, in the Conference on Quality and Testing that we organized in Panel last October. Nothing more and nothing less ! His talk gave a lot to talk about, and proof of this is the subsequent debate that was generated among all the attendees.
There is no doubt that today, in the post-agile era that we live in, the figure of the tester as an independent development entity, and the benefits derived from this activity, are in question. But the reality is that testing needs to be reinvented, and companies look for new ways more agile to ensure the "quality" of what we build.
After the presentations, we decided to do a interview with the four experts who intervened in the Conference: Javier Garzas, Director of the company Kybele Consulting and Associate Professor at the Rey Juan Carlos University; to Carlos Losa, Manager of Certification and Implementation of Systems of Telefónica Spain; to Pablo rivera, Operations Director of Panel Sistemas; already Javier Lopez-Camacho, Business Manager of Panel Sistemas.
We asked the four of them three questions about testing activity and the evolution of Software Quality, and It is at least curious to observe the differences in the four answers: each of them brings a different perspective of the business and the profession. And although deep down the general opinion is that the figure of the tester should be "transformed" but not "eliminated", it is worth comparing the vision of these four experts, to realize that there are still many things to say, and for decide, in the future of Software Quality.
We invite you to watch the interview, and to leave your comments.
In EVOLUTION, without a doubt. If one has to evolve and does not know or does not want to ... surely it is close to decadence.
When mobile telephony appeared, the brilliance of technology overshadowed the importance of preserving "conversation quality." We are still paying that mortgage: "please call me on the landline that I don't know about."
The brilliance of massive access to software programs (the "Personal Computer") overshadowed the importance of preserving that software free of errors: "if it crashes, reboot and that's it."
Can we continue to pay this mortgage?
The easy view is to think, "hmm, restarting a running car isn't cool." Futuristic. Well, maybe not so much:
I think that the tester (or whatever you want to call it) is a function inherent to the creation of a product.
Is quality on the decline?
Let's restart then.
In line with how the way of developing is changing ... many of the roles are changing, including that of tester.
There will always be testing, but the speed that many developments require today is making the figure of the traditional tester totally separate from development and working on the last phase of the «cascade life cycle» obsolete (when it is too late to say what is failing )
Indeed Javier, today many development projects require a change in the concept of testing.
It is proven that in a percentage close to 80% the errors made in software production come from the first phases of the life cycle (definition and design of systems, test strategy, project management, etc.). That is why it is important to integrate testing in each phase, and with an agile methodology, from the beginning, working as a team with development.
The problem is that it is more common than we think that software is not tested, for many reasons ... We are at least convinced of the importance of ensuring the quality of what you do 😉
Thank you for your comments, and for your presentation!