skills.rest
fabiano001
fabiano001COMMUNITY
Explore all skills by this author →
GitHub

e2e-test-combined-flow

Automate end-to-end QA tests for the combined loan application flow using Playwright.

Updated Aug 6, 2025
Search Tags:#e2e#qa#reporting#playwright#browser#snapshots#test-automation
One-click install
npx skills add https://github.com/fabiano001/claude-config --skill e2e-test-combined-flow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-test-combined-flow
Source: https://github.com/fabiano001/claude-config/tree/main/skills/e2e-test-combined-flow
Command: npx skills add https://github.com/fabiano001/claude-config --skill e2e-test-combined-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually validating end-to-end flows for a combined loan application can be slow and error-prone.

Core Features & Use Cases

  • Automates end-to-end QA tests for the combined loan application funnel using headed Playwright runs.
  • Accepts structured <TEST_TO_RUN> blocks to drive tests, verify results, and produce a structured report including snapshots.
  • Enforces safe automation boundaries by wrapping Playwright usage and providing deterministic test execution scripts.

Quick Start

Provide a <TEST_TO_RUN> block with TEST_NAME, TEST_URL, and VERIFY_ITEMS to run a test.

Frequently Asked Questions about e2e-test-combined-flow

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

FAQPage Schema
How do I automate end-to-end QA tests for a web application flow?▼

Automating end-to-end QA tests for a web application flow is handled by driving Playwright in headed browser mode using structured test blocks. You provide test names, URLs, and verification items to execute scripts and generate a structured results report.

What is needed to run Playwright browser tests for a loan application funnel?▼

To run Playwright browser tests for a loan application funnel, you need to provide a TEST_TO_RUN block containing TEST_NAME, TEST_URL, and VERIFY_ITEMS. This drives the headed browser execution and produces a structured report with snapshots.

Can I run ad-hoc Playwright CLI commands for test automation?▼

You cannot run ad-hoc Playwright CLI commands for test automation because the process enforces safe automation boundaries. It requires literal arguments and uses prebuilt scripts to ensure deterministic test execution and prevent unsafe direct CLI usage.

Does this approach generate test automation reporting with snapshots?▼

Yes, this approach generates test automation reporting with snapshots. After driving the headed browser tests via structured input blocks, it automatically verifies the specified items and outputs a structured results report including the captured snapshots.

Why use headed browser mode for end-to-end test automation?▼

Using headed browser mode for end-to-end test automation allows you to visually validate the combined application flow. It executes the prebuilt scripts deterministically while capturing visual snapshots for the structured QA report.

Related Skills

Explore More Software Engineering Skills→
fabiano001fabiano001

generate-test-run-blocks

Generate TEST_TO_RUN blocks for the e2e-test-combined-flow agent from Jira tickets or descriptions.

Community
Intermediate
mgeermgeer

qa-review

Run project tests and map results to an assertion checklist for a QA review report.

Community
Intermediate
neuron-oneneuron-one
25

e2e-tests

Automate end-to-end browser tests for user flows and visual validation across Playwright or Cypress.

Community
Advanced
AvatarGanymedeAvatarGanymede

e2e

Automate end-to-end web application testing with Playwright.

Community
Advanced