# QA vendor questionnaire

_ChooseQAVendor framework v1.0. Situation: General. 81 questions. Nothing you enter in the toolkit is sent anywhere._

Issued by [Buyer]. Please answer every question in writing. Answer with specifics: names, documents, numbers and examples. Where you cannot answer, say so; a blank or generic answer scores zero.

---

## Team and staffing

_Who actually does the work, how senior they are, and what happens when people leave._

### 1. Who, by name and role, will work on our account in the first three months? Please share their CVs and confirm these are the people who will start, not examples.

Answer:

Evidence attached (document name or link):

### 2. What is the seniority mix of the proposed team, and how many years of testing experience does each person have on products like ours?

Answer:

Evidence attached (document name or link):

### 3. If a named team member leaves or is moved to another client, how much notice do you give us, who approves the replacement, and how is knowledge handed over?

Answer:

Evidence attached (document name or link):

### 4. What proportion of the proposed team are your own employees, and will any work be done by contractors or subcontractors? If so, which roles and where are they based?

Answer:

Evidence attached (document name or link):

### 5. Which testing qualifications do the proposed testers hold, and how can we verify them?

Answer:

Evidence attached (document name or link):

### 6. Who is the single accountable lead on your side, how much of their time is allocated to us, and what decisions can they make without escalating?

Answer:

Evidence attached (document name or link):

### 7. How will your testers work inside our team day to day: which of our meetings do they attend, whose backlog do they work from, and who on our side assigns their work?

Answer:

Evidence attached (document name or link):

### 8. How many working hours overlap between your team and ours, and who is available during our core hours when a release is blocked?

Answer:

Evidence attached (document name or link):

### 9. How quickly can you add or reduce testers, what notice do you need in each direction, and does the rate change when the team size changes?

Answer:

Evidence attached (document name or link):

### 10. Can we interview the proposed testers before we sign, and can we run a short paid pilot with the same people?

Answer:

Evidence attached (document name or link):

---

## Process and methodology

_How the vendor decides what to test, documents it and fits into your delivery cycle._

### 11. Please share an anonymised test strategy or test plan you have written for another client. What sections does it contain?

Answer:

Evidence attached (document name or link):

### 12. How do you decide what to test first and what not to test? Walk us through how you would assess risk on our product.

Answer:

Evidence attached (document name or link):

### 13. What are your entry and exit criteria for a test cycle, and who has the authority to say a release is not ready?

Answer:

Evidence attached (document name or link):

### 14. What does a defect report from your team contain, and can you show us a few real, anonymised examples?

Answer:

Evidence attached (document name or link):

### 15. How do you fit testing into an agile, iterative delivery cycle? At what point in a sprint or release does your team start testing a change?

Answer:

Evidence attached (document name or link):

### 16. How do you plan and record exploratory testing so that we can see what was covered and what was found?

Answer:

Evidence attached (document name or link):

### 17. How do you cover non-functional quality such as performance, accessibility and security? Which of these do you do yourselves, and which would you leave to us or a specialist?

Answer:

Evidence attached (document name or link):

### 18. How do you get and manage test data? Will your team ever need access to production data, and if so, how is it masked or protected?

Answer:

Evidence attached (document name or link):

### 19. What test environments do you need from us, and how do you make sure results in those environments reflect how the product behaves in production?

Answer:

Evidence attached (document name or link):

### 20. In your first 30 days on our account, what will you produce and how will we know onboarding has worked?

Answer:

Evidence attached (document name or link):

---

## Automation and code ownership

_Who owns the test code, which framework it uses, and whether you can maintain it without the vendor._

### 21. Where will the test automation code live? Will it be in a repository that we own and control from the first commit?

Answer:

Evidence attached (document name or link):

### 22. Who owns the intellectual property in the test code, test cases, data and documentation you produce for us, and does any of it depend on your own libraries or accelerators?

Answer:

Evidence attached (document name or link):

### 23. Which automation framework would you use for our product, and why that one? What would make you choose differently?

Answer:

Evidence attached (document name or link):

### 24. How do you define, detect and deal with flaky tests? What do you do with a test that passes and fails on the same code?

Answer:

Evidence attached (document name or link):

### 25. How will the automated tests run in our CI pipeline, and how long should a full run take before it slows our developers down?

Answer:

Evidence attached (document name or link):

### 26. How do you keep test code maintainable? Do you have coding standards, code review and a way of structuring tests that our developers could follow?

Answer:

Evidence attached (document name or link):

### 27. How do you decide which tests to automate and which to keep manual, and how will you report automation coverage to us?

