From the founders of CodeceptJS and Codeception

Custom test automation framework development for your stack, repository and CI

You have no test framework yet, or the one you have is slow, flaky, hard to extend, or understood by nobody since its author left. With test automation framework development, we design and set up the test framework your team writes tests on, or rework the one you have: structure, conventions, test data, reporting and CI runs, in your repository. The framework is chosen for your stack and your people, and the reason is written down. Zapple.Tech was founded by the founders of CodeceptJS and Codeception, two open-source testing frameworks. The result is ordinary code your team runs without us. It starts with a one-week framework audit.

Framework review worksheet, one product 2 passed 1 failed 1 review
  • Structure and conventions One layout for tests, and it is written down keep
  • Test data Data sits inside the test code and breaks when it changes move out
  • Runs in CI Tests run on every change, one after another split runs
  • Reporting Results reach the test management tool keep
Illustrative example of a framework review. Not client data.
  • Founders of CodeceptJS and Codeception
  • Founders of Testomat.io and Testomat.ai
  • 42 completed projects
  • 9 solutions developed
  • Since 2015
  • 4.9 out of 5 on Clutch

At a glance

What it is
Test automation framework development
First step
Framework audit About one week
You receive
A written framework decision (keep, rework or replace) with the reason +2 more
After that
Pilot Two to six weeks

What we test

Services in this area

  • A new framework set up for your stack

    For teams with no framework, or with a handful of loose scripts. The structure, conventions and helpers are set up in your repository, so your engineers can add tests the same way.

    • Chosen for your language, your product and the people who will write the tests
    • The reason for the choice is written down
  • Rework or migration of an existing framework

    For a suite that is slow, flaky or hard to extend. The audit marks each current test keep, rewrite or delete before anything is rebuilt.

    • Rework is the default; a migration to another framework is an option, not a given
    • Repair of single tests is test maintenance, a separate service
  • CodeceptJS and Codeception frameworks

    If your stack fits CodeceptJS or Codeception, open-source testing frameworks whose founders founded Zapple.Tech, the framework can be set up on one of them. Official support for each has its own page.

    • CodeceptJS support and Codeception support are separate services
    • Your existing framework is always the first candidate
  • A framework ready for AI agents

    If you want AI agents to draft or repair tests, the framework is laid out so they can. Agent work itself is described under end-to-end testing with AI agents.

    • An engineer reviews every change an agent makes
    • Only an AI provider you approve is used

When you need a new framework or a rework

This is for teams that will write most of the tests themselves and need the base to be right first. Typical situations:

  • There is no framework. Tests are loose scripts, or there are no automated tests yet, and the next ones should not be written the same way.
  • The suite is slow, flaky or hard to extend. Adding a test takes longer than writing it should.
  • The person who built it left, and nobody else understands how it works.
  • A migration is on the table, for example from an older tool to a current one, and you want it planned before it starts.

If you want us to write the tests as well, see automated test script development. If you want engineers inside your team, see hire test automation engineers.

What the test automation framework includes

The parts depend on your product. This is the list we go through in the audit.

  • Structure and conventions. Where tests, helpers and configuration live, and how a new test is added.
  • Helpers and page objects, including wrappers for your custom controls, such as grids.
  • Test data kept out of the test code, so changing data does not mean changing tests.
  • Environments and configuration. How the application under test is started and which environment a run uses.
  • Reporting into your test management tool.
  • Runs in CI, including parallel runs. Wiring them to your pipeline stages is described under CI/CD test automation.
  • AI agent set-up, if you want it, described under end-to-end testing with AI agents.

Build your own or start from an open-source framework

In test automation framework development, building from scratch costs three things: time, money and people. It also leaves a framework that depends on whoever wrote it, and when that person leaves, the framework becomes the problem. An open-source framework with a thin project layer on top (your conventions, your helpers, your wrappers) avoids most of that, which is why it is the usual starting point in the audit. The audit report says which applies to your product.

Choosing the framework

Your stack, your language and who will write the tests decide. Playwright, CodeceptJS and Codeception are examples of frameworks that fit different stacks. Zapple.Tech was founded by the founders of CodeceptJS and Codeception, open-source testing frameworks that other teams build their suites on, so we say so up front. The choice and the reason for it are written into the audit report. If Testomat.io or Testomat.ai, which the same founders also founded, is on your shortlist for test management, the report says so and applies the same criteria to every tool.

If you already use CodeceptJS or Codeception, official support is covered on the CodeceptJS support and Codeception support pages.

Test automation framework development: the patterns in plain words

Frameworks are often described by pattern. These are patterns, not products. A real framework mixes several.

