Automated tests · QA
How to set up automated tests
on an application
that has none?
Start with E2E tests on critical flows, not unit tests. With Cypress, I build a minimal viable coverage scaled to your application and integrate it into your CI/CD pipeline. I wrote 500+ Cypress scenarios for Citeo, reaching 70% coverage.
The right sequence
Where to start: E2E, unit, or integration?
Short answer: E2E tests first. Unit tests are faster to write but don't cover what matters most: does the complete flow work from the user's perspective?
For an application with no tests at all, 10 Cypress scenarios covering critical flows (sign-up, login, main action, payment) bring more value than 200 unit tests on isolated functions. It's counter-intuitive but proven in practice.
Integration and unit tests come later, on components with the most business logic. We build coverage from the outside in, not the reverse.
The process
From zero to viable coverage
Critical flows
Together we list the 5 to 10 user actions whose failure costs the most. These are the first scenarios to cover, without exception.
Cypress setup
Installation, configuration, naming conventions, reusable fixtures and commands. A clean foundation the team can maintain independently.
First scenarios
Happy path + main error cases for each critical flow. Each scenario is documented to serve as a template for the team.
CI/CD integration
Tests run automatically on every push. Without this step, the suite dies within weeks. I integrate with GitHub Actions, GitLab CI, or Azure DevOps.
Team training
I pass on the patterns, conventions, and reflexes so your team can write new scenarios without me. I trained 2 QA engineers at Citeo: they maintain the suite independently.
Concrete reference
Citeo · 4 years
I designed and implemented 500+ automated E2E test scenarios with Cypress on the Citeo platform, a high-traffic critical application.
Tests are integrated into the Azure DevOps pipeline. Result: 70% coverage, secured deployments, increased team velocity (Stéphane Bourdon, Head of IT, verified LinkedIn recommendation).
Same approach applicable to your stack (React, Vue, Angular, Symfony/Laravel applications).
Deliverable
What you receive
- Cypress test suite running on your critical flows
- Integration into your existing or new CI/CD pipeline
- Convention documentation for team continuity
- Training session (2 to 4 hours) for your team
- Guide for writing future scenarios
Go further
Other audit cases
First contact
Zero tests today?
We can change that. 30 minutes to assess your stack and define the first flows to cover.