Quality assurance is sold as one thing and is at least three: finding defects before users do, building the automated safety net that lets you change code confidently, and improving the process so fewer defects are created. Those need different people and different contracts, and buying the first when you needed the third is the usual disappointment.
QA software testing is three different purchases under one name
Testing execution finds defects in what exists and is straightforward to buy by the hour. Test automation is a software build project with its own maintenance obligation. Quality consulting changes how your team works so that fewer defects are produced at all, and it is the only one of the three that reduces future cost rather than detecting present problems. Be explicit about which you are buying, because vendors will happily supply the first when you asked for the third.
Software development quality assurance cannot compensate for an untestable system
If a system cannot be deployed to a clean environment on demand, has no realistic test data and no stable interfaces, no amount of testing effort will produce reliable results. That is why competent consultants start with environments, data and the deployment pipeline rather than with test cases. A vendor that proposes to start writing tests without asking how the system is deployed and how test data is produced has not diagnosed anything.
Agree what finished means before a QA testing service starts
Coverage percentages are a poor definition of done because they measure lines executed rather than risk reduced. Better contract terms are the specific user journeys that must be covered end to end, the maximum acceptable suite runtime, the defect categories that block a release, and who triages a failure. Those are measurable and arguable in advance, which is exactly what a coverage target is not.
What it costs and who does it
Testing is a distinct profession with its own market: BLS reports a median annual wage of $104,300 for software quality assurance analysts and testers in May 2025, against $135,980 for software developers. That gap is one reason dedicated testers are usually better value than having developers test each other's work, and it is also why an automation engagement priced at developer rates deserves a question about who is actually doing the work.
Questions people ask about software testing and quality assurance services
What should a software QA consulting engagement start with?
Environments, test data and the deployment pipeline. A system that cannot be deployed cleanly on demand with realistic data cannot be tested reliably, so a vendor proposing to write test cases before asking about those has not diagnosed the problem.
Is test coverage a good target?
No. It measures lines executed rather than risk reduced, and it is easy to satisfy without improving anything. Contract instead for named user journeys covered end to end, a maximum suite runtime, blocking defect categories and named triage ownership.
Should developers do their own testing?
They should test their own work, and that is not a substitute for dedicated QA. Testers are a separate profession at a different price point, with BLS putting the median at $104,300 in May 2025 against $135,980 for developers, which usually makes them better value for the work.