ui-testing

Automate Playwright UI tests for Frictionless apps and generate TESTING.md checklists.

7|3|Updated Dec 23, 2025

Search Tags:#testing #Playwright #UI automation #test documentation #Frictionless apps #QA workflow

Ready to run

npx skills add https://github.com/zot/frictionless --skill ui-testing-zot

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ui-testing
Source: https://github.com/zot/frictionless/tree/main/install/skills/ui-testing
Command: npx skills add https://github.com/zot/frictionless --skill ui-testing-zot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps QA teams automate Playwright-based UI testing for Frictionless apps, ensuring requirements are checked and documented without code fixes during tests.

Core Features & Use Cases

Automated Playwright UI tests against app requirements to verify features.
TESTING.md generation to record results, gaps, and a Known Issues section for later resolution.
Clear guidance for loading apps, navigating, and collecting test evidence with reproducible steps.

Quick Start

Always make sure you have base_dir from ui_status first. Then:

Find requirements: {base_dir}/apps/<app>/requirements.md
Check server: .ui/mcp status → get base_dir and url
Load app: .ui/mcp display("<app>")
Open browser: .ui/mcp browser OR navigate Playwright to {url}/?conserve=true
Create TESTING.md from requirements
Test each feature, update checklist
Document bugs in Known Issues section

Frequently Asked Questions about ui-testing

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

FAQPage Schema

How do I automate Playwright UI testing for Frictionless apps?▼

Automate Playwright UI testing by loading the Frictionless app via MCP, navigating to the specified URL, and verifying features against requirements.md to generate a structured TESTING.md checklist.

How do I generate test documentation for QA workflows?▼

Generate test documentation by executing Playwright UI tests against app requirements and recording the results, coverage gaps, and bug details in a structured TESTING.md file.

Does Playwright UI testing require fixing code during the test run?▼

Playwright UI testing for Frictionless apps does not require code fixes during the run; testers load the app, verify features, and document bugs in the Known Issues section for later resolution.

How do I document Known Issues when testing Frictionless apps?▼

Document Known Issues by navigating the Frictionless app with Playwright, verifying defined requirements, and recording any discovered bugs with reproducible steps in the dedicated TESTING.md section.

What is the best way to set up reproducible Playwright UI tests?▼

Set up reproducible Playwright UI tests by retrieving the base directory from ui_status, loading the app via MCP display, opening the browser, and creating a TESTING.md checklist from requirements.md.