# Managed QA services: we run your testing and own the result, month by month

> Managed QA Services and QA as a Service | Zapple.Tech. Canonical page: <https://zapple.tech/services/managed-service/>

Your testers are stretched, releases keep outrunning testing, and you do not want to manage a QA team on top of everything else. With our managed QA services, Zapple.Tech runs your testing as an ongoing service: we plan it, test every release, maintain the automated checks and own the result within the scope we agree. You set the goals and make the release decision. The measures are agreed at the start and reported every month, with a written result after each release. It starts with a one-week QA audit of your current testing.

## What you can order

- **[Release testing and regression](https://zapple.tech/services/regression-automation-testing/)**: Every release is tested within the agreed scope, and the result is written up afterwards.
- **[Test automation built and maintained as part of the service](https://zapple.tech/services/automated-testing-maintenance/)**: The automated checks are written in your tools and kept current as the product changes.
- **[Manual and exploratory testing](https://zapple.tech/services/manual-testing/)**: New features get a person's attention before release, through exploratory sessions planned within the agreed scope.
- **[QA audit and proposed scope](https://zapple.tech/services/audit-and-assessment/)**: A fixed-scope review of how you test today, which is where the managed service scope comes from.

## When managed QA fits

Managed QA suits testing that is long-term, frequent and planned, the kind your team keeps losing to other work:

- **Testing keeps slipping.** Your people are busy shipping, so testing happens when someone has time.
- **You want an outcome, not a team.** You do not want to direct testers task by task.
- **Releases are frequent.** Each one needs the same checks, and the results need writing down.
- **Nobody reports on quality.** You cannot say what was covered in the last release.

If you want to direct the engineers yourself, managed QA is the wrong model. See the comparison below.

## What our managed testing services include

Within the scope we agree:

- **Test planning** for the product area in scope, starting from the [QA audit](/services/audit-and-assessment/).
- **Manual and automated testing:** [regression testing](/services/regression-automation-testing/) for each
  release, and [manual and exploratory testing](/services/manual-testing/) of new features.
- **Repeated manual checks moved to scripts** by the same team.
- **Reporting:** a written result after every release and a monthly report.

## Who decides what

| | You | Zapple.Tech |
|:--|:----|:------------|
| Goals and scope | You set them | We propose them after the audit |
| Priorities inside the scope | | We set them and plan the testing |
| Running the testing | | We do it and maintain the automated checks |
| Result against the agreed measures | | We own it and report on it |
| Release decision | You decide | We report what we found and what we did not cover |

Owning the result means the testing outcome and the agreed measures. It does not mean deciding when to release.

## How quality is measured and reported

Measures are agreed at the start, before any testing is reported against them. You get three things:

1. **A written result after every release:** what was tested, what failed, what was not covered.
2. **A monthly report** against the agreed measures.
3. **Release-by-release reviews and handover sessions** with your team.

Defects go into your tracker and test runs into your CI, so the report never holds news your developers have not seen.

## Managed QA versus outsourcing, a dedicated team or hiring

| Model | Who sets priorities | Who owns the result |
|:------|:--------------------|:--------------------|
| [Hire QA engineers](/services/hire-qa-engineers/) (team expansion) | You, task by task | You |
| [Dedicated QA team](/services/dedicated-qa-team/) | You | The team runs the testing; you decide on release |
| [QA outsourcing services](/services/qa-outsourcing/) (full outsourcing) | You, at project level | We run the testing and keep you informed; you decide on release |
| Managed QA | We do, within the agreed scope | We do, for the agreed measures |

If you only want the automation built, that is a narrower job. See
[test automation outsourcing](/services/automated-qa-outsourcing/). For the full range of automation work, see
[test automation and QA testing services](/services/).

## Where AI speeds up managed QA, and where engineers decide

We use AI tools to draft test cases, automated tests and repairs. In a service measured every month, that is a trap as well as a help: a suite padded with drafted
tests can make a coverage number look better while checking less.

So an engineer reviews every change before it is merged, and decides what is worth testing. Only tools you approve
are used. How agents draft and repair browser tests under engineer review is described under
[end-to-end testing with AI agents](/services/agentic-e2e-testing/).

Zapple.Tech was founded by the founders of CodeceptJS and Codeception, open-source testing frameworks, and of
Testomat.io and Testomat.ai. The tools for your service are chosen for your product, not from that list by
default, and the choice is written into the audit report with the reason.

## What managed QA does not solve

Managed QA moves the running of testing to us. What your product should do, and when it ships, are still your calls.

- The vendor owns testing, not your product decisions. What quality means for your product and when to release stay with you.
- Measures cover only what was agreed in scope. Anything outside the scope is neither tested nor measured.
- Unstable environments and missing test data cause failures that the test side cannot fix alone.
- Handing over testing does not remove the need for the unit tests your developers write.
- The first weeks need someone on your side who knows the business rules and can answer questions.

## How the work runs

1. **QA audit** (About one week): We review your current testing, tools, environments and release process, and propose what a managed service would cover.
2. **Pilot** (Two to six weeks): One product area is tested in your tools and reported against the measures agreed with you. It is the trial run of the service itself.
3. **Managed service** (Monthly): Testing of every release within the agreed scope. You decide after each step whether to continue.

## FAQ

### What are managed QA services?

Managed QA, also called QA as a service, QA managed services or managed testing services, means a vendor runs your testing as an ongoing service and owns the result within an agreed scope. We plan the testing, test every release, maintain the automated checks and report every month. You set goals and decide on release.

### How is managed QA different from QA outsourcing or a dedicated team?

In the other models you keep the testing priorities, whether task by task, by team or at project level. In managed QA you hand them over within the agreed scope, and we answer for the result against the agreed measures. QA outstaffing is the opposite end, with engineers under your management. The comparison table on this page links to each model.

### How do you measure and report quality?

Measures are agreed with you at the start, for your product, and reported every month. They can be, for example, coverage of the critical journeys, defects found before release and the number of flaky tests. After each release you also get a written result of what was tested, what failed and what was not covered.

### Who does the testing?

Zapple.Tech testers and test automation engineers, with one named contact on our side. Team size is agreed after the audit and reviewed with you as the product changes.

### What do we still have to do ourselves?

Set the goals and the scope, give access to your tools, test accounts and a test environment, answer product questions in the first weeks, and decide on each release. Team size is reviewed with you as the product changes.

### Can we start with one product area, and how soon?

Yes. The one-week audit comes first, then a pilot on one product area for two to six weeks, and you decide afterwards whether to continue. The start date is agreed in the quote and depends mostly on how soon access and a test environment are ready.

### What is the term, and how do we leave?

Term and notice are set in the contract. The automated checks live in your repository, the defects and reports in your tracker, and a handover session is part of the service.

### Does managed QA include test automation?

Yes, as well as manual and exploratory testing. We write and maintain the automated checks in your tools as part of the service. If you only want an automation project with a defined suite, see test automation outsourcing.

### How do you use AI in managed QA?

AI drafts test cases, tests and repairs, and an engineer reviews every change before it is merged. Only tools you approve are used. Nothing leaves your environment if your rules say so.

### How is managed QA priced?

Prices are not published. The quote states scope, term and price. Describe the product and you get a scoped proposal within one business day.

[Request a managed QA proposal](https://zapple.tech/services/managed-service/#start)
