Synthetic Monitoring and E2E Testing: 2 Sides of the Same Coin
summary
Argues that the same code artifact validates user journeys in CI and production, demonstrating Playwright + Elastic Synthetics run from GitHub Actions to produce monitors-as-code that ping production every 10 minutes, emit JUnit reports, and store per-step metrics in Elasticsearch. Shows a login journey with token-based request calls, uses data-test-id locators to reduce brittleness, surfaces a red failing monitor with step-level durations and core web vitals, and warns that deployment drift causes noisy false alerts.
AI-written summary · about
chapters (12)
- 0:00Synthetic monitoring vs E2E testing
- 1:41Early career lessons
- 4:32Shifting left challenges
- 8:49E2E testing vs synthetic monitoring
- 13:03Playwright artifacts
- 16:13Playwright syntax tips
- 21:53Tests to monitors
- 24:43CI with GitHub Actions
- 26:30Elastic Synthetics diagnostics
- 28:57Alerting strategies
- 30:43Uniting teams
- 31:44Resources
related talks
30mSynthetic Monitoring and E2E Testing: 2 Sides of the Same Coin
26mSynthetic Monitoring and E2E Testing: 2 Sides of the Same Coin
40mMonitoring as Code: E2E Testing in Production with Playwright
23mSecure by Design: Rethinking Test Credentials for Synthetic Monitoring
40mDecoding Synthetic Monitoring: A Journey from E2E UI Tests to Service-Level Probes
44mSynthesizing Sanity with, and in Spite of, Synthetic Monitoring
44mUnleash Synthetic Monitoring with Supercharged Test Automations
01h 02mThe Art & Joy of Testing in Production