Results for “playwright”

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.

Test local web applications with Playwright, a browser automation tool. Check frontend functionality, investigate interface behavior, capture screenshots, and inspect browser logs, with a helper script that manages one or more application servers during testing.

• Checking buttons and forms in a local web app
• Investigating interface problems with screenshots and logs
• Testing with both frontend and backend servers running

Generate marketing screenshots with Playwright, a browser automation tool. Use the images for landing-page hero sections, App Store listings, or changelog visuals. The catalogue entry points to an upstream bundle containing the full workflow and supporting resources.

• Creating a landing-page hero screenshot
• Preparing screenshots for an App Store listing
• Creating visuals for changelog announcements

Test local web applications with Python scripts using Playwright, a browser automation tool. Verify interface behavior, investigate problems, capture screenshots, and inspect browser logs, with a helper that manages one or more application servers.

• Verify buttons, links, and form behavior
• Investigate problems in dynamic web interfaces
• Capture screenshots of local applications

Run repeatable tests of Cherry Studio’s key workflows with Playwright, which checks application behavior through automated interactions. Collect results on macOS and Windows and produce English reports for release acceptance or development validation.

• Checking key workflows before a release
• Validating application behavior on a development branch
• Running regression tests for a specific task

Create and improve Playwright end-to-end tests for Studio changes. Check complete user actions, including whether settings affect requests, data survives reloads, tools return expected results, and workflows pass data correctly.

• Testing whether agent settings affect actual requests
• Checking that saved data survives page reloads
• Verifying tool outputs and workflow data flow

Connect TestRail test cases with Playwright automated tests. Generate tests from documented steps, send execution results back, create test runs, and check which cases remain unlinked using case IDs recorded in each test.

• Generating Playwright tests from TestRail cases
• Sending automated test results to TestRail
• Creating a test run for regression testing

Creates test starters for React and Next.js applications and analyzes coverage reports to find untested code. Supports unit, integration, and browser-based tests, simulated API responses, reusable test data, and test runner configuration.

• Generating test starters for React components
• Finding untested code before a release
• Creating browser tests from Next.js routes

Automate website searches, logins, form entry, and price comparisons using Playwright, a browser automation tool. Provides workflows for locating page elements, checking results, and recovering from navigation errors or missing elements.

• Comparing product prices across online stores
• Filling and submitting web forms
• Logging in and checking the result

Test local web applications with Python scripts using Playwright, a browser automation tool. Verify interface behavior, investigate problems, capture screenshots, and inspect browser logs, with a helper that manages one or more application servers.

• Verify buttons, links, and form behavior
• Investigate problems in dynamic web interfaces
• Capture screenshots of local applications

Test local web applications with Python scripts using Playwright, a browser automation tool. Inspect rendered pages, exercise interface controls, capture screenshots and console logs, and use a helper to manage one or more application servers during tests.

• Verifying buttons, links, and form inputs in a local app
• Investigating unexpected interface behavior
• Capturing screenshots and browser console logs

Goal-driven E2E testing where a browser agent (Playwright MCP / computer-use) reads a natural-language goal and explores the app via the accessibility tree to assert outcomes — no pre-written script. Covers when intent-driven beats scripted, making agent runs deterministic (pinned model, temperature 0, seeded data, bounded steps, explicit success assertion, snapshot-not-pixel), cost/latency control, the accessibility-tree-first interaction model, CI gating, and graduating a stable run into a scripted Playwright test. Use when: "agentic browser test," "goal-driven browser test," "let an agent explore the app," "natural-language E2E," "browser agent smoke test," "Playwright MCP test." Not for: Writing/maintaining deterministic scripted Playwright tests — that is playwright-automation. Testing your product's OWN LLM features — that is ai-system-testing. Related: playwright-automation, ai-system-testing, exploratory-testing, test-reliability, qa-project-context.

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

Record web application demos with Playwright, a browser automation tool. The workflow explores the interface, rehearses each step, and produces WebM videos with visible cursor movement, subtitles, and readable pacing.

• Creating a video walkthrough of a new feature
• Recording tutorials for new users
• Adding operation videos to documentation

Automate website navigation, form filling, content collection, and Windows desktop interactions. The skill selects browser or desktop tools for the task and guides screenshot capture and desktop network traffic observation when needed.

