skills.rest
medtrics
medtricsOFFICIAL
Explore all skills by this author →
Website𝕏@medtricslabGitHub

15-TEST-e2e-discover

Explore web application routes and generate a structured FINDINGS.md report.

Updated Aug 23, 2026
Search Tags:#documentation#qa#playwright#e2e testing#bug discovery#ui exploration
One-click install
npx skills add https://github.com/medtrics/medtrics-acumen --skill 15-test-e2e-discover
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 15-TEST-e2e-discover
Source: https://github.com/medtrics/medtrics-acumen/tree/main/templates/shared/skills/15-TEST-e2e-discover
Command: npx skills add https://github.com/medtrics/medtrics-acumen --skill 15-test-e2e-discover

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of thoroughly exploring a web application's user interface, identifying bugs, and documenting interactive elements to streamline the testing and fixing workflow.

Core Features & Use Cases

  • Comprehensive UI Exploration: Navigates through all pages and interactive elements of a feature.
  • Bug Detection: Identifies issues like untranslated text, broken navigation, and form validation errors.
  • Element Inventory: Catalogs all interactive elements with suggested Playwright locators.
  • Use Case: Before writing automated end-to-end tests, use this Skill to perform a manual QA-style exploration of a new feature, ensuring all user flows, states, and potential bugs are documented.

Quick Start

Use the 15-TEST-e2e-discover skill to explore the user interface of the '/settings' route and document all findings.

Frequently Asked Questions about 15-TEST-e2e-discover

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

FAQPage Schema
How do I automate end-to-end UI exploration to find bugs before writing tests?▼

You can automate end-to-end UI exploration by scanning all routes within a feature, testing forms and states, and generating a structured FINDINGS.md report to document discovered bugs and interactive elements.

What types of bugs can automated UI exploration detect in web applications?▼

Automated UI exploration detects untranslated text, broken navigation, and form validation errors. It catalogs all interactive elements with suggested Playwright locators to streamline subsequent bug fixing and test writing workflows.

Do I need browser automation tools to run e2e UI discovery for web applications?▼

Yes, e2e UI discovery requires browser automation tools to navigate and interact with the application. These tools enable the Skill to automatically explore pages, test interactive elements, and document findings for QA workflows.

Can I use this automated QA exploration to catalog Playwright locators for interactive elements?▼

Yes, the automated QA exploration catalogs all interactive elements with suggested Playwright locators. It navigates through pages and forms to inventory elements, streamlining the transition from bug discovery to writing automated end-to-end tests.

What's the best way to document all user flows and states when testing a new feature?▼

The best way to document user flows and states is performing a QA-style exploration that navigates all pages and interactive elements, automatically generating a structured FINDINGS.md report to ensure potential bugs are documented for fixing.

Related Skills

Explore More Software Engineering Skills→
FilipcsupkaFilipcsupka

browser

Automate browser navigation, interaction, and data extraction via MCP tools.

Community
Intermediate
vanhoangkhavanhoangkha

playwright

Develop Playwright E2E tests using the Page Object Model.

Community
Intermediate
xxziikoxxziiko

playwright-e2e

Automate Playwright end-to-end test execution and debugging across projects.

Community
Intermediate
KSD-COKSD-CO
11

qa-only

Generate structured QA reports with health scores and reproducible steps for web applications.

Official
Intermediate