Breaking the Chain of Blame: How to Get True Test Observability?
summary
Uses Playwright to drive a Node.js app that imports a Pokemon by ID while emitting OpenTelemetry spans to a Jagger collector, and verifies traces with Tracetest.io-style checks. A failing import for ID 143 traces to an external pokeapi call using deprecated v1.9 — the test reproduces the error and pinpoints the third‑party failure. Examples include Playwright + Jagger traces, trace-based assertions for HTTP 200, specific span content, and DB latency thresholds.
AI-written summary · about
chapters (8)
- 0:00Test observability intro
- 2:50Blame game in testing
- 5:50Third-party API failure postmortem
- 6:12Test observability defined
- 8:20Trace-based testing
- 9:45Playwright test observability
- 13:17Key takeaways
- 14:52Q&A