• Automating website login and form entry
• Collecting page content and screenshots
• Operating Windows desktop applications

Develop HTML and JavaScript web games through small changes and repeated Playwright tests, which automate browser actions. Inspect gameplay screenshots, text representations of game state, and console errors to check controls, outcomes, and newly added features.

• Adding features to a browser game
• Testing movement, jumping, and attacks
• Checking score changes and win or lose transitions

Capture a local static HTML page from the terminal using Playwright and Chromium. The supplied commands install the browser, set a 2048 × 1152 viewport, and save screenshots without starting a web server.

• Capturing a local static HTML page
• Saving screenshots at a specified viewport size
• Keeping first and second captures as separate files

Debug local web and Electron apps through a persistent Playwright session in js_repl, an interactive JavaScript environment. Reuse browser connections while checking user interactions, visual states, screen sizes, and screenshots after changes.

• Rechecking an interface after code changes
• Testing buttons and complete user flows
• Inspecting layouts at desktop and mobile widths

Automate a real browser from the terminal to navigate pages, fill forms, extract data, and investigate interface problems. Use page snapshots to identify controls, and capture screenshots or traces, records of browser activity, for review.

• Automate form filling and submission
• Extract information from web pages
• Investigate UI flows with screenshots and traces

Add Storybook stories, examples of component states, for the Kilo VS Code extension UI. The existing Playwright runner turns them into screenshot comparisons to check visual changes across states and widths.

• Add screenshot coverage for chat or settings screens
• Check layouts at 420px and 200px widths
• Show permission requests using mock data

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.

Write production-grade Playwright tests in TypeScript: Page Object Model, fixtures, auto-waiting, user-facing locators, parallel execution, CI integration, sharding, and 2025-2026 feature awareness. Includes an explicit "do not" list for AI agents. Use when: "Playwright," "write E2E test," "page object," "new Playwright suite," "Playwright config." Not for: fixing one flaky test at runtime — use test-reliability. Not for: bulk regenerating selectors after a UI refactor — use selector-drift-recovery. Not for: visual baseline creation/management — use visual-testing. Not for: deep WCAG/axe audits — use accessibility-testing. Related: visual-testing, ci-cd-integration, api-testing, test-reliability, selector-drift-recovery, accessibility-testing.

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

Migrate a test suite from one framework to another, incrementally and without losing coverage. Covers Selenium→Playwright, Cypress→Playwright, Jest→Vitest, Mocha→Vitest, and Protractor→Playwright, with parallel CI running, locator/assertion translation, and a coverage-parity track. Use when: "migrate tests," "switch framework," "Selenium to Playwright," "Jest to Vitest," "framework migration." Not for: bulk selector regeneration after a UI refactor on the SAME framework — use selector-drift-recovery. Not for: healing one flaky test at runtime — use test-reliability. Not for: modernizing patterns without changing framework — use ai-qa-review. Related: playwright-automation, cypress-automation, unit-testing, ci-cd-integration, test-reliability.

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

Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, and anti-detection patterns. This skill covers Playwright (recommended) and Puppeteer, with patterns for testing, scraping, and agentic browser control. Key insight: Playwright won the framework war. Unless you need Puppeteer's stealth ecosystem or are Chrome-only, Playwright is the better choice in 2025. Critical distinction: Testing automation (predictable apps you control) vs scraping/agent automation (unpredictable sites that fight back). Different problems, different solutions. Use when "playwright, puppeteer, browser automation, headless, web scraping, e2e test, end-to-end, selenium, chromium, browser test, page.click, locator, playwright, puppeteer, browser, automation, testing, scraping, headless, e2e, selenium, web-testing" mentioned.

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

Playwright v1.64 (E2E / コンポーネントテストフレームワーク) リファレンス。 test, expect, page, locator, getByRole / getByText / getByLabel / getByTestId / getByRef、 toBeVisible, click, fill, route, mock, fixtures、playwright.config.ts、 auth 永続化、Credentials (passkeys / WebAuthn)、WebStorage、WebMCP、 Playwright MCP / playwright-cli、trace viewer、screencast、test locks、codegen、UI モード。

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