Si QA no es de nadie, nadie se preocupa por QA

En un artículo llamado The QA Mindset donde se nota que el que escribe es de una escuela más vieja que la actual, y bastante contemporánea a la mía, encuentro esto:

“My concern is that the absence of QA is the absence of a champion for aspects of software development that everyone agrees are important, but often no one is willing to own. Unit tests, automation, test plans, bug tracking, and quality metrics. The results of which give QA a unique perspective. Traditionally, they are known as the folks who break things, who find bugs, but QA’s role is far more important. It’s not that QA can discover what is wrong, they intimately understand what is right and they unfailingly strive to push the product in that direction.

I believe these are humans you want in the building.”

La tesis del artículo es que antes había una función de QA clara, ahora ya no. Para el autor no está claro si eso es bueno o no, pero le preocupa que porque nadie es QA, nadie se preocupa por QA.

Yo veo esa postura, no sólo con QA, en muchas organizaciones.

Antes de irme, dejo esta otra cita con la que me sentí muy identificado:

“In QA, there is a distinct moment. It comes once you’re deeply familiar with your product or product area; it comes when you’re lost in your testing, and it comes in an instant. You find a problem, and because of your strong context about your product, you definitely know:Something is seriously wrong here.”

Seguimos pensando..

PD: Este post está dedicado a Fernando.