browser-qa

Automate browser-based QA for Tale platform using Playwright MCP.

20|5|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/tale-project/tale --skill browser-qa-tale-project
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser-qa
Source: https://github.com/tale-project/tale/tree/main/.claude/skills/browser-qa
Command: npx skills add https://github.com/tale-project/tale --skill browser-qa-tale-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Driving Tale's platform QA in a real browser to run the manual test guides, enabling deterministic validation of UI flows and reducing manual steps.

Core Features & Use Cases

  • Real-browser QA execution against Tale services/platform/tests/manual guides using Playwright MCP.
  • ARIA-based selectors and i18n-stable locators for robust tests, avoiding brittle CSS targeting.
  • Run→snapshot→act→wait→verify→record loop with traces and screenshots for clear defect reporting.

Quick Start

Launch the Playwright MCP workflow to execute the manual QA guides against a live Tale deployment.

Frequently Asked Questions about browser-qa

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

FAQPage Schema
How does Playwright automate end-to-end UI testing for web platforms?▼

Playwright automates end-to-end UI testing by orchestrating real-browser navigation to execute test plans. It uses ARIA-based element targeting and structured result recording to ensure repeatable validation of UI flows without manual steps.

How do I run browser QA tests against manual test guides using Playwright?▼

You run browser QA tests by launching the Playwright MCP workflow against a live deployment. The process follows a run, snapshot, act, wait, verify, and record loop to execute manual test guides and capture traces and screenshots for defect reporting.

Why should I use ARIA-based selectors instead of CSS for browser UI testing?▼

ARIA-based selectors provide robust browser UI testing by avoiding brittle CSS targeting. They use i18n-stable locators to target elements, ensuring test plans remain stable across UI changes and language variations during end-to-end validation.

Does browser QA require a live deployment to execute end-to-end test plans?▼

Yes, browser QA requires a live deployment to execute end-to-end test plans. The automated workflow uses the Playwright MCP server to drive real-browser navigation against the deployed services to validate manual guides deterministically.

What is the best way to ensure deterministic validation when automating browser QA?▼

The best way to ensure deterministic validation in browser QA is using deterministic run configurations with the Playwright MCP server. This approach standardizes real-browser navigation, ARIA targeting, and structured result recording for repeatable test execution.

What limitations exist when using ARIA locators for end-to-end testing?▼

A limitation of using ARIA locators for end-to-end testing is that elements must have proper ARIA attributes or semantic roles. The automation relies on i18n-stable locators, so custom UI components lacking these attributes may not be targetable during browser QA execution.