e2e-page-validator

Automates end-to-end testing of web pages by exercising inputs and verifying backend service responses.

2|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/Shubh2310-developer/ENGUNITYCORE --skill e2e-page-validator-shubh2310-developer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-page-validator
Source: https://github.com/Shubh2310-developer/ENGUNITYCORE/tree/main/.claude/skills/e2e-page-validator
Command: npx skills add https://github.com/Shubh2310-developer/ENGUNITYCORE --skill e2e-page-validator-shubh2310-developer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually validating that a web page's forms, parameters, and backend API calls all work correctly is repetitive and error-prone. This Skill automates browser-driven exploration of a page, systematically tests its inputs, and confirms every network request succeeds. ## Core Features & Use Cases - Interactive Element Exploration: Navigates to a target URL in Chrome, lists all inputs, dropdowns, and buttons, and maps the happy-path user flow. - Parameter Testing: Tests each data-binding parameter with valid, missing, and invalid or extreme values such as long strings and special characters. - Service Verification: Monitors XHR/Fetch network traffic during interactions and logs any failed 4xx/5xx responses with request details. - Use Case: After deploying a new login or checkout page, run this Skill to confirm every form field behaves correctly, every backend call returns 2xx, and receive a test_report.md with screenshots of any failures. ## Quick Start Use the e2e-page-validator skill to test the page at the given URL and generate a full validation report.

Frequently Asked Questions about e2e-page-validator

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

FAQPage Schema
How do I automate E2E testing of a single web page?

Provide the target URL and let the Skill drive Chrome to explore the page, test every input with valid and invalid data, and monitor network calls. It produces a test_report.md summarizing parameters, service responses, and failures.

What does the E2E page validator check during a test run?

It checks interactive elements like inputs, dropdowns, and buttons, tests each parameter with valid, missing, and extreme values, verifies all XHR/Fetch calls return 2xx, and captures browser console errors and failure screenshots.

Can I test a page that requires login credentials?

Yes. The Skill includes credentials for the login page (a test user email and password) so it can authenticate before exploring protected pages. You would supply equivalent credentials for other environments.

What are the limitations of automated page validation?

It validates one target page per run and focuses on happy-path flows plus parameter edge cases. It does not replace full regression suites, load testing, or multi-page journey orchestration across an entire application.

Why do failed service calls get logged during page testing?

Every button click that triggers a network request is verified, and any 4xx or 5xx response is logged with request details. This surfaces backend integration bugs that a simple page-load check would miss.