What is observability-driven development?
summary
Claims a practical workflow that replaces heavy mocking by asserting on OpenTelemetry spans using Trace test to trigger HTTP/gRPC, pull traces from Jaeger/Tempo/OpenSearch and evaluate span attributes and durations. Shows a real books+availability microservice, adds span attributes (books_count, available) and timing assertions (<500ms), and demonstrates failing and passing tests; the tool runs as CLI/server and integrates with existing tracing pipelines — concrete, runnable, and language‑agnostic.
AI-written summary · about
chapters (29)
- 0:00intro
- 0:21preface
- 0:51hi, i'm adnan
- 1:37today i will talk about...
- 2:28the pain of testing microservices
- 3:20here's how you solve it
- 4:05what is distributed tracing?
- 5:05out istributed system
- 6:06integration testing and tdd need help
- 6:34the pain points of tdd
- 7:38just to start tdd-based integration testing
- 8:01traditional integration test
- 10:00how observability-driven devleopment can help
- 11:08what is trace-based testing?
- 12:02observability-driven development in practice
- 12:12what is tracetest?
- 12:24why tracetest?
- 14:02how tracetest works?
- 14:31hands-on observability-driven development
- 15:52assert on timing
- 16:47assert on any part of an http transaction
- 20:01works with any distributed system with opentelemetry instrumentation
- 20:31tracetest triggers api, fetches response and trace data, runs assertions
- 20:54install tracetest
- 21:05installing tracetest cli
- 21:34what did we learn?
- 22:13let's recap
- 22:41thank you! any questions?
- 23:09tracetest community
related talks
43mObservability-Driven Development with Kubernetes
36mHow Testability Drives Observability
39mHow Testability Drives Observability
21mThe Road to Observability Everywhere at Monday.Com- 36mHow Testability Drives Observability
43mObservability Visualization in the Age of OpenTelemetry
53mObservability Driven Development
30m"Observability for the Front End"