What an honor it was to join the panel discussion hosted by LeadDev this week—alongside brilliant minds like Ole Lensmar, @Varun Awasthi, and our amazing & talented moderator Heidi Waterhouse.

Event Link: https://leaddev.com/event/how-teams-test-at-ai-powered-velocity

We tackled one of the most pressing questions in software today: How do we maintain quality and developer experience when velocity is being pushed to its limits—especially with AI tools accelerating the pace?
Here are a few of my favorite takeaways that resonated deeply:

🔍 Key Insights & Highlights

🌿 Orchestrating Tests in Cloud-Native Environments
Scaling test automation across Kubernetes and complex cloud infrastructures is no longer optional—it’s essential. We discussed patterns and practices that help achieve consistency and coverage without slowing things down.

🌿 Breaking Down Silos between QA, Platform, and Dev Teams:
Collaboration is critical. One recurring theme: embedding quality into every step, not isolating QA as a final gate. Cultivating shared responsibility ensures faster feedback loops and higher trust. LeadDev

🌿 Better Observability, Fewer Flakes:
Too often we drown in test noise. By improving observability—clearly distinguishing signal from noise—we can reduce flaky tests and focus on real quality signals. LeadDev

🌿 Developer Experience as a First-Class Concern:
Velocity is important, but not at the cost of a broken feedback loop. Optimizing for DX means tests must be fast, reliable, and integrated—so developers feel empowered, not burdened.

The depth of conversations, the invigorating questions, the connections made—all of it reaffirmed how powerful shared learning is.

A heartfelt thank you to the LeadDev team for inviting me and running such a seamless, high-impact event. And to my fellow panelists and everyone who joined the discussion: thank you for your insights, your challenges, and your curiosity. We grow by asking hard questions together!💡

Cheers,

Nishi