'playwright' 검색 결과

Automate browser tasks with playwright-cli, including navigation, form filling, and data extraction. Test web applications, capture screenshots, reuse login sessions, and generate test code through command-line browser controls.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Automating form entry and page navigation
• Checking web application behavior
• Saving screenshots, videos, and PDFs

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

웹 앱의 조작 과정을 커서와 자막이 포함된 WebM 영상으로 기록합니다. 화면 조사와 리허설을 거쳐 입력, 클릭, 스크롤을 보기 편한 속도로 촬영합니다.

• 새 기능의 사용 과정을 영상으로 소개
• 처음 사용하는 사람을 위한 안내 영상 제작
• 문서에 조작 영상 추가

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

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

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

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

Run Nexent daily or manual full test suites on a self-hosted Ubuntu machine, using the appropriate test layer for each check. Keep results and evidence local, and prepare maintenance candidates for local test assets.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Running daily full test suites
• Recording manual test results and evidence locally
• Preparing local test and Playwright maintenance candidates

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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 モード。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review and add E2E tests, which check complete user journeys such as signing in or checking out. Identify missing coverage, organize reusable tests, and check that automated delivery workflows run them and handle failures.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking test coverage for sign-in and checkout flows
• Adding tests for form submissions
• Reviewing automated test runs and failure handling in CI/CD

Create YAML test scenarios for web applications and run them in a real browser with Playwright. Use image matching and text recognition to check screens, then organize failure findings for investigation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Test a checkout flow in a real browser
• Check screens with image matching and text recognition
• Investigate browser test failures

Write and review Handsontable tests that check intended behavior. The skill guides bug reproduction, meaningful assertions, failure diagnosis, and fresh test runs, while covering mock boundaries and migration of broken legacy tests to Playwright.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reproducing a bug with a failing test
• Diagnosing whether code or test expectations are wrong
• Reviewing assertions for meaningful behavior checks

Build websites, landing pages, and interactive experiences with colors, typography, and layouts shaped by their subject. Create images and logos, then check desktop and mobile views with Playwright before delivering a verified local preview.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating a small business website
• Building a portfolio with a distinct visual style
• Producing a landing page with custom images and a logo

Build and run computer-use-demo in Docker, then use Playwright to test its Streamlit interface without opening a visible browser. Save conversation transcripts, API exchanges, and screenshots to inspect behavior after changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking the interface after changing computer-use-demo
• Testing combinations of models and tool versions
• Checking Thinking settings and model changes during a session

Prepare a local LangBot environment for development and browser testing. The skill covers service startup, shared connection settings, browser access, proxy troubleshooting, and reusable login profiles, with guidance for Linux and WSL environments.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare a local Linux or WSL development environment
• Start services and verify WebUI access
• Choose Computer Use or Playwright MCP for browser control

Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipelines, or publishing test results to the Azure portal.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this when adding Nix-based local runs for an existing Playwright e2e suite. Provides a self-contained `tests/shell.nix` that uses `nixpkgs-latest` for `playwright-driver.browsers`, plus a justfile entry — works on NixOS where `npx playwright install --with-deps` cannot.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert knowledge for Playwright Workspaces development including troubleshooting, best practices, decision making, limits & quotas, security, and configuration. Use when managing Playwright Testing workspaces, tokens/RBAC, quotas, monitoring/metrics, or run/AADSTS7000112 issues, and other Playwright Workspaces related development tasks. Not for Azure App Testing (use azure-app-testing), Azure DevOps (use azure-devops), Azure Pipelines (use azure-pipelines), Azure Test Plans (use azure-test-plans).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.