「web-testing」の検索結果

Create, edit, validate, and run Agent QA tests, suites, and hooks through MCP or CLI while preserving canonical IDs and schema contracts.

日本語の概要は準備中です。原文の説明を表示しています。

Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.

日本語の概要は準備中です。原文の説明を表示しています。

Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.

日本語の概要は準備中です。原文の説明を表示しています。

Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.

日本語の概要は準備中です。原文の説明を表示しています。

Create, edit, validate, and run Agent QA tests, suites, and hooks through MCP or CLI while preserving canonical IDs and schema contracts.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Odoo browser-facing test guidance for HTTP controllers, website and portal flows, QWeb templates, assets, OWL integration, browser tours, and JavaScript behavior. Use when testing or debugging public pages, portal access, forms, controllers, frontend assets, or end-to-end Odoo web behavior.

日本語の概要は準備中です。原文の説明を表示しています。

Vitest test runner - configuration, assertions, mocking (vi.fn, vi.mock, vi.spyOn), fake timers, snapshot testing, coverage, workspace projects

日本語の概要は準備中です。原文の説明を表示しています。

Vue Test Utils — mount vs shallowMount, the wrapper API, awaiting DOM updates, flushPromises, testing composables, and the global mounting options. Load when writing or reviewing tests that mount Vue components.

日本語の概要は準備中です。原文の説明を表示しています。

Visual regression testing — screenshot baselines, determinism, diff review, baseline custody and CI wiring. Load when adding, reviewing or debugging tests that compare a rendered subject against an approved image.

日本語の概要は準備中です。原文の説明を表示しています。

Playwright E2E testing patterns - test structure, Page Object Model, locator strategies, assertions, network mocking, visual regression, parallel execution, fixtures, and configuration

日本語の概要は準備中です。原文の説明を表示しています。

Cypress E2E testing patterns - test structure, data-cy selectors, cy.intercept() mocking, custom commands, fixtures, component testing, accessibility testing with cypress-axe, and CI/CD integration

日本語の概要は準備中です。原文の説明を表示しています。

React Testing Library — query hierarchy, userEvent, async utilities, renderHook, custom render with providers. Load when writing or reviewing tests that render React components or hooks.

日本語の概要は準備中です。原文の説明を表示しています。

Web testing patterns and best practices using Playwright for automated testing

日本語の概要は準備中です。原文の説明を表示しています。

Browser automation CLI for AI agents using agent-browser. Use for navigating websites, clicking/filling pages, screenshots, data extraction, web app testing, exploratory QA, dogfooding, Electron apps, Slack automation, Vercel Sandbox browser runs, AWS AgentCore cloud browsers, auth-heavy flows, and long autonomous browser sessions. Prefer over generic browser tools when a fresh/tool-managed Chrome session is fine. NOT for the user's real Chrome cookies/profile (see mk:chrome-profile); NOT for reusable Playwright specs (see mk:qa-manual).

日本語の概要は準備中です。原文の説明を表示しています。

Playwright automation, Chrome DevTools debugging, and browser interaction testing. Use for E2E/unit tests, capturing screenshots, inspecting network/console logs, or validating user flows in web applications.

日本語の概要は準備中です。原文の説明を表示しています。