End-to-end tests
Technical checks show whether services run. End-to-end tests show whether users can actually work: a real browser performs typical user journeys at a fixed interval and measures every step.
How it works
- Tests are written with Cypress and run in a headless browser at a fixed interval (e.g. every 5–15 minutes) against each environment.
- Each test logs in with a dedicated test user, performs its steps and cleans up afterwards.
- Failed runs keep screenshots and a video of the browser session for analysis.
Results and alerting
- Dashboards show availability and response time per scenario and step over time.
- Alerts are raised when a step fails or exceeds its target time, routed like all other alerts.
- Comparing step times with the metrics of OTDS, Content Server, Search, Archive Center and the database shows which component causes a delay.
Further reading
handel gmbh · otwatch documentation · Last updated 19 October 2026