cs-pw_skill

This skill helps you accelerate end-to-end Playwright testing by generating, reviewing, and fixing flaky tests, and migrating from Cypress or Selenium.
  • Python

2.6k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill cs-pw

  • _meta.json279 B
  • SKILL.md5.0 KB

Overview

This skill is a production-grade Playwright testing toolkit that generates, reviews, fixes, and runs reliable end-to-end tests. It streamlines Playwright adoption, migrates suites from Cypress/Selenium, and integrates with TestRail and BrowserStack for CI-grade reporting. The toolkit includes templates, agents, and smart checks to reduce flakiness and enforce best practices.

How this skill works

It inspects your project to detect or scaffold Playwright configuration, then generates tests from user stories, URLs, or components using reusable templates. It reviews generated tests for anti-patterns, diagnoses flaky failures, and applies fixes or migration mappings. Optional connectors sync test cases with TestRail and run cross-browser jobs on BrowserStack, while reporting tools produce CI-ready reports.

When to use it

  • Bootstrapping Playwright in a new or existing web project
  • Generating tests from user stories, pages, or components
  • Fixing flaky or failing Playwright tests discovered in CI
  • Migrating test suites from Cypress or Selenium to Playwright
  • Syncing test cases and results with TestRail or running on BrowserStack

Best practices

  • Run /pw:review immediately after generating tests to catch locator and assertion anti-patterns
  • Use semantic locators (getByRole, getByLabel) before CSS/XPath to improve resilience
  • Replace page.waitForTimeout() with web-first expect() assertions that auto-retry
  • Keep tests isolated with fixtures and avoid shared global state
  • Use baseURL in config and set retries=2 in CI, 0 locally; enable traces on first retry

Example use cases

  • Generate a login flow test from a user story and auto-fix locator issues before commit
  • Diagnose a flaky checkout test in CI and replace brittle waits with stable assertions
  • Migrate an existing Selenium suite to Playwright and run coverage checks to confirm parity
  • Push automated test results into TestRail and launch cross-browser runs on BrowserStack
  • Scaffold Playwright config, CI pipeline, and a first smoke test for a new repo

FAQ

Yes. Use the migrate command to translate common patterns and then run coverage checks to verify parity before decommissioning the old suite.

How does it reduce flaky tests?

It enforces web-first assertions, replaces hard timeouts, suggests semantic locators, adds retries/traces in CI, and can automatically apply fixes for common flakiness patterns.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational