From the founders of CodeceptJS and Testomat.io
Your developers ship with AI. Your QA has to keep up.
When code lands faster than it can be tested, releases slip or defects escape. Our QA and test automation services help you release on schedule and catch defects before your users do: hands-on manual testing where judgement matters, automated tests drafted by AI agents and reviewed by an engineer before every merge, and evaluation of the LLM features you ship.
Reply within one business day with scope, timeline and a quote. Only tools and data you approve.
End-to-end suite
- Checkout with a saved card 2.1 s
- Log in with SSO Failing step healed on CI. Suggested change printed for review.
- Refund from order history 3.4 s
Agent-drafted tests
- Coupon applied at checkout Drafted from the test plan. Waiting for an engineer's review.
AI assistant evaluation
- Answer matches the refund policy 0.94
- Instructions pasted inside a ticket Prompt injection followed. The merge is blocked. 0.31
6 checks: 3 pass, 1 fail, 2 waiting for review
- Founders of CodeceptJS and Codeception
- Founders of Testomat.io and Testomat.ai
- 4.9 out of 5 on Clutch
- 42 completed projects
Teams that have worked with Zapple.Tech
What is closest to your situation?
Pick one. You will see the first step we would suggest, how long it takes and what you get.
- First step
- One-week QA audit of one product area
- What you get
- A written report on what is at risk and what to fix first, and a pilot plan you can run with us or without us
Automated tests are drafted by AI agents and reviewed by an engineer before every merge.
- First step
- Evaluation baseline for one AI feature, about one week
- What you get
- A dataset of the cases that matter, a measured baseline, and checks that run in your CI on every change
Evaluation measures how the feature behaves on the cases tested. It cannot prove the model will never give a wrong answer.
- First step
- AI readiness assessment, then a pilot on one real suite
- What you get
- A plan for where AI fits in your team's work, tools trialled on your own code, and training to run it
AI does not replace your testers' judgement. In the pilot, an engineer accepts, changes or rejects every AI output before it is used.
My developers really enjoyed the trainings and consulting done by Zappletech. We found the trainer very competent. Thank you guys!
- First step
- One-week exploratory test of one release
- What you get
- Bug reports with steps and evidence in your own tracker, and a written view of what to keep testing by hand and what to automate
Manual testing, including manual end-to-end testing, is a service in its own right, not an add-on.
The first step
A one-week QA audit, then you decide
If you know something is wrong with how you test but not what to fix first, the audit answers that in about a week, for one product area, and leaves you with a plan you own.
What we review
- Your tests: what they cover and whether the team trusts them
- Your pipeline: when tests run and what blocks a merge
- Your release process: how a build becomes a release
What you get
- A written report on what is at risk and what to fix first
- A scoped pilot plan you can run with us or without us
- The framework choice, with the reason
What stays in your control
- Only tools you approve, against test environments
- The environment, test data and AI provider agreed before the first run
- If one of our founders' tools is on a shortlist, the report says so and applies the same criteria to every other tool
A week shows where the risks are; it does not fix them. The audit covers the product area and suites you give us access to.
Each step has a defined scope, duration and deliverables. You decide after each one whether to continue.
Initially, Zapple Tech experts audited the client’s system, evaluated previous QA practices, and generated a list of tasks for further solutions.
The team then rewrote the tests, converted them to Playwright and TypeScript, and set up CI/CD and parallel runs.
Read the caseZappletech have provided us with software development and test automation services, both in terms of guiding the architecture, and implementing a lot of test case.
Published work
What we built for other product teams
Four projects described on this site. Figures are quoted as the case pages publish them.
-
Healthcare · UK · 5 people
Clinic management app
- The problem
- Test every version of a cross-platform web system from scratch and find defects before each release
- What was done
- Test architecture from scratch, about 2,000 automated test cases, API test chains for smoke checks, tests integrated into GitLab CI
- Result, as published
As a result, over 100 critical system errors were identified and eliminated.
-
EdTech · Australia and New Zealand · 2 people
School management platform
- The problem
- Test all system modules and prepare tests that cut the effort of future releases
- What was done
- Automated tests with Codeception, WebDriver and PHP, integrated into Jenkins CI, smoke tests for UAT environments
- Result, as published
Automatic tests covered 18 different modules of all versions of the School Management Platform.
-
USA · 2 people
Car rental and transfer platform
- The problem
- Build a test architecture from scratch and cover every level of a web and mobile product
- What was done
- API, web and mobile automated tests with CI/CD integration, plus sets of manual tests for end-to-end testing
- Result, as published
All levels of the web and mobile Car Rental Solution were covered with automatic tests.
-
Health tech · UK · 2 people
Private medicine software
- The problem
- A slow test cycle (over 40 hours, as published) and tests that did not catch enough
- What was done
- An audit of the existing QA practice first, then tests rewritten and converted to Playwright and TypeScript, CI/CD, parallel runs
- Description of work
- Started with an audit.
How the work is done
AI agents draft. Engineers decide what gets merged.
Our engineers use AI agents to draft and maintain tests. Every change is reviewed in a pull request before it is merged, and the tests run in your CI, in your repository.
Your testers keep the judgement calls. AI takes on drafting and repairs; people set the criteria and approve the result.
Why Zapple.Tech
From the founders of four testing tools
Many QA vendors now use AI testing tools. Zapple.Tech was founded by the founders of four of them: two open-source testing frameworks and two AI tools for testing.
- Founded by the founders of CodeceptJS and Codeception, open-source testing frameworks
- Founded by the founders of Testomat.io and Testomat.ai
-
CodeceptJS
Open-source testing framework for JavaScript
CodeceptJS support -
Codeception
Open-source testing framework for PHP
Codeception support -
Testomat.io
AI test management tool
-
Testomat.ai
AI agents for software testing
Do you have to use our tools? No. If an audit recommends a tool change and one of ours is on the shortlist, the report says so and applies the same criteria to the others.
Always fast and professional. Exactly what we have needed for company with dynamic growing business. We were working together on automation testing framework.
- Years of experience with automated tests and TestOps
- 9
- Test automation engineers and experts working on projects
- 32
- Completed test automation and infrastructure projects
- 42
- Solutions developed in a variety of business domains
- 9
Your options
Four ways to catch up, compared
Each is the right choice for some teams. The questions on the left are worth asking of any option, including us.
| Question | Hire in-house | A lower-cost QA vendor | An AI testing tool on its own | Zapple.Tech |
|---|---|---|---|---|
| Who does the testing work? | People you recruit, once hired | The vendor's testers | Your own team, alongside its other work | Our engineers and testers, in your process and your tools |
| Who reviews AI-written tests? | Your team sets the rule | Ask the vendor | Your team, if someone has the time | An engineer, in a pull request, before every merge |
| Where do the tests live? | Your repository | Ask before you sign | Depends on the tool | Your repository and your CI |
| How do you start? | A hiring process | Depends on the vendor | A tool trial | A one-week audit with a written report |
| What do you keep if you stop? | The people and their work | Ask before you sign | Whatever the tool lets you export | The tests in your repository, and a plan you can run without us |
| The right choice when | Testing is core to your business and you can wait to hire | The test cases are well defined and you will manage the vendor closely | Your team has the time and skills to run and review it | You want a first result in about a week, from a company founded by the founders of CodeceptJS and Testomat.io |
Services
QA and test automation services
Manual testing, test automation and AI testing, delivered as a project or by engineers who join your team.
Test with AI
Manual testing and automated tests for web, mobile, API and desktop, reviewed by engineers
Test AI
Evaluation of LLM features, chatbots and AI agents
Adopt AI
An audit, a workflow and training for your own QA team
Hire and outsource
Full outsourcing, team expansion or a dedicated team
Not ready to talk?
Check your release process: ten questions
Ten questions about how your team tests and releases today. You get a result for each area and a first step for every weak spot. Nothing is sent anywhere unless you choose to send it.
10 questions, one click each
- Releases
- Tests
- Pipeline
- AI
-
First step: Find where the last slipped release lost its time: waiting for testing, fixing what testing found, or re-testing after fixes. Each needs a different fix, so measure before you add people.
-
First step: List the last five production defects and, for each, the check that would have caught it before release. That list is your first set of tests to add.
-
First step: A suite nobody trusts gets ignored. Sort the failures of the last 20 runs into defect, test fault and environment fault. Fix or delete the tests that fail without a defect before writing new ones.
-
First step: Write down the five to ten journeys that would hurt most if they broke (sign-up, payment, the core task). Check them on every release, by hand at first if needed.
-
First step: Run at least the critical-journey tests on every pull request, so a breaking change is stopped where it was made, not found days later.
-
First step: Split the suite: a fast set that blocks the merge and a longer set that runs on a schedule. Try parallel runs before buying more hardware.
-
First step: Unstable environments and missing test data make any test fail, hand-written or AI-written. Give the tests their own data and reset it between runs.
-
First step: Tests your team cannot maintain become dead weight. Keep them in your repository, in a framework your developers know, and review them like product code.
-
First step: Apply the same review and the same test gate to AI-written pull requests. More code per day means the gate matters more, not less.
-
First step: Collect 30 to 50 real questions with the answers you expect, score the current version against them, and re-run that set before every prompt or model change.
Your result
-
Releases
No weak answers in this area.
-
Tests
No weak answers in this area.
-
Pipeline
No weak answers in this area.
-
AI
No weak answers in this area.
"In good shape" means 80% or more of an area's points, "Worth a look" 50 to 79%, "Start here" below 50%. These labels come from your own answers and the thresholds above. They are not an industry benchmark.
This is what a one-week QA audit looks at: your tests, pipeline and release process, with a written report on what to fix first.
FAQ
Questions buyers ask
How do we start, and how long does it take?
With an audit or an evaluation baseline for one product area or one AI feature. It takes about one week and ends with a written report. A pilot of two to six weeks follows if you want it. After each step you decide whether to continue.
What do we get at the end of the audit?
A written report on what is at risk and what to fix first, a scoped pilot plan you can run with us or without us, and the framework choice with the reason. After that you decide whether to continue.
How much does it cost?
Prices are not published. The quote depends on the scope, mainly how many product areas, platforms or AI features are involved and what tests already exist. Describe what you need in the form and we reply within one business day with scope, timeline and a quote.
Who reviews tests written by AI?
An engineer reviews every change in a pull request before it is merged. AI drafts and repairs; it does not decide what gets into your main branch.
Do you use AI tools on our code and data?
Only tools you approve. Agents and evaluations run against test environments, and the environment, the test data and the AI provider are agreed before the first run. If your rules say nothing leaves your environment, nothing does.
Will we be locked in?
The tests live in your repository and run in your CI. The pilot plan is written so you can run it without us, and you decide after each step whether to continue.
Do you still do manual testing?
Yes. Manual testing, including manual end-to-end testing, is a service alongside test automation. A tester works on your release and files bug reports with steps and evidence in your tracker.
Do we have to use CodeceptJS or Testomat.io?
No. If an audit recommends a tool change and Testomat.io or Testomat.ai is on the shortlist, the report says so and applies the same criteria to the other tools.
Can we hire QA engineers or a dedicated team instead of a project?
Yes. There are three models. In full outsourcing we take over testing for a product. In team expansion our engineers join your team remotely. A dedicated team works on your project with your staff, using the tools you provide.
What does Zapple.Tech do?
QA and test automation services in three areas. Test with AI: automated tests for web, mobile, API and desktop, drafted and maintained with AI agents and reviewed by engineers. Test AI: evaluation of LLM features, chatbots and AI agents. Adopt AI: an audit, a workflow and training that bring AI into your own QA team's work. You can also hire QA engineers or a dedicated team.
Request a QA audit quote
Tell us what you ship and what worries you. We reply within one business day with scope, timeline and a quote.
What happens after you send this
- You send the form: your situation and what you need tested, then your name and work email.
- Within one business day, we reply with a suggested first step, its scope, timeline and a quote.
- If you go ahead, the audit takes about one week and ends with a written report and a pilot plan you can use with us or without us.
- Rated 4.9 out of 5 on Clutch, from 7 client reviews
- 42 completed test automation and infrastructure projects
- Founded by the founders of CodeceptJS and Codeception, open-source testing frameworks
Prefer to talk first? Schedule a call
They helped us to close the positions and consult our team how to proceed further. High-quality quick feedbacks with the deep checking of the required tasks, professional approach, great understanding of the company's technologies and product, detailed reports.
One-week QA audit · written report
Request a QA audit quote