- QA engagement model
- The way a client and a QA provider agree to work together: who manages the testers, how long the commitment lasts and how the work is billed.
- Dedicated QA team
- A group of QA engineers assigned only to one client’s product, usually on an ongoing monthly basis.
- Staff augmentation
- Adding individual QA engineers to a client’s existing team, where they work under the client’s management and processes.
- Managed testing
- A model where the QA provider owns testing end to end, from strategy to reporting, and is accountable for agreed quality outcomes.
- Fixed-price project
- A testing engagement with an agreed scope, deliverables and end date, often used for launches, migrations or audits.
- QA consulting
- An expert review of a team’s QA process, tools and coverage that ends in a prioritised improvement plan.
- On-demand testing
- Testing booked per release or per test cycle, without a retainer or long-term commitment.
- Test cycle
- One complete round of planned testing on a specific build, such as a regression or pre-release cycle.
- Proof of concept (POC)
- A short pilot, one week at QAonTOP, that shows how a QA team works on your product before you commit.
- Hybrid engagement
- Using two or more engagement models at once, such as a dedicated core team plus on-demand testers for peaks.