e2e-test

Automate Playwright end-to-end tests to validate runtime browser behavior.

Updated Dec 11, 2025
One-click install
npx skills add https://github.com/semicolon-devteam/semo --skill e2e-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-test
Source: https://github.com/semicolon-devteam/semo/tree/main/packages/eng/nextjs/skills/e2e-test
Command: npx skills add https://github.com/semicolon-devteam/semo --skill e2e-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

브라우저 레벨에서의 기능 검증을 자동화하고, 주요 유저 흐름의 회귀를 방지합니다.

Core Features & Use Cases

  • Dev 서버 확인: 로컬 개발 서버 상태 확인.
  • Playwright로 네비게이트: 페이지 접근 및 상호작용 테스트.
  • 결과 리포트: E2E 테스트 요약과 스크린샷 저장.

Quick Start

로컬 서버를 실행하고 Playwright를 통해 페이지를 탐색합니다.

Frequently Asked Questions about e2e-test

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

FAQPage Schema
How do I automate end-to-end testing with Playwright for my web application?

End-to-end testing with Playwright automates browser-level validation of user workflows by navigating pages, interacting with UI elements, and capturing results. This Skill configures Playwright to test page load, rendering, console errors, component behavior, and responsive layouts, then generates standardized reports and screenshots.

Can I use Playwright to test my local development server?

Yes, this Skill includes dev server readiness checks that verify your local development server is running before executing browser tests. It navigates pages, validates element visibility and interactions, and captures console logs to confirm server functionality.

What does e2e testing validate that unit tests don't cover?

End-to-end testing validates runtime browser behavior across full user journeys—page navigation, UI rendering, console errors, element interactions, and responsive layouts—catching integration issues unit tests miss. This Skill automates these checks during post-implementation verification and pre-merge validation.

How do I get screenshot and test report output from Playwright tests?

This Skill generates standardized test reports with screenshots and console log capture, storing results in a structured format. Output includes test summaries and visual evidence of page state, enabling debugging and documentation of test runs.

When should I run e2e tests in my development workflow?

E2E tests fit three stages: post-implementation verification before merge, PR pre-merge checks to prevent regression, and runtime validation after deployment. This Skill automates these checks to catch user-facing issues early without manual browser testing.