Pattern What it means When it fits
Linear (record and playback) Steps are recorded or written in order, one script per scenario A short-lived check or a first proof of concept. It gets expensive to change as the suite grows
Modular The application is split into parts, and each part has its own reusable test module Products with clear areas that change independently
Library architecture Shared functions sit in a library that the tests call Teams that want one place to fix a step used by many tests
Data-driven The same test runs with different data from a file or table Many cases that differ only in input, such as forms and rules
Keyword-driven Tests are written as named actions that non-programmers can combine Teams where analysts or manual testers write part of the tests
Hybrid A mix of the above, picked to match the product Suites that have grown past one kind of test

The audit does not pick a pattern from this list. It looks at your product and your people first.

Handover: a framework your team runs without us

The framework is in your repository and is your code. We write down its conventions and walk your engineers through it in a handover session, so you can extend it without us. If you want us to keep extending or maintaining it, that is the ongoing step. If you do not, nothing is assumed. For repair of existing tests, see test automation maintenance.

When a new framework is the wrong choice

Running the framework at the right stages of your pipeline is covered under CI/CD test automation. If you are not sure which of these applies, the one-week framework audit comes first.

How an engagement runs

Start small, with a fixed scope

Each step has a defined scope, duration and deliverables. You decide after each one whether to continue.

  1. Step 1 About one week

    Framework audit

    The existing framework, suite and CI are reviewed. If there is none, we review your stack and the people who will write the tests. The scope is fixed before the week starts.

    You get

    • A written framework decision (keep, rework or replace) with the reason
    • Each existing test judged worth keeping, rewriting or deleting
    • A pilot plan that does not depend on us to carry out
  2. Step 2 Two to six weeks

    Pilot

    The framework is set up or reworked in your repository, with the first tests for one product area running in your CI.

    You get

    • Framework and first tests in your repository and your CI
    • Written conventions for adding a test
    • A handover session for your engineers
  3. Step 3 Monthly, or none

    Ongoing or handover

    Zapple.Tech extends and maintains the framework, or your team takes it over after the handover session. You decide after each step whether to continue.

    You get

    • A monthly report, if the work continues
    • Or a team that runs the framework on its own

From a test automation client

Always fast and professional. Exactly what we have needed for company with dynamic growing business. We were working together on automation testing framework.

Hennadii Bulakh Manager at Sixt/Ride, Germany More reviews

From a test automation client

Zappletech have provided us with software development and test automation services, both in terms of guiding the architecture, and implementing a lot of test case.

Chris McVittie Head of Technology, UK More reviews

FAQ

Questions buyers ask

What is a test automation framework?

A test automation framework is the code, conventions and tools that tests are written and run with. It decides how a test is structured, how it reaches the application, where test data lives, how results are reported and how the suite runs in CI. The tests themselves sit on top of it.

What are the advantages of a test automation framework?

Tests share the same helpers, so they look alike and are easier to read and extend. Test data is kept apart from test code. Results are reported in one place. A suite built on a framework can run in CI the same way every time. None of this makes tests correct by itself, and it does not remove the work of deciding what to test.

Should we build our own framework or use an existing one?

Usually an open-source framework plus a thin project layer. Building from scratch costs time, money and people, and it leaves a framework that depends on its author. A custom layer pays off where the product has something unusual, such as custom controls or a special way to start the application. The audit says which applies to you.

Which framework do you recommend?

It depends on your stack, your language and who will write the tests. Playwright, CodeceptJS and Codeception are examples of frameworks that fit different stacks. Zapple.Tech was founded by the founders of CodeceptJS and Codeception, so we disclose that. If Testomat.io or Testomat.ai, which the same founders also founded, is on your shortlist for test management, the report says so and applies the same criteria to every tool. The choice and its reason are written into the audit report.

Can you rework our existing framework instead of starting again?

Yes. The audit marks each current test keep, rewrite or delete, and the pilot plan follows from that. A migration to another framework is possible, but it is an option, not the default. If the current framework fits your stack, we keep it.

How long does it take to build a test automation framework?

A common order of work is source control and structure first, then learning the application, environments and test data, a small smoke suite, helpers for common actions, checks, and logging and reporting. Your product may change the order. The pilot sets up the framework with the first tests for one product area in two to six weeks. We do not state other figures, because they depend on your product.

Will we depend on you to run it?

No. The framework is ordinary code in your repository, with written conventions and a handover session for your engineers. You can extend it without us, or with another vendor.

What does it cost?

Prices are not published. The cost depends on whether the framework is new or reworked, how many platforms it covers, how it runs in CI and how results are reported. Describe your product and you get scope, timeline and a quote within one business day.

Start with a one-week framework audit

Tell us which product you test, what framework or tests you have today, if any, and what hurts. We reply within one business day with scope, timeline and a quote.

  • Founded by the founders of CodeceptJS and Codeception, open-source testing frameworks
  • Founded by the founders of Testomat.io and Testomat.ai
  • 42 completed test automation and infrastructure projects
  • 9 solutions developed in a variety of business domains
  • On the market since 2015
  • Rated 4.9 out of 5 on Clutch, from 7 client reviews

Prefer to talk first? Schedule a call

    We reply within one business day.