How It Works
Interfaces with the Playwright MCP Server to execute test suites, stream live terminal output, and capture results. Supports CI/CD config generation for GitHub Actions and GitLab CI. Selector health analysis detects fragile locators and suggests resilient alternatives.
Configure Test Run
Available Tests ()
Overall
Passed
Failed
Duration
Failures
Run History
| Job ID | Pattern | Browsers | Passed | Failed | Duration | Status | |
|---|---|---|---|---|---|---|---|
|
|
||||||
| No test runs yet. Run your first test above. | |||||||
Overall Grade
Errors
Warnings
Files Analysed
Page Object Files
Issue Breakdown
| File | Grade | Errors | Warnings | Info | Selectors | ||||
|---|---|---|---|---|---|---|---|---|---|
|
|||||||||
|
|
|||||||||
Duplicated Selectors (extract to Page Objects)
used in files:
Generate CI/CD Pipeline Config
Generate Playwright API Tests from Jira Story
Fetches the story from Jira then generates an API .spec.ts
API tests use Playwright's
request fixture — no browser needed.
They run in <5s per test and test HTTP endpoints directly.
Best for stories that mention: REST, endpoint, JSON, payload, status codes, webhooks.
— try a story with API/endpoint keywords.
Detected context: