Synthetic Monitoring and E2E Testing: 2 Sides of the Same Coin
summary
Demonstrates using Playwright tests stored in a repo as journeys as code, pushed by GitHub Actions to Elastic Synthetics via API keys so the same scripts run in CI, staging and production; monitors record screenshots, per-step durations and failures, letting teams add anomaly detection and SLOs. Shows a recorder that generates Playwright scaffolding, recommends environment-aware configs to avoid pointing monitors at localhost, and flags data cleanup or blue/green strategies for tests that mutate production data.
AI-written summary · about
chapters (9)
- 0:00Introduction and background
- 4:34Synthetic monitoring explained
- 6:21Tooling and workflow setup
- 9:27Writing monitors as code
- 13:59Test-driven development practices
- 15:43Deploying monitors via CI
- 17:48Multi-discipline collaboration
- 19:54Unified tooling benefits
- 20:40Q&A session
related talks
32mSynthetic Monitoring and E2E Testing: 2 Sides of the Same Coin
30mSynthetic Monitoring and E2E Testing: 2 Sides of the Same Coin
40mMonitoring as Code: E2E Testing in Production with Playwright
10mCreate, Run and Deploy end-to-end tests with Playwright and GitHub Actions
40mEnd to End Automation from a Developer Standpoint
49mReal World Lessons from Scaling Test Automation
11mHow to make cheap e2e tests
30mSynthetic Monitoring: Automating the User Experience for Continuous Improvement