skills.rest
nguyenpv1980-wq
nguyenpv1980-wqCOMMUNITY
Explore all skills by this author →
GitHub

clickthrough-test-engineer

Walk through a running application to find UI defects and verify route coverage.

2|Updated Jul 6, 2026
Search Tags:#ui testing#defect reporting#clickthrough#screenshot evidence#staging verification#browser walkthrough
One-click install
npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill clickthrough-test-engineer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clickthrough-test-engineer
Source: https://github.com/nguyenpv1980-wq/Project-Aegis/tree/main/.claude/skills/clickthrough-test-engineer
Command: npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill clickthrough-test-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a disciplined way to inspect a running application by driving it through realistic user flows, so you can find broken navigation, form issues, permission bugs, console errors, and unsafe destructive interactions before release.

Core Features & Use Cases

  • Route-by-route walkthrough planning: Builds a pre-click checklist for the screens in scope so coverage is explicit and measurable.
  • Interactive UI verification: Exercises navigation, valid and invalid form input, dialogs, permission-gated controls, empty states, loading states, error states, and confirmation flows.
  • Evidence-backed reporting: Captures screenshots at named checkpoints, records console findings, rates defects by severity, and reports what was completed versus skipped.
  • Use Case: A tester needs to smoke-check a staging build before a demo and quickly identify broken screens without creating a permanent automated suite.

Quick Start

Use the clickthrough-test-engineer skill to plan and execute a safe interactive walkthrough of the running app, then return a defect report with screenshots, console findings, and honest coverage.

Frequently Asked Questions about clickthrough-test-engineer

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

FAQPage Schema
How do I perform a UI walkthrough on a staging build to find visual defects?▼

Interactive UI verification exercises navigation, valid and invalid form input, dialogs, permission-gated controls, and empty or loading states. It logs console findings and rates defects by severity to report release readiness.

What is the best way to verify route coverage and capture screenshot evidence during a browser walkthrough?▼

This approach verifies route coverage by exercising navigation, invalid inputs, and permission checks. It captures masked screenshots at named checkpoints to ensure evidence-backed defect reporting and honest coverage tracking.

Can I do a manual staging smoke check without creating a permanent automated test suite?▼

It applies to staging smoke checks and release readiness reviews by performing a one-session interactive walkthrough. This finds broken navigation, permission bugs, and unsafe destructive interactions without requiring a permanent automated suite.

How do I safely test invalid inputs and permission-gated controls during UI testing?▼

It requires safe test accounts to exercise invalid form input, permission-gated controls, and destructive interactions safely. Console observation and masked screenshot evidence ensure severity-rated defect reporting without risking live data.

What should I do if my manual clickthrough test finds console errors and broken navigation?▼

It handles discovered console errors and broken navigation by capturing masked screenshot evidence at named checkpoints and rating defects by severity. This produces a defect report detailing what was completed versus skipped during the walkthrough.

Related Skills

Explore More Software Engineering Skills→
xlelibertyxleliberty

browserstack

Execute Playwright test suites on BrowserStack cloud infrastructure.

Community
Intermediate
supertyrellesupertyrelle

bug

Extract artifact, symptom, repro steps, expected behavior, and severity into structured bug reports.

Community
Advanced
johnlindquistjohnlindquist
24

ts-testing

Design and maintain TypeScript test suites with Jest, Vitest, Playwright, or Cypress.

Community
Advanced
betaTridentbetaTrident

browser-qa

Automate visual regression testing and UI interaction verification for web applications.

Community
Advanced