Shift Left, Ship Ready: Automating E2E Tests Directly from Jira with Playwright MCP

Abstract:
Modern teams often treat automation as the final step of development—something that begins after a feature is “done.” The result? Automation lag, missed edge cases, brittle tests, and last-minute rework. What if automation could begin the moment an epic is written?

In this session, we’ll explore a practical workflow that integrates Jira with Playwright using MCP (Model Context Protocol) to transform epics and acceptance criteria into executable E2E sanity tests—while the feature is still under development.

Using Jira as the source of truth, we:

• Extract epics, stories, and acceptance criteria via MCP

• Convert requirements into structured sanity test plans

• Generate Playwright specs automatically

• Refine tests in parallel as the UI stabilizes

This approach enables QA and automation engineers to work alongside developers—not after them—reducing automation bottlenecks and surfacing ambiguity early.

You’ll see a live demonstration of:

• Fetching Jira epics using MCP

• Translating acceptance criteria into actionable test scenarios

• Generating Playwright test specs under a structured framework

• Iterating in headed mode as the UI evolves

• Producing actionable HTML reports for fast feedback

By the end of this session, you’ll learn how to:

• Shift automation left without increasing overhead

• Turn documentation into testable artifacts

• Deliver sanity coverage by the time the feature merges

• Build a scalable structure for AI-assisted E2E testing