test-ui

Run Playwright UI smoke tests and output a PASS/FAIL report.

31|5|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/NSEvteev/FullSpec --skill test-ui-nsevteev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-ui
Source: https://github.com/NSEvteev/FullSpec/tree/main/.claude/skills/test-ui
Command: npx skills add https://github.com/NSEvteev/FullSpec --skill test-ui-nsevteev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Playwright UI smoke tests are prone to human error and slow feedback cycles; this Skill delegates their execution to a dedicated agent, providing reliable, repeatable checks and quick visibility through screenshots and a PASS/FAIL report.

Core Features & Use Cases

  • Delegates execution to test-ui-agent (Playwright CLI) for deterministic UI smoke runs.
  • Captures screenshots and generates a PASS/FAIL report for quick validation.
  • Suitable for CI pipelines and local workflows to verify UI stability after changes.

Quick Start

Run the /test-ui command to execute a Playwright UI smoke test and produce PASS/FAIL results.

Frequently Asked Questions about test-ui

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

FAQPage Schema
How do I automate Playwright UI smoke tests in a CI pipeline?

Playwright UI smoke tests are automated by delegating execution to a dedicated agent that runs deterministic checks against your web app and outputs a PASS/FAIL report for CI validation.

Can I capture screenshots during automated UI smoke testing?

Automating UI smoke testing captures screenshots during execution to provide quick visual validation and reliable reporting of application stability after changes.

What is the best way to validate UI stability after changes to a web dashboard?

The best way to validate UI stability is running automated smoke tests that execute deterministic UI interactions and generate a PASS/FAIL report for quick visibility.

Do I need Playwright installed to run automated UI smoke tests?

The execution relies on the Playwright CLI to drive interfaces against a running application, requiring the application to be active for accurate smoke testing.

Why does my UI smoke test report show a failure after minor code changes?

A UI smoke test reports a failure when deterministic checks detect application instability, helping prevent human error and slow feedback cycles by validating UI behavior after changes.