The suite is full of cy.wait calls
A previous team reached for cy.wait every time something flaked, and now every test blocks on fixed timeouts that hide the real behaviour.
Waits replaced with assertions
Running Cypress?
A Cypress suite that spent a year accumulating cy.wait calls and defaultCommandTimeout bumps stops being a test suite and becomes a wall of ignored red. We read the retries, remove the waits that are hiding real bugs, and leave you with a shorter suite you can genuinely rely on at the end of a release.
What it is
Cypress is a JavaScript end-to-end testing framework for web applications, released by Brian Mann and Cypress.io in 2017. It runs tests inside the browser itself rather than driving one remotely, which gives it direct access to the application's state and a runner window where tests play back step by step. Along with the open-source runner, Cypress Cloud provides a dashboard, parallelisation and flake detection as a paid service.
Cypress 10 restructured how tests are configured, Cypress 12 removed the experimentalSessionAndOrigin flag and made cy.session and cross-origin support production features, and recent versions added better component testing for React, Vue, Angular and Svelte. The runner is tightly tied to Electron and Chromium, and Firefox and WebKit coverage are less polished than in Playwright.
The honest version
No technology is all upside. This is where Cypress earns its place and where it tends to cause trouble.
Sound familiar?
The Cypress problems that bring people to us, and what you have once each one is fixed.
A previous team reached for cy.wait every time something flaked, and now every test blocks on fixed timeouts that hide the real behaviour.
Waits replaced with assertions
Cypress Cloud is retrying failing tests three times by default, which hides regressions behind a green badge until a customer surfaces them in production.
Retries tuned, real failures visible
A URL pattern no longer matches after an API refactor, so cy.wait on the intercept hangs forever and the test reports a timeout rather than a bad mock.
Intercepts pinned, mocks honest
A combination of extra parallel machines, retention tiers and flaky test retries has quietly doubled the Cypress Cloud invoice over a couple of quarters.
Spend aligned with real suite needs
experimentalSessionAndOrigin was removed in Cypress 12, and the suite is still using the old shape. Login steps are being repeated per test at a huge time cost.
cy.session in place, login once per spec
Memory leaks from long specs, large payloads being captured in snapshots, or extensions loaded into the test browser are pushing it over the edge during CI runs.
Memory contained, browser stable
A sprawling tests directory, a lot of green noise, a smaller amount of red that everybody ignores, and nobody whose job it is to look at the Dashboard every morning.
Suite trimmed, ownership defined
A test that touches an OAuth provider or an embedded Stripe iframe falls apart because cross-origin support was never configured correctly for the suite.
Origins configured, flows end to end
What we do
Call us for one unstable suite, or let us take the whole testing pipeline in hand.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Yes, and this is the most common job we take on. We read the retry history from Cypress Cloud or CI, classify each flake as a real bug, a test-code race or an infrastructure issue, and apply the right fix for each. Most suites come back to under a one percent flake rate within a week or two.
Sometimes. If you need WebKit coverage, better cross-origin support, or a faster parallel runner, Playwright is a clear win. If your suite is mostly Chromium flows and the team knows Cypress well, we often get more value from stabilising what you have than from a full migration.
The common causes are more parallel machines than the suite actually needs, retries left on for every test, and generous retention of recordings. We review the Cloud usage, show you where the money is going, and typically reduce the invoice without slowing CI down meaningfully.
Yes. We wire it into GitHub Actions, GitLab CI or CircleCI with the right Docker image, cache configuration, parallelisation, artifact uploads and failure screenshots. If you want Cypress Cloud it integrates on top; if you prefer to stay on the open-source runner, we keep the setup pure.
Yes. We replace cy.wait calls with assertions on application state or network interceptions that resolve when the work is actually done. The suite usually gets faster and more reliable at the same time, because the waits were covering for something specific we now handle directly.
The quote itself is at no charge. Share a recent CI run and the config file, and we come back with a number before any changes are proposed.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: