E2E tests that stop regressions, not releases
An end-to-end suite that fails at random ends up switched off, and then nothing protects production. We put Cypress or Playwright on the journeys that matter, wire the suite into your CI and make it usable by your developers and by their AI agents. If you need hands, we also provide the QA engineer.
Describe my needWhat you get
A suite on the journeys that earn money, or cost it when they break: sign-in, order, payment, creating a record. Not three hundred tests, the right ones.
Stable selectors placed in the application code, controlled test data and tests that do not depend on each other. Those three things, far more than the tool, decide whether a suite survives the first redesign.
A CI run on GitHub Actions, Azure DevOps or GitLab that blocks the merge when a journey breaks and attaches screenshots, videos or traces to the failure.
One short documentation page: what is covered, what is not, and how to add a test without us.
Cypress or Playwright
We ship on both and choose for your application, not out of habit. Playwright is stronger on parallelism and multiple tabs. Cypress is still the best at showing why a test failed.
A Cypress suite that works does not justify a migration. The budget goes to making the existing tests stable first. The full comparison is in the reading list at the bottom of this page.
Tests your AI agents can run
Your developers code with Claude Code, Cursor or Copilot. We built cypress-mcp, an open-source MCP server that lets the agent run Cypress tests, read a structured failure and rerun after a fix. We install it if your team wants it.
What the agent does not do: decide what deserves a test, choose the assertions, or judge that a green test proves the right thing. An engineer reviews every test before merge. The engineer is accountable for the result, not the tool.
Setup or team extension
Setup: a fixed, priced scope agreed before we start, usually the critical journeys, the CI and the documentation. The price depends on the number of journeys, the test environment and access to data. We give it after a conversation about your application, never before.
Team extension: a QA or frontend engineer joins your team at our public rates, EUR 150 a day for a junior profile and EUR 200 for an operational one, more for confirmed or senior profiles. Contract with JADEV GROUP in Belgium, engineering from our Rabat center.
When this is the wrong purchase
If your interface changes completely every month, an end-to-end suite will cost more to maintain than it protects. Start with unit and API tests.
If nobody on your side will look at a red CI, no suite will protect you, whatever the tool. First decide who stops a release when a journey breaks.
And if the only criterion is the lowest day rate, you will find cheaper elsewhere. What we sell is a suite that holds up over time.
Every profile has already shipped on the stack shown. Rates follow our public grid, EUR 150 to 450 a day by seniority.
- QA and E2E automation engineerCypress, Playwright, CI integration, regression suitesWrites and stabilizes the critical journeys, then wires the suite into CI.
- Frontend engineerReact, Next.js, Angular, TypeScriptAdds test selectors in the code and fixes what the suite uncovers.
- Cloud and DevOps engineerGitHub Actions, Azure, DockerMakes runs fast and reliable: parallelization, caching, test environments.
Frequently asked questions
- What is the starting rate?
- A QA engineer on your team starts at EUR 150 a day for a junior profile and EUR 200 for an operational one, following our public rate card. A fixed-scope setup is priced after a conversation about your application.
- How long until a first suite runs in CI?
- It depends on the number of journeys and access to a stable test environment. The timeline is in the proposal, once we have seen the application. We do not quote a duration before that.
- Can you take over an existing suite?
- Yes, that is the most common case. We first make the existing tests stable, then add coverage where it is missing.
- Do we have to use AI?
- No. cypress-mcp is an option for teams that already code with an agent. The suite runs and is maintained without it.
- Who owns the tests?
- You do. The test code lives in your repository and runs on your accounts, like the rest of your application.
Which journeys must never break?
Describe your application, your CI and what breaks today, without confidential code. We reply with a scope and a price.
Describe my need- Cypress MCP server: let the AI agent run your E2E testsCoding agents write Cypress tests but cannot run them. What we built to close the loop, and what production taught us along the way.
- Cypress vs Playwright: which one for your E2E testsI have shipped both to production. The architectural difference is real, but the tool is never what decides whether an E2E suite survives.
- Regression testing for critical user journeysCoverage protects nobody. Three rings of tests, a ten-minute rule, and the only metric worth putting on a wall.
- E2E testing a legacy web app: the prerequisitesJava 1.5, WebForms, PHP: an E2E test does not read your code, it looks at HTML. Here are the six prerequisites that actually matter, and the real limits.
- Business Software ModernizationYour business software works, but every change is harder. We scope a staged modernization with your team, preserving what still delivers value.
- ERP and CRM Integration ServicesA quote in your CRM, an order in your ERP, a payment elsewhere: we scope the flows that should connect your tools and the exceptions your team needs to handle.
- AI and chatbot engineeringModels integrated into software that has to run, with a straight answer on what will not work.
- Architecture & delivery auditA starting point for complex change: risks, costed scenarios and a practical roadmap.
- Data engineeringWarehouse, pipelines and reconciliation, so the numbers can be trusted.
- CTO as a servicePart-time senior technical leadership, to arbitrate without a full-time hire.
- IT staff augmentationNamed engineers inside your existing team, on a European working day, contracted through Belgium.
- Nearshore development teamA dedicated group that owns delivery end to end, from architecture through production support.
- Nearshore vs offshoreA straight comparison for European teams who already offshore and are weighing a move closer.
- Cloud migrationInventory, batched cutovers and a tested rollback, so the move does not depend on luck.
- Infrastructure as codeEnvironments described in code, reviewed and rebuildable, instead of configured by hand once and never again.
- Managed IT and cloudCloud, pipelines, domains, mail and access, held by the team that also knows the code.
- Shopify developmentFor Shopify stores that have to talk to an ERP, a stock system or a payment flow.