skills.rest
V4-Company
V4-CompanyOFFICIAL
Explore all skills by this author →
WebsiteGitHub

marsai:dev-frontend-e2e

Orchestrate Playwright E2E tests across Chromium, Firefox, and WebKit.

2|Updated Apr 10, 2026
Search Tags:#testing#frontend#e2e#qa#playwright#cross-browser
One-click install
npx skills add https://github.com/V4-Company/marsai --skill marsai-dev-frontend-e2e
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: marsai:dev-frontend-e2e
Source: https://github.com/V4-Company/marsai/tree/main/dev-team/skills/dev-frontend-e2e
Command: npx skills add https://github.com/V4-Company/marsai --skill marsai-dev-frontend-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that every product designer flow has a Playwright E2E test, and that those tests run across Chromium, Firefox, and WebKit to prevent regressions in frontend behavior.

Core Features & Use Cases

  • Orchestrates end-to-end tests for frontend user flows across multiple browsers.
  • Validates that all flows defined by product designers are covered by E2E tests, including happy-path and error-path scenarios.
  • Integrates with the frontend development cycle gates (Gate 5) and supports optional inputs to tailor test scenarios (unit_id, implementation_files, user_flows_path, backend_handoff, gate4_handoff).

Quick Start

Provide unit_id and implementation_files, then trigger Gate 5 to generate and run cross-browser Playwright tests.

Frequently Asked Questions about marsai:dev-frontend-e2e

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

FAQPage Schema
How do I automate cross-browser E2E tests for frontend user flows?▼

Automating cross-browser E2E tests uses Playwright to execute frontend user flows across Chromium, Firefox, and WebKit. It generates test scenarios covering both happy-path and error-path validations with responsive viewport coverage to prevent frontend regressions.

Can I run Playwright E2E tests across Chromium, Firefox, and WebKit?▼

Yes, Playwright E2E tests run across Chromium, Firefox, and WebKit. The skill orchestrates cross-browser execution and responsive viewport coverage to validate that all designer-defined frontend flows function consistently without regressions.

What inputs are required to generate Playwright E2E test scenarios?▼

Generating Playwright E2E test scenarios requires unit_id and implementation_files as mandatory inputs. Optional inputs include user_flows_path, backend_handoff, and gate4_handoff to further tailor the automated test creation and validation workflow.

How do you validate both happy-path and error-path scenarios in frontend testing?▼

Validating happy-path and error-path scenarios in frontend testing involves a workflow with both automated and manual verification steps. The skill creates test scenarios that cover all product designer flows, executing them across multiple browsers to ensure comprehensive coverage.

What is Gate 5 in the frontend development cycle?▼

Gate 5 in the frontend development cycle is the stage where cross-browser Playwright E2E tests are orchestrated. It ensures every product designer flow has automated test coverage across Chromium, Firefox, and WebKit before progressing further.

Related Skills

Explore More Software Engineering Skills→
LerianStudioLerianStudio
4

ring:dev-testing

Enforce 85% unit-test coverage thresholds for Go, TypeScript, and Python acceptance criteria.

Official
Advanced
TurnaboutHeroTurnaboutHero
12

playwright-master

Automate browser testing and web scraping with Playwright across Chromium, Firefox, and WebKit.

Community
Intermediate
luanrodriguesluanrodrigues
2

bee:dev-cycle-frontend-vuejs

Orchestrate a 9-gate development cycle for Vue.js/Nuxt 3 frontend projects.

Community
Advanced
nekorush14nekorush14
4

playwright-testing

Automate Playwright end-to-end tests across Chromium, Firefox, and WebKit.

Community
Advanced