Developers are increasingly taking ownership of testing. AI coding agents and frameworks like Playwright make it faster than ever to write tests alongside code—and for many teams, that feels like progress. But it leaves a critical question unanswered: who is actually accountable for quality?

Using AI coding agents with Playwright is a logical way to keep up with fast-paced development. This approach effectively answers one question: does this feature work in this pull request? However, it doesn't address a more difficult concern: are the end-to-end experiences that users rely on—across different flows and applications—still functioning as expected?

In this session, we'll cut through the hype and make the case that the rise of agentic development doesn't eliminate the QA role—it makes it more critical. Because the faster code ships, the more your organization needs someone who can tell when a passing test no longer reflects what the business actually needs it to validate.

You will learn:

• Why generating tests faster doesn't mean you can trust them more—and what it actually takes to know your quality signals are reliable.


• The three ways a Playwright + coding agent strategy quietly breaks down at scale, and how to spot them before they reach customers.


• Why the rise of agentic development actually expands the QA role rather than eliminating it—and what modern quality practitioners own that no coding agent can.