pagoda-e2e-verify

Automate browser-based end-to-end verification of Pagoda UI using git context.

29|19|Updated Jan 24, 2020
One-click install
npx skills add https://github.com/dmm-com/pagoda --skill pagoda-e2e-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pagoda-e2e-verify
Source: https://github.com/dmm-com/pagoda/tree/main/.claude/skills/pagoda-e2e-verify
Command: npx skills add https://github.com/dmm-com/pagoda --skill pagoda-e2e-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Browser-driven integration testing of Pagoda/AirOne (FE+BE combined). Use when asked to verify in the browser, test the UI, check if it works, run a smoke test, perform a manual or end-to-end test, or to validate feature readiness. It can also respond to phrases in Japanese like 動作確認, ブラウザで確認, and 画面で試して, and it determines what to test from the current git diff context and drives browser automation to navigate pages, fill forms, click buttons, and verify results.

Core Features & Use Cases

  • Browser-driven tests that adapt to the changed areas by inspecting git context and selecting relevant UI paths to verify
  • Phase-based workflow covering pre-checks, change analysis, test execution, and cleanup to ensure repeatable results
  • Use cases include end-to-end UI validation after feature work, smoke testing before releases, and regression checks across Pagoda UI flows

Quick Start

Run browser-based end-to-end verification against the current UI using agent-browser and follow the Phase 1–4 workflow.

Frequently Asked Questions about pagoda-e2e-verify

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

FAQPage Schema
How do I automate browser-based end-to-end testing for Pagoda UI changes?

Browser-based end-to-end testing for Pagoda UI is automated by analyzing the current git diff context to identify changed areas and driving browser automation to navigate pages, fill forms, and verify outcomes across combined frontend and backend flows.

Can I run smoke tests before releases using git context analysis?

Yes, smoke testing before releases uses git context analysis to select relevant UI paths, executing a phase-based workflow from pre-checks to cleanup to validate feature readiness and ensure repeatable regression checks.

Does e2e verification require a specific browser automation tool?

E2e verification requires a browser automation tool such as agent-browser to drive the UI interactions, navigate pages, and click buttons during the test execution phase.

How does change-driven testing determine which UI flows to validate?

Change-driven testing determines UI flows to validate by inspecting the current git context and diff, automatically selecting relevant UI paths and browser actions to verify the modified frontend and backend integration.

What is the workflow structure for browser-driven integration testing?

The browser-driven integration testing workflow is structured into four phases: pre-checks, change analysis, test execution, and cleanup, ensuring repeatable end-to-end verification of Pagoda and AirOne UI flows.