Break down traditional QA silos and empower devs to own quality checks.
Quality Assistance may sound very similar to quality assurance, and while the two are related QA engineers’ role, there are some differences between the two.
Let’s start with Quality Assurance:
- The QA tends to give the ‘go’ or ‘no go’ for a release.
- The QA tends to test every newly developed feature before a release.
- The QA tends to build and maintain the test automation framework.
- The QA creates all bug tickets.
- The QA defines a test plan and executes it themselves.
And now let’s look at a few points for Quality Assistance:
- The QA shares their testing expertise with developers, so the developer can test.
- Developers don’t rely on the QA to do all the testing, decreasing the potential for testing bottlenecks.
- The QA can help by creating workshops that identify common testing pitfalls with developers.
- The QA is not testing every newly developed feature before release, the developers are empowered to do so.
- Bugs are detected much earlier in the development phase.
- The QA isn’t a release guardian, once tested confidently by developers they have the independence to release.
It’s clear to see that the two operate quite differently, quality assistance focuses on sharing and building testing confidence within developers. Software systems have become more complex over the years, and the traditional way of funneling all of the testing through the QA just isn’t as efficient as it used to be. Moving towards the Quality Assistance approach should help your team to move faster, deliver sooner and build a stronger testing culture within your entire team, and not just the QA.
Subscribe if you like what you’ve read ? Leave a clap 👏 and stay tuned for more!
