Frequently Asked Questions: Software Quality Assurance in New Zealand
What is QA testing in software development?
Quality Assurance (QA) testing is the process of systematically identifying bugs, usability issues, and performance problems in software before it is released to users. QA includes functional testing (does it work as intended?), regression testing (does new code break existing features?), performance testing, security testing, and user acceptance testing. Good QA is what prevents software failures in production.
Why does dedicated QA testing matter?
Bugs found during QA testing cost a fraction of bugs found after release. A bug identified before release might take an hour to fix; the same bug discovered in production could cost days of emergency developer time, user trust damage, and potential data integrity issues. Dedicated QA is an investment that consistently pays for itself many times over.
Does Putti provide QA testing services?
Yes. Putti has a dedicated QA team that tests all software they build and also offers standalone QA services for software built by other teams. They provide both manual testing for complex user flows and automated testing pipelines for regression coverage. Based in Auckland, Putti’s QA team is integrated with their development team for seamless handoff and issue resolution.
What is the difference between QA by developers and a dedicated QA team?
Developers testing their own code is significantly less effective than dedicated QA testing. Developers have blind spots around their own implementations, are often too close to the code to catch usability issues, and face time pressure to ship rather than to find problems. Dedicated QA testers approach software from a user’s perspective, test edge cases developers didn’t consider, and can catch a significantly higher percentage of bugs before release.