Quick Answer: What questions should I ask a software testing company before hiring?
Ask about scope, method, reporting, and data handling first, then dig into pricing and proof. A good vendor will happily walk through how it designs test cases, what a defect report looks like, and how it measures coverage before any contract is signed. The answers separate teams that test on instinct from teams that follow a documented process you can audit.
Some firms offer manual testing only, while others blend automation, performance work, and security checks, and the difference shapes both price and timeline. Others resell offshore capacity under a local brand, which changes who actually answers your questions at 9 a.m. on a release day.
Before committing, compare written scope, sample defect reports, methodology references, tool stack, data protection terms, references, exit criteria, and total cost including change requests.
Why the First Conversation Decides Most of the Outcome

Picture the scene. A release is three days away, the vendor’s report says “testing complete,” and nobody can tell you what that actually means. Was every requirement covered? Were the risky payment flows tested on a slow connection? Did anyone check what happens when the database times out?
That gap between “we tested it” and “we can prove it works” is where projects bleed money. Most of it gets settled in the sales conversation, long before a single test case is written. The questions below are the ones that surface that gap early, while walking away is still cheap.
One practical tip from people who buy testing services regularly: send your question list by email and ask for written answers. Sales calls reward charm. Written answers reward clarity. The vendor that sends back a structured document with specifics, including the things it does not do, is usually the safer bet.
Start With Scope: What Exactly Is Being Tested?
Scope is the question most buyers skip because it feels obvious. It is not. “Testing” can mean anything from clicking through the main screens to a full regression suite with automated checks running on every commit.
Ask the vendor to define, in writing:
- Which features, platforms, and browsers are in scope, and which are explicitly out.
- Whether testing covers new functionality only or includes regression testing of existing features.
- Whether non-functional areas are included: performance, load, accessibility, usability, security.
- How many test cycles are included and what triggers an extra one.
- What happens when a requirement is ambiguous or missing.
That last point matters more than it sounds. A vendor that writes test cases purely from a vague ticket will test what the ticket says, not what users need. Ask whether they review requirements and raise gaps before testing starts. Testers who question requirements catch defects that developers never had a chance to see. (Rillabox review buyers should know before ordering)
Which Methodology and Standards Do They Follow?
You do not need a vendor to be certified in everything. You do need to know whether they follow a repeatable process or improvise.
The international standard for software testing is ISO/IEC/IEEE 29119, a series covering testing concepts, processes, and documentation. It is not mandatory, and adoption is uneven, so treat it as a signal rather than a pass-fail test. If a vendor cites it, ask which parts shape their process. If they have never heard of it, that is not automatically disqualifying, but it tells you the process is homegrown.
Vocabulary matters too. The ISTQB glossary of testing terms is free and widely used, and it is a handy way to check that “severity” and “priority” mean the same thing to both sides. Plenty of contract disputes are really translation problems: the vendor’s “critical” defect is your “minor annoyance.”
For quality attributes, ISO/IEC 25010 defines a product quality model with characteristics such as functional suitability, performance efficiency, security, and maintainability. It gives you neutral words for asking what, specifically, will be measured. Note that the 2011 version was superseded by a 2023 revision, so confirm which version a vendor cites.
If security testing is in scope, ask whether findings are mapped to the OWASP Top Ten, the widely referenced awareness document on web application security risks. The current edition is 2021, with a 2025 release discussed at the time of writing, so verify the status. Also ask whether the team follows a published methodology such as the OWASP Web Security Testing Guide or PTES. “We do security testing” is a claim. “We follow WSTG and report against the Top Ten” is a checkable statement. (Ai chatbot security 2027 9 questions ask before buying)
How Do They Report Defects and Prove Coverage?
Ask for a sample defect report. Not a template. A real, redacted example from a past project.
A useful report includes steps to reproduce, expected versus actual behavior, environment details, severity, priority, screenshots or logs, and the build version. If the sample is a single line reading “login broken,” expect the same quality on your project.
Then ask the harder question: how do they measure coverage? Common answers include requirement coverage, code coverage, and risk-based coverage. Each has limits. Code coverage can hit 90 percent while the checkout flow stays untested. Requirement coverage says nothing about whether the requirements were any good. A vendor that can explain the trade-offs, rather than quoting one number, is worth listening to.
Also pin down exit criteria, the conditions that must be met before testing is declared done. According to the ISTQB glossary, exit criteria are the agreed conditions for completing a test activity. Get yours in writing: zero open critical defects, all high-priority cases executed, regression suite green. Without them, “done” becomes whatever the invoice needs it to be.
How Do They Handle Your Data and Environments?
If the vendor will touch production-like data, this section deserves real attention.
GDPR, the EU regulation applicable since May 2018, governs how personal data is processed, and test data is no exception. Ask how production data is anonymised or masked before it reaches a test environment, who can access it, and whether a data-processing agreement is in place.
If the vendor manages its own environments or handles your data at scale, ask about ISO/IEC 27001, the international standard for information security management systems, current edition 2022. The key follow-up: what is the scope of the certification? “We are certified” means little if the certificate covers the head office and not the offshore test lab.
For security engagements, NIST SP 800-115, the technical guide to information security testing and assessment, is a useful public reference for planning tests, agreeing rules of engagement, and formatting results. Ask whether the vendor’s reports follow a similar structure. If they will run penetration tests, ask who is authorised to sign off, what the testing window is, and how out-of-scope systems are protected.
What Does the Tool Stack Look Like, and Who Owns the Automation?
Automation questions trip up a lot of buyers. A vendor may promise automated regression at a tempting price, then deliver a fragile suite that breaks every sprint and nobody maintains.
Ask which tools they use and why, whether the automation code lives in your repository or theirs, and who owns it if the contract ends. Ask how they keep tests maintainable: page objects, test data management, CI integration. Ask what percentage of the suite is automated and, more importantly, which scenarios they deliberately keep manual. Exploratory testing still finds the bugs scripts miss. (Managed detection response checklist 12 questions ask before)
Vendors who happily hand over automation code and documentation tend to be confident in their work. Vendors who guard it as intellectual property are building a dependency, whether they say so or not.
What Will It Actually Cost, and What Is Not Included?
Pricing models vary widely, and comparing headline rates is a trap. A per-hour rate tells you nothing about efficiency. A fixed price tells you nothing about what happens when scope shifts.
| Pricing model | Best suited to | Watch for |
|---|---|---|
| Time and materials | Evolving products, unclear scope | Hours creep with no visibility into value |
| Fixed price per cycle | Stable, well-defined releases | Change requests priced steeply |
| Retainer | Continuous testing needs | Unused hours that expire quietly |
| Per test case | Auditable, countable work | Incentive to write many shallow cases |
Ask what triggers a change request, how it is priced, and whether test environment setup, test data creation, and reporting time are billed separately. Those three items are where budgets quietly disappear. Get a sample invoice or a worked example for a project like yours.
Can They Prove It? References, Certifications, and Trial Work
Ask for two or three references from clients with a similar product, stack, and regulatory context. Then ask the references two questions the vendor cannot script: what went wrong, and how did the vendor respond? Every project has a rough patch. The response is the product.
Certifications are useful but narrow. A tester holding an ISTQB certification has passed an exam on terminology and fundamentals; it does not prove they can test your payment system. Treat certificates as a floor, not a ceiling. Verify any certification claim directly with the issuing body rather than relying on a logo on a slide.
A small paid pilot is often the smartest move. Give the vendor one feature, one sprint, and a fixed fee. You will learn more about their communication, report quality, and speed from two weeks of real work than from any pitch deck. Buyers weighing bigger procurement decisions often use the same logic, as this managed detection response checklist of 12 questions to ask before buying shows: ask early, ask in writing, and compare answers side by side.
What Do They Do When Things Go Wrong?
Ask how the vendor handles a missed deadline, a production defect that slipped through, or a disagreement about severity. Look for a named escalation contact, a defined response time, and warranty terms. Some contracts include a free re-test window for defects found after sign-off. Others do not.
Also ask about communication rhythm: daily standups, weekly reports, a shared channel. Testing fails quietly when information stops flowing. A vendor that insists on a regular written summary is protecting both sides.
If the vendor’s answers feel rehearsed, request a short written response to a realistic scenario. Something like: “A critical defect is found on release day. Walk us through the next four hours.” The reply reveals more about process maturity than any brochure.
Conclusion
Hiring a software testing company is a procurement decision wrapped inside a trust decision. The questions above are not about catching vendors out. They are about making expectations visible while everyone is still friendly and the contract is still unsigned.
Written scope, a documented methodology, a sample defect report, clear exit criteria, honest data-handling answers, transparent pricing, and verifiable references will carry you through most of the risk. Add a small paid pilot, and you will know more in two weeks than most buyers learn in a year. The best vendor will welcome every question on this list. The one that dodges them has just answered the most important question of all.
FAQ
How many testing vendors should I evaluate before choosing one?
Three is a practical number. Two makes comparison thin, and five burns weeks of evaluation time. Give each vendor the same written brief and the same question list, then compare answers side by side rather than sequentially. Consistency in the brief is what makes the comparison meaningful.
Is a fixed-price contract always safer than time and materials?
No. Fixed price protects the budget only when scope is genuinely stable and well documented. On evolving products, fixed-price deals tend to produce either steep change-request fees or quiet scope trimming. Time and materials works better when you have visibility into hours and a clear weekly reporting rhythm.
Do I need a vendor that is certified to ISO/IEC 27001?
It depends on what they will touch. If the vendor handles production data or runs its own environments, certification is a reasonable baseline. If they only test a staging environment you control, the question matters less. Either way, ask about the certification’s scope and what that scope covers, rather than only whether a certificate exists.
Should automated testing replace manual testers?
Not entirely. Automation excels at repeatable regression checks, data-driven scenarios, and fast feedback in CI. Manual and exploratory testing still catch usability problems, unexpected workflows, and edge cases that scripts miss. Most mature teams run both, with automation handling the repetitive load.
What is a reasonable length for a paid pilot?
Two to four weeks covering one feature or sprint is usually enough to judge report quality, communication, and speed. Define success criteria before it starts: defects found, report clarity, response times. A pilot without criteria becomes a free trial that teaches you nothing.
How do I verify a vendor’s references are genuine?
Ask for references from clients in your industry with a similar stack, then contact them directly rather than through the vendor. Ask specific questions about problems encountered and how they were resolved. Vague praise is a warning sign; detailed stories about a rough patch and its fix are a good one.


