Skip to content
cccskills

Browse skills

8 skills (repositories by testdino-hq) · sorted by popularity

QA engineering workflows on top of Playwright. Use when a QA engineer asks to design test cases from a ticket, PRD or acceptance criteria, decide what to automate, write a bug report from a failing test or trace, convert manual test cases (TestRail, Xray, CSV) into Playwright specs with case-ID traceability, or review Playwright test code and pull requests.

The English summary is being prepared. Showing the original description.

testdino-hq/playwright-skill396Updated Oct 12, 2026

For frontend engineers authoring UI — how to make components reliably locatable by tests and AI agents. Covers the official Playwright locator priority, semantic/accessible markup first, and how to add valid, unique, stable `data-testid` attributes (naming convention, uniqueness in lists, stability rules) for React, Vue, Angular, and Svelte. Use when writing or reviewing components, or when an agent needs durable locators.

The English summary is being prepared. Showing the original description.

testdino-hq/playwright-skill396Updated Oct 12, 2026

Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or have explicit authorization to test.

The English summary is being prepared. Showing the original description.

testdino-hq/playwright-skill396Updated Oct 12, 2026

Current Playwright (1.64) patterns for writing, debugging, and scaling reliable test suites. Use for any Playwright task, even ones you think you know, because the guides cover APIs and CLI flags newer than most training data. Covers writing or fixing tests, locators, a failing or flaky test, a trace.zip or error message, playwright.config and projects, network mocking, auth, visual and accessibility testing, Docker and CI sharding, playwright-cli browser automation, Playwright Test Agents, page objects, migrating from Cypress or Selenium, and QA work: test case design, bug reports from failures, automating manual test cases, and reviewing tests. TypeScript and JavaScript.

The English summary is being prepared. Showing the original description.

testdino-hq/playwright-skill396Updated Oct 12, 2026

Step-by-step migration guides for moving to Playwright from Cypress or Selenium/WebDriver — command mappings, architecture changes, and incremental adoption strategies.

The English summary is being prepared. Showing the original description.

testdino-hq/playwright-skill396Updated Oct 12, 2026

Page Object Model patterns for Playwright — when to use POM, how to structure page objects, and when fixtures or helpers are a better fit.

The English summary is being prepared. Showing the original description.

testdino-hq/playwright-skill396Updated Oct 12, 2026

Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.

The English summary is being prepared. Showing the original description.

testdino-hq/playwright-skill396Updated Oct 12, 2026

Battle-tested Playwright patterns for writing and debugging reliable E2E, API, component, visual, accessibility, and security tests. Use when you need locator strategy, assertions, fixtures, network mocking, auth flows, trace debugging, or framework recipes for React, Next.js, Vue, and Angular. TypeScript and JavaScript.

The English summary is being prepared. Showing the original description.

testdino-hq/playwright-skill396Updated Oct 12, 2026