Playwright Regression Testing

Q: Why use Playwright Regression Testing on TypingMind?

Because you install it once and use it with any model. Playwright Regression Testing is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

Q: How do I install Playwright Regression Testing in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/fugazi/test-automation-skills-agents/tree/main/skills/playwright-regression-testing. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Q: Which AI models can use Playwright Regression Testing?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

Q: How many AI models can I use with Playwright Regression Testing?

As many as you like. As long as a model supports skills, you can use Playwright Regression Testing with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Q: Is the Playwright Regression Testing AI skill free?

Yes. It is published on GitHub by fugazi under the MIT license. You only pay your own AI provider for the tokens you use.

Q: What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

Q: How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Community

fugazi

playwright-regression-testing

Govern Playwright TypeScript regression suites across many tests. Use when asked to plan, select, tier, execute, or optimize suites with risk/change analysis, tags, CI/CD, sharding, flaky-test management, or suite-health metrics; not for authoring one UI spec. Keywords: regression strategy, smoke tests, test selection, CI pipeline, flaky tests, test sharding, impact analysis, git diff.

Overview

Publisher	fugazi
Repository	`test-automation-skills-agents`
Skill name	`playwright-regression-testing`
Stars	238
Forks	42
Bundled files	6
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
6 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by fugazi on GitHub. Read the source before you install it.

Installation

Install the Playwright Regression Testing AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/fugazi/test-automation-skills-agents/tree/main/skills/playwright-regression-testing

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/fugazi/test-automation-skills-agents.git /tmp/test-automation-skills-agents
mkdir -p .claude/skills
cp -r /tmp/test-automation-skills-agents/skills/playwright-regression-testing .claude/skills/playwright-regression-testing

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Playwright Regression Testing in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Playwright Regression Testing on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Playwright Regression Testing is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Playwright Regression Testing (TypeScript)

Strategy and best practices for automated regression testing of web applications using Playwright with TypeScript.

Activation: This skill is triggered when working with regression test strategy, test suite selection, test prioritization, CI/CD pipeline testing, flaky test management, test sharding, or optimizing test execution for web applications using Playwright.

When to Use This Skill

Plan regression suites with risk-based and change-based test selection
Organize tests into tiers (smoke, sanity, selective, full regression)
Optimize execution with parallelization, sharding, and time-budget strategies
Integrate with CI/CD using GitHub Actions pipelines
Manage flaky tests with quarantine, retry policies, and root cause tracking
Monitor suite health with execution time, flake rate, and detection metrics
Select tests after changes using git diff analysis and impact mapping

Do NOT Use For

Authoring a single UI spec or page-object model (use playwright-e2e-testing).
Driving a live browser interactively for debugging (use playwright-cli).
Selenium/Java regression suites (use webapp-selenium-testing).
API contract testing in isolation (use api-testing).

Prerequisites

Requirement	Details
Node.js	v18+ recommended
Playwright	`@playwright/test` package
TypeScript	`typescript` configured in project
Browsers	Installed via `npx playwright install`
Git	Required for change-based test selection
GitHub Actions	Recommended CI/CD platform

Quick Reference

Tiers: Smoke (<2min, every commit) → Sanity (<10min, every PR) → Selective (<30min, on merge) → Full (<60min, nightly/pre-release).

Key tags: @smoke, @sanity, @regression, @e2e, @api, @destructive — exactly one per test, never on describe() blocks. Domain-specific extensions (e.g., @a11y in accessibility skills) are allowed alongside, but only one execution tag per test.

CLI: npx playwright test --grep @smoke | --grep @regression | --grep-invert @destructive | --shard=1/4 | --last-failed

For full tier model, regression types table, and tag taxonomy, see references/regression-catalogs.md.

Red Flags

Treating flaky tests as "fixed" by adding retries or waitForTimeout — quarantine and root-cause instead.
Running the full suite on every commit — use tiered selection (smoke on commit, full nightly).
Quarantining tests silently with no tracking ticket — quarantine must be temporary and owned.
No change-based selection — running everything regardless of what changed wastes CI budget.
Ignoring suite-health metrics (rising duration, climbing flake rate) until they block releases.

References

Document	Content
Regression Strategy	Tier model (smoke→full), regression types, triggers, directory layout, test tagging and tag taxonomy
Regression Selection	Test selection (change-based, risk-based, historical, time-budget) and test naming conventions
Regression Best Practices	Locator priority, web-first assertions, test independence, `test.step()` reporting, complete worked example test
CI/CD Integration	GitHub Actions tiered pipeline, sharding, merge reports, Playwright config, performance optimization, CLI reference
Flaky Management	Retry policies, quarantine strategies, detection checklist, suite health metrics, troubleshooting

Verification

Smoke test subset identified — Tagged @smoke tests run in under 2 minutes
No test duplication — Each scenario tested exactly once at the appropriate level
Test isolation verified — Running tests in random order produces same results as sequential
Flaky test baseline established — All tests pass 5/5 consecutive runs

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Playwright Regression Testing AI skill do?

Why use Playwright Regression Testing on TypingMind?

Because you install it once and use it with any model. Playwright Regression Testing is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Playwright Regression Testing in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/fugazi/test-automation-skills-agents/tree/main/skills/playwright-regression-testing. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Playwright Regression Testing?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Playwright Regression Testing?

As many as you like. As long as a model supports skills, you can use Playwright Regression Testing with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Playwright Regression Testing AI skill free?

Yes. It is published on GitHub by fugazi under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Setup Matt Pocock Skills

mattpocock

CommunityPopular

Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

Tdd

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

To Spec

Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.

To Tickets

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Playwright Regression Testing (TypeScript)

When to Use This Skill

Do NOT Use For

Prerequisites

Quick Reference

Red Flags

References

Verification

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now