Member-only story
“It’s the fault of QA”.
It’s the recurring and easy excuse of a new delayed and buggy release. We need a culprit, and for once we can’t blame the network team. The QA, responsible for quality is an ideal target.
Moreover, “it’s not complicated to do tests”. Taking a step back, this position assumes that quality rhymes with testing. However, we do blood tests without necessarily being in good health.
This segregation of QA quickly reaches its limits to help create value. At best, we can run a few automated tests to find anomalies with a high cost of rework at the end of the chain.
This article shares the key elements of the Quality Assistance model inspired by leading players such as Atlassian or GitLab. You can find their implementation at Manomano and OpenClassrooms in this article.
Follow the QE Unit for more exclusive Quality Engineering from the community.
Quality Assistance, necessary for the creation of value
The traditional QA is too often perceived as the medical testing firm carrying out tests once the software development is finished. The logical next step is that of an organizational silo misunderstood and limited in value addition. And most…
