'e2e' 검색 결과

Run the "get dependencies current" flow for this monorepo — sweep for available updates, triage into safe / deliberate / wait buckets, bump the pnpm catalog, and prove it with the typecheck + e2e gate. Use when asked to "update dependencies", "are we on the latest", "do the quarterly sweep", "bump deps", or when the recurring sweep ticket comes due. We run NO update bot on purpose (#141) — this skill IS the update process.

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

Browser automation for AI agents via inference.sh. Navigate web pages, interact with elements using @e refs, take screenshots, record video. Capabilities: web scraping, form filling, clicking, typing, drag-drop, file upload, JavaScript execution. Use for: E2E testing, web research, automat...

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

Summarise the unit and e2e tests a branch/PR adds, run only those, and produce a paste-ready report (e.g. for a Linear card). Use when asked to 'summarise added tests', 'run the new tests', 'what tests did this PR add', or to prove a card's test coverage.

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

Conducts rigorous authoring and review of Playwright E2E tests. Enforces accessibility-first locators, web-first assertions, strict isolation, and DAMP architecture. Use when generating, refactoring, or reviewing any Playwright test code.

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

Validate bugs and features that depend on local hosts, localhost, filesystem home state, auth, polling, installed apps, real conversations, or signed native helpers.

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

Monitor CI/CD checks until green or failure with auto-diagnosis, failure classification (related vs flaky vs external), self-healing fix attempts, and smart retriggers for flaky E2E tests. Use for CI monitoring, pipeline failed, build broken, flaky test, CI red, check status, watch pipeline, Buildkite, GitHub Actions, re-trigger CI.

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

Covers Flutter testing across all three layers: unit tests (business logic, ViewModels, repositories), widget tests (UI rendering, interactions, golden regression), and integration/E2E tests (full app flows, native OS interactions). Use this skill when writing any Flutter test, setting up mocking with mocktail or mockito, implementing golden file tests, debugging async failures (pumpAndSettle timeouts, Timer leaks, FakeAsync deadlocks), fixing cross-platform golden pixel diffs in CI/CD, testing state management (Riverpod/BLoC/Provider), handling permission dialogs or native system UI with Patrol, or troubleshooting MediaQuery/Theme missing errors in widget tests.

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

Design a test strategy around product risk, business invariants, failure modes, and existing controls, deciding what deserves testing and at which boundary rather than maximising coverage. Use whenever the user asks how to test something, wants a test plan or strategy, is deciding between unit/integration/contract/E2E/property/concurrency testing, or wants to know whether existing tests actually protect what matters. Prefer this over writing tests immediately. Part of the audit suite; inherits the shared constitution while its own job is proving risk coverage.

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

Use when building this Hydrolix Grafana datasource plugin — frontend webpack bundle (`dist/module.js*`) or Go backend binary (`dist/gpx_plugin_*`). Covers the split between host-built frontend and container-built Go, when each needs an explicit rebuild, watch vs one-shot, and the verification chain (typecheck / lint / unit tests). Apply for any task that edits `src/**`, `pkg/**`, `Magefile.go`, `webpack.config.ts`, or that needs to confirm `dist/` matches the working tree before running e2e or the dev stack.

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

Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.

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

Design and implement comprehensive testing strategies. Use when setting up tests, choosing test types, implementing TDD, or improving code quality. Covers unit tests, integration tests, E2E tests, test-driven development, and testing best practices.

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

Use this skill for all verification: unit, component, E2E, native, and release checks. Required alongside mobile-core for every implementation.

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

Use when working with Detox — detox React Native testing management and analysis. Covers test configuration review, device and simulator management, build configuration analysis, test result parsing, artifact collection, and test runner integration. Use when managing Detox test suites, investigating mobile test failures, or reviewing React Native E2E testing configurations.

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

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.

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

Visual inspection of live websites to find and fix design issues. Use when reviewing UI layout/design, checking responsive design visually, detecting visual inconsistencies, or diagnosing CSS/accessibility problems at the source code level. Not for automated E2E testing.

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

Expert en test automatisé (Playwright, Cypress, Selenium, CI integration, visual testing)

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

Android/iOS automated testing: device management, app install, performance profiling, log analysis, screenshot comparison, Maestro E2E orchestration.

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

MANDATORY deploy after every code change. Typecheck → deploy → purge CDN → E2E on production → visual verify → fix-forward loop. Workers Builds native CI/CD, D1 Time Travel PIT recovery, D1→R2 long-term backups, wrangler rollback, wrangler secrets management, structured observability, cross-browser smoke tests, rollback procedures, and GitHub auto-configuration.

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

5-level verification pyramid: static→unit→Playwright E2E (homepage-first, 6bp)→AI visual→post-deploy. 8-check quality gate. Multi-agent testing (functional/security/a11y/performance). Playwright v1.59+ AI agents (Planner/Generator/Healer). WCAG 2.2 AA via axe-core v4.11. Percy+Chromatic visual regression. ADA Title II 2027/2028 deadlines.

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

Use for the infrastructure implementation phase after the backend follows the model — turning documents/infra-design decisions into infra/ (local container stack, production IaC), wiring cradle.json infra.up / infra.containers, adding IaC validate and image build steps to CI, and, once E2E passes, applying production once in a sandbox and recording it in the deployment table. Not for designing infrastructure (infra-design).

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

Electron (Chromium + Node.js 製クロスプラットフォームデスクトップアプリフレームワーク, v44) の リファレンス。main / renderer / preload / utilityProcess, ipcMain / ipcRenderer / contextBridge, BrowserWindow / BaseWindow / WebContentsView / webContents, Electron Forge, autoUpdater, safeStorage, fuses, ASAR, contextIsolation / sandbox, code signing, MAS, crashReporter, contentTracing, debugging, E2E testing, breaking changes。

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

Comprehensive testing strategies including unit tests, integration tests, E2E tests, property-based testing, visual regression, and test automation. Use when writing tests, setting up testing frameworks, or designing test coverage strategies.

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

Set up Playwright end-to-end testing in a project, including test configuration, example tests, and CI integration.

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

Pre-PR verification for VenTu — tests, data validation, static build, and e2e for the touched surface. Use before opening any PR. For visual UI checks also load ventu-verify-ui.

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