How to choose a software testing partner: a 10-point checklist

The 10-point checklist

• Can they name who will test your product, not just describe a team?
• Do they offer a small paid trial before a long contract?
• Do they show you a real, redacted bug report, not a generic sample?
• Do they cover both manual and automated testing, or push one over the other regardless of fit?
• Is pricing and scope written down clearly, with no vague and-more language?
• Do they ask about your architecture before quoting a price?
• Can they explain how they would test your riskiest flow, specifically?
• Do they mention flaky test rates or maintenance cost, or only speed?
• Are client references checkable, not just logos on a slide?
• Do they say plainly what they are not good at?

A partner who is honest about their limits is usually honest about everything else too.

Why the last point matters most

Every vendor will tell you what they are good at. Few will tell you where they are weak, or which projects they would turn down. That honesty is a better predictor of the relationship than anything in the pitch deck, because it tells you whether they will flag a real problem later or quietly let it slide.

Start small, not long

The lowest-risk way to test any of this is a short, paid engagement, like a 2-week testing audit, rather than a year-long commitment. You get a real look at how they work before either side is locked in.

Want to see how we would answer this checklist? Request a free 30-minute testing audit and judge for yourself.