32건 · 관련도순
Move browser tests from Cypress or Selenium to Playwright with file-by-file conversion and verification. The skill also adapts shared helpers and element selectors, updates CI workflows and documentation, and reports tests that need manual work.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Move browser tests from Cypress or Selenium / WebDriver to Playwright using dedicated migration guides. Covers corresponding commands, changes in test architecture, and incremental adoption strategies to help plan and carry out the transition.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Set up Playwright browser tests, generate cases from specifications or URLs, and review coverage gaps. Diagnose tests that fail inconsistently, migrate Cypress or Selenium suites, and optionally connect TestRail and BrowserStack for results and browser testing.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create Playwright tests for user workflows, APIs, and visual changes. Use TypeScript or JavaScript examples to choose reliable page elements, manage login state, diagnose intermittent failures, and configure automated test runs in CI.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Migrate from Cypress or Selenium to Playwright. Use when user mentions "cypress", "selenium", "migrate tests", "convert tests", "switch to playwright", "move from cypress", or "replace selenium".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automated cookie consent validation using Selenium and Playwright. Covers banner interaction testing, consent state verification, tag firing audit after consent choices, regression testing for cookie compliance, and CI/CD pipeline integration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert en test automatisé (Playwright, Cypress, Selenium, CI integration, visual testing)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Accessibility testing toolkit using Selenium WebDriver 4+ with Java 21+ and axe-core engine. Use when asked to validate WCAG 2.1/2.2 compliance, scan pages or components for a11y violations, test keyboard navigation, audit color contrast, check ARIA semantics, generate accessibility reports, filter axe rules, debug screen reader issues, or implement POUR principles (perceivable, operable, understandable, robust).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Browser Use Cloud의 API와 SDK로 브라우저 자동화를 구현하도록 돕습니다. 인증, 세션, 로그인 상태 저장, 기존 에이전트 및 외부 서비스 연동을 안내합니다.
Analyze custom virtual machines written in JavaScript by extracting instruction tables, examining constants, and capturing runtime state. Use the findings to reconstruct how obfuscated code executes, including custom runtimes used in risk-control engines.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use ROADrecon and roadtx during authorized Microsoft Entra ID testing to inspect directory objects and authentication tokens, which represent access permissions. Explore collected configuration offline, test token exchanges, and assess conditional access and device controls.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Inspect website responses with curl, using browser-like request headers and checking file size, content, and format. Identify placeholder pages and choose a browser-based or direct API approach when the expected content is missing.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
End-to-end testing with Playwright: test generation, page objects, locator strategy, flaky- test diagnosis, visual regression, and CI integration. Use when writing E2E tests, fixing flaky tests, or migrating from Cypress/Selenium.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks to "build web automation scripts", "check browser automation for detection", "generate web scraping code", "create form filling automation", or "build anti-detection browser scripts".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Execute Python code in a safe sandboxed environment via [inference.sh](https://inference.sh). Pre-installed: NumPy, Pandas, Matplotlib, requests, BeautifulSoup, Selenium, Playwright, MoviePy, Pillow, OpenCV, trimesh, and 100+ more libraries. Use for: data processing, web scraping, image manipulation, video creation, 3D model processing, PDF generation, API calls, automation scripts. Triggers: python, execute code, run script, web scraping, data analysis, image processing, video editing, 3D models, automation, pandas, matplotlib
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Step-by-step migration guides for moving to Playwright from Cypress or Selenium/WebDriver — command mappings, architecture changes, and incremental adoption strategies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Step-by-step migration guides for moving to Playwright from Cypress or Selenium/WebDriver — command mappings, architecture changes, and incremental adoption strategies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Battle-tested Playwright patterns for writing, debugging, and scaling reliable test suites. Use when you need guidance for E2E, API, component, visual, accessibility, or security testing, plus CI/CD, CLI automation, page objects, and migration from Cypress or Selenium. TypeScript and JavaScript.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Explains test failures and provides actionable debugging guidance. Use when tests fail (unit, integration, E2E), builds fail, or code throws errors. Analyzes error messages, stack traces, and test output to identify root causes and suggest concrete fixes. Handles pytest, jest, junit, mocha, vitest, selenium, cypress, playwright, and other testing frameworks across Python, JavaScript/TypeScript, Java, Go, and other languages.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Bulk-regenerate broken test selectors after a UI refactor or redesign. Detects drift between old and new DOM with an aria-snapshot diff, maps old locators to new equivalents using role-first + region scoping, validates against the new build, and produces a single PR with grouped per-file selector updates and per-change evidence. Assumes Playwright >= 1.50 (trace viewer DOM-snapshot panel, getByRole filtering, ariaSnapshot). Use when: "UI refactor broke tests," "redesign broke tests," "bulk update selectors," "regenerate selectors after refactor," "selector drift," "fix N broken tests after redesign." Not for: healing one flaky test at runtime — use test-reliability. Not for: writing a new test suite from scratch — use playwright-automation. Not for: re-recording tests after a framework switch (Selenium to Playwright) — use test-migration. Related: test-reliability, playwright-automation, test-migration, ci-cd-integration, visual-testing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build Cypress test suites in TypeScript: E2E tests, component tests, custom commands, cy.intercept network control, cy.session login, Cypress Cloud, and CI integration. Covers retry-ability, the command queue, cross-origin flows with cy.origin, and data-driven testing with fixtures. Use when: "write E2E test in Cypress," "Cypress page object / custom command," "cy.," "cy.intercept," "Cypress component test," "Cypress Cloud," "cypress.config.ts." Not for: Playwright suites — use playwright-automation; flaky-test healing or quarantine — use test-reliability; bulk selector regeneration after a UI refactor — use selector-drift-recovery; Selenium-to-Cypress conversion — use test-migration. Related: playwright-automation, ci-cd-integration, visual-testing, unit-testing, test-reliability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.