qa-e2e

Generate and execute Playwright E2E tests from user scenarios.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/gridi-ai/gridi-skills --skill qa-e2e
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-e2e
Source: https://github.com/gridi-ai/gridi-skills/tree/main/skills/qa-e2e
Command: npx skills add https://github.com/gridi-ai/gridi-skills --skill qa-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automatically translates user-provided test scenarios into Playwright E2E tests, writes the test code, executes tests against a real server, and generates bug reports for failures.

Core Features & Use Cases

  • Generate E2E test suites from test-case documents and application flows.
  • Execute tests against real backend/frontend environments, verify results, and produce bug reports when failures occur.
  • Use cases include full-stack login flows, user management, and critical business processes.

Quick Start

Provide test scenarios and run the workflow to generate, execute, and report on Playwright E2E tests.

Frequently Asked Questions about qa-e2e

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Playwright E2E tests from user scenarios?

You can automate Playwright E2E test generation by providing test-case documents and user scenarios, which the skill translates into executable test code, runs against real server environments, and produces bug reports for failures.

What is end-to-end test automation for real server environments?

End-to-end test automation for real server environments executes generated test suites against actual backend and frontend infrastructure to verify application flows, ensuring deterministic execution and validating critical business processes like full-stack login and user management.

Can I automatically generate bug reports from failed Playwright tests?

Yes, you can automatically generate bug reports from failed Playwright tests by executing the test suite against a real server and letting the workflow verify results, capturing failures and translating them into structured bug reports.

Does this E2E testing workflow support integration testing across full-stack login flows?

This E2E testing workflow supports integration testing across full-stack login flows, user management, and critical business processes by executing generated Playwright tests against real backend and frontend environments to verify application behavior.

What do I need to provide to start generating Playwright E2E test suites?

To start generating Playwright E2E test suites, you need to provide test scenarios or test-case documents and application flows, along with access to a real server environment where the generated tests will be executed and verified.