Answer:

Evidence attached (document name or link):

### 28. If we ended the contract tomorrow, could our own engineers run, read and extend the test suite without you? What documentation would they have?

Answer:

Evidence attached (document name or link):

### 29. What access will your engineers need to our code, pipelines and cloud accounts, and how will that access be granted, reviewed and removed?

Answer:

Evidence attached (document name or link):

### 30. If you are taking over automation from a previous supplier or our own team, how will you assess the existing suite before deciding to keep, fix or rewrite it?

Answer:

Evidence attached (document name or link):

---

## Tooling

_How the vendor's work runs inside your tools and pipeline rather than theirs._

### 31. Which tools will you use for test management, defect tracking and reporting, and will they be our accounts or yours?

Answer:

Evidence attached (document name or link):

### 32. Are any of the tools you propose licensed by you and charged to us, directly or inside your rate? What happens to those licences if we part ways?

Answer:

Evidence attached (document name or link):

### 33. Can all test cases, results and defect history be exported in an open format such as CSV, JSON or plain text at any time, not only at exit?

Answer:

Evidence attached (document name or link):

### 34. How will your tools connect to our existing pipeline, issue tracker and chat channels? Is there anything we would need to install or change?

Answer:

Evidence attached (document name or link):

### 35. Which devices, browsers and operating systems will you test on, and are they real devices, emulators or a cloud device service? Who pays for that service?

Answer:

Evidence attached (document name or link):

### 36. Which tools and methods do you use for accessibility testing, and how do you combine automated checks with manual checks against WCAG 2.2?

Answer:

Evidence attached (document name or link):

### 37. If security testing is in scope, which methodology and tools do you follow, and what do you not cover that a specialist penetration tester would?

Answer:

Evidence attached (document name or link):

### 38. Do you use any AI or code-generation tools on client work? If so, which data from our product is sent to them, and can we opt out?

Answer:

Evidence attached (document name or link):

### 39. How is test progress shown to us during a cycle? Can we see a live dashboard in our own tools, and which measures does it show?

Answer:

Evidence attached (document name or link):

### 40. Where are your tools and any test artefacts hosted, in which countries, and does any of our data leave our environment when your tools run?

Answer:

Evidence attached (document name or link):

---

## Security and data

_Security posture, certifications with verifiable scope, and handling of test and personal data._

### 41. Can you share your most recent SOC 2 Type II report under NDA, and tell us its audit period, the Trust Services Criteria in scope, and which offices and systems it covers?

Answer:

Evidence attached (document name or link):

### 42. What does your ISO/IEC 27001 certificate cover: which legal entity, which sites and which services? Which certification body issued it, which accreditation body accredits that body, and when does it expire?

Answer:

Evidence attached (document name or link):

### 43. Where will our test data, test results, screenshots and logs be stored, in which countries, and on whose systems? Who on your side can reach them?

Answer:

Evidence attached (document name or link):

### 44. Will your testers ever need production data? If so, how do you mask, subset or synthesise it, and who approves any exception?

Answer:

Evidence attached (document name or link):

### 45. If you process personal data for us, will you sign a data processing agreement that covers every point in GDPR Article 28(3), including acting only on our documented instructions, confidentiality, security, assistance, deletion or return, and audits?

Answer:

Evidence attached (document name or link):

### 46. Which subprocessors, subcontractors or freelancers would touch our systems or data? How do you tell us before adding or changing one, and can we object?

Answer:

Evidence attached (document name or link):

### 47. If our data will be accessed from outside the UK or EEA, which transfer mechanism will you use, and have you carried out a transfer risk assessment for those countries?

Answer:

Evidence attached (document name or link):

### 48. How do you control access to our environments: named accounts, multi-factor authentication, least privilege, managed devices, and removal when someone leaves the team? How quickly is access removed?

Answer:

Evidence attached (document name or link):

### 49. Will you complete our security questionnaire, or a standard one such as the CSA CAIQ, and back each answer with evidence we can sample?

Answer:

Evidence attached (document name or link):

### 50. How will you notify us of a security incident or personal data breach affecting our data, within what time, and what will the first notice contain?

Answer:

Evidence attached (document name or link):

### 51. How do you manage supply chain risk in your own tools and dependencies, such as test frameworks, plugins, browser extensions and cloud services used on our work?

Answer:

Evidence attached (document name or link):

---

## Reporting and communication

_What you see each week, how problems surface, and how the team talks to yours._

### 52. Can you show us a real, anonymised weekly status report from a current engagement, with nothing added for the sales process?

Answer:

Evidence attached (document name or link):

### 53. How exactly do you define and count your defect metrics, such as severity, priority, defect leakage, reopen rate and fix verification time? Where are those definitions written down?

Answer:

Evidence attached (document name or link):

### 54. Which measurable outcomes would you agree to be held to, how are they measured, and what happens when one is missed?

Answer:

Evidence attached (document name or link):

### 55. Who is our day-to-day contact, who is their escalation point, and how fast do they respond to a blocking issue during our working hours?

Answer:

Evidence attached (document name or link):

### 56. How many working hours will your team overlap with ours each day, and which meetings and ceremonies will your testers attend live?

Answer:

Evidence attached (document name or link):

### 57. What does your test completion report at the end of a release or phase contain, and can you show one?

Answer:

Evidence attached (document name or link):

### 58. How do you report flaky or unreliable automated tests, and how do you keep them from hiding real failures in our reports?

Answer:

Evidence attached (document name or link):

### 59. Will we have direct, read access to your test management data, defect tracker and automation results at all times, rather than only through reports?

Answer:

Evidence attached (document name or link):

### 60. How often will we review the service together, who attends from your side, and what data will those reviews use?

Answer:

Evidence attached (document name or link):

### 61. How will you tell us about risks you see in our product or process, such as untestable requirements or unstable environments, and how quickly?

Answer:

Evidence attached (document name or link):

---

## Commercials

_How you pay, what you get for it, and which remedies apply when service levels are missed._

### 62. Is your price based on time and materials, fixed price or outcomes, and exactly which activities are inside the price and which are billed separately?

Answer:

Evidence attached (document name or link):

### 63. If we pay for time, how are hours recorded, approved and evidenced on invoices, and can we see timesheets by person and activity?

Answer:

Evidence attached (document name or link):

### 64. Can you lock your rates for the initial term, and what is the mechanism and cap for any increase after that?

Answer:

Evidence attached (document name or link):

### 65. How do you handle change requests: who can raise them, how are they estimated and approved, and what happens to work that starts before approval?

Answer:

Evidence attached (document name or link):

### 66. Can you show how your price is built up, such as roles, seniority mix, rates, management overhead and tooling, so we can compare it with our own estimate?

Answer:

Evidence attached (document name or link):

### 67. What service credits or other remedies apply when an agreed service level is missed, and how are they calculated and applied?

Answer:

Evidence attached (document name or link):

### 68. What are your payment terms, and would you accept tying part of the payment to acceptance of deliverables or milestones?

Answer:

Evidence attached (document name or link):

### 69. What minimum commitment, notice period and early termination fees apply, and how can we scale the team down or up?

Answer:

Evidence attached (document name or link):

### 70. What insurance do you hold, such as professional indemnity, cyber and general liability, at what limits, and will you share certificates?

Answer:

Evidence attached (document name or link):

### 71. What limitation of liability do you propose, and are data protection breaches, confidentiality breaches and intellectual property claims treated separately?

Answer:

Evidence attached (document name or link):

---

## Exit and continuity

_How you leave, what you take with you, and which legal entity you are actually contracting with._

### 72. What exactly will you hand over when the contract ends: test cases, automation code, test data, environments configuration, defect history, documentation and credentials?

Answer:

Evidence attached (document name or link):

### 73. Will you agree a written exit plan within the first months of the contract, keep it updated, and test it?

Answer:

Evidence attached (document name or link):

### 74. How long a knowledge transfer period will you support at exit, what does it include, and how is it priced?

Answer:

Evidence attached (document name or link):

### 75. What notice period applies to termination for convenience and for cause, and will service levels continue to apply during the notice period?

Answer:

Evidence attached (document name or link):

### 76. When we take over or move the automation suite, can it run in our own pipeline without your licences, private libraries or internal tools?

Answer:

Evidence attached (document name or link):

### 77. Who will own the intellectual property in test cases, scripts and documentation created for us, and will the contract assign it to us in writing?

Answer:

Evidence attached (document name or link):

### 78. How will you delete or return our data at the end of the contract, and will you certify that it is done?

Answer:

Evidence attached (document name or link):

### 79. How do you keep the service going if key people leave, fall ill or are moved to another client? What notice do we get and how do you replace them?

Answer:

Evidence attached (document name or link):

### 80. What is your business continuity plan for the delivery team, such as loss of an office, power, connectivity or a regional disruption, and when was it last tested?

Answer:

Evidence attached (document name or link):

### 81. Will you give us, and our regulators where relevant, the right to audit and access information during the contract and through the exit period?

Answer:

Evidence attached (document name or link):
