Testing Overview
The active test suite is testing-v2/. The original testing/ submodule is retained as a read-only reference but is no longer run or maintained. See Why We Replaced the Testing Suite for the full reasoning.
Active Suite — testing-v2/
Repo: testing-v2/ (submodule, separate git repo)
Cypress E2E tests written in BDD/Gherkin using @badeball/cypress-cucumber-preprocessor. One org under test by default: Nova Home Care (org ID 1, the system default).
Stack
| Tool | Version | Role |
|---|---|---|
| Cypress | 13.15 | Test runner & browser automation |
| @badeball/cypress-cucumber-preprocessor | 21.x | Gherkin/BDD support (maintained fork) |
| @bahmutov/cypress-esbuild-preprocessor | 2.x | Fast ESBuild bundler for step definitions |
| Cypress Mochawesome Reporter | 3.8 | HTML test reports |
Structure
testing-v2/
├── .env.example ← copy to .env (3 vars)
├── cypress.config.js
├── package.json
└── cypress/
├── e2e/features/
│ ├── 01_login/ ← login page and auth flow
│ ├── 02_dashboard/ ← post-login appearance checks
│ └── ... ← journeys added incrementally
├── pages/ ← Page Object Model
│ ├── LoginPage.js
│ └── DashboardPage.js
└── support/
├── e2e.js
└── step_definitions/
├── common/ ← shared auth / navigation steps
├── login/
└── dashboard/Running Tests
Full suite (headless):
docker compose run --rm e2e-v2Single feature folder:
docker compose run --rm e2e-v2 sh -c "npm install && cypress run --spec 'cypress/e2e/features/01_login/**/*.feature'"Single feature file:
docker compose run --rm e2e-v2 sh -c "npm install && cypress run --spec 'cypress/e2e/features/01_login/login.feature'"Coverage (current)
| Feature | Folder |
|---|---|
| Login page — elements, error, success | 01_login |
| Dashboard appearance — sidebar, logo, role, notifications | 02_dashboard |
See Migration Status for what is still to be ported from the legacy suite.
Legacy Suite — testing/ (reference only)
Repo: git@gitlab.com:nova-hc/mwe/v2/testing.git
Retained as a catalogue of the test journeys that were delivered at handover. Do not run it in CI. Do not fix bugs in it. When porting a journey to testing-v2/, use the corresponding feature file in testing/ as a spec reference only.
See Why We Replaced the Testing Suite for the list of problems found.