In 2026, our systems are too complex for our test suites to keep up. We spend weeks writing manual scripts for "known-unknowns," while the real disasters happen in the "unknown-unknowns" of production. If you are still relying on hard-coded assertions and mock data to tell you if your system is healthy, you aren't testing—you’re just hoping.

Traditional testing treats the "Lab" and "Production" as two different worlds. We shift-left to find bugs early, but we ignore the mountain of high-fidelity data sitting in our telemetry pipelines. As we move toward non-deterministic AI agents and micro-frontend architectures, the "Expected Result" is no longer a static value; it’s a living pattern of behavior.

Enter Observability-Driven Testing (ODT). This isn't just "testing in production"; it’s the evolution of the SDLC where production telemetry is the test oracle. In this session, we will explore how to use OpenTelemetry (OTel) and trace-based testing to bridge the gap. We will discuss how to transform production "traces" into automated integration tests, using real-user journeys to validate system correctness in real-time.

You will walk away with a blueprint for moving past "Is the button green?" to "Is the system behaving as the users taught it to?" We’ll cover how to implement ODT without breaking your budget or your SLAs.

From Assertions to SLOs: Learn why hard-coded assertEquals() is failing in 2026 and how to replace it with SLO-based assertions that account for latency, error rates, and system drift.

Trace-Based Testing (TBT): A deep dive into using Distributed Tracing as a test runner. Learn how to trigger a test and validate every microservice "hop" in the chain without writing a single mock.

The "Mirroring" Pattern: How to safely "shadow" production traffic to your staging environment to auto-generate regression suites based on actual user behavior.

Operationalizing the Feedback Loop: Practical steps to integrate tools like Grafana, Honeycomb, or OpenTelemetry directly into your CI/CD gate, turning "Mean Time to Discovery" into a metric that your QA team actually owns.

The "Spicy" Truth: Why the role of the "Manual Tester" is evolving into the "Quality Observability Engineer"—and the three skills you need to survive this transition.