'e2e' 검색 결과

Write and update Handsontable unit tests with Jest and type tests with TypeScript. Explains file placement, focused test runs, boundary cases, and checks for public types, while helping choose between isolated logic tests and browser tests.

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

• Adding unit tests for calculations and data transformations
• Covering bug fixes and internal refactoring
• Checking TypeScript declarations and public exports

AWT — AI-Powered E2E Testing (Beta) workflow skill. Use this skill when the user needs AI-powered E2E web testing — eyes and hands for AI coding tools. Declarative YAML scenarios, Playwright execution, visual matching (OpenCV + OCR), platform auto-detection (Flutter/React/Vue), learning DB. Install: npx skills add ksgisang/awt-skill --skill awt -g and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

Architects the encryption, codec/transport, and premium-feature layer of a group video-calling product, on top of an already-chosen SFU topology. Covers E2EE patterns (Zoom leader-fan-out, Signal pairwise-fan-out, MLS/TreeKEM as in Discord's DAVE, Telegram's ledger consensus), the SFrame (RFC 9605) + WebRTC Insertable Streams mechanism letting an SFU relay encrypted frames it can't read, codec/transport choice (AV1/VP9 SVC vs. simulcast, Opus, congestion control, Media-over-QUIC, WHIP/WHEP), and which "premium" features (virtual backgrounds, live captions, recording, breakout rooms, spatial audio) survive E2EE vs. structurally can't. Use when adding E2EE to an SFU-based call, choosing a 2026 codec/SVC strategy, or deciding which features to disable under E2EE mode. NOT for call topology/platform choice (see webrtc-adhoc-video-chat, which this composes with). NOT for one-way broadcast (see managed-video-streaming-pipeline). NOT for the DM/group-chat text backend (see realtime-messaging-backend-architecture).

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

OpenClaw의 Docker 환경에서 전체 동작을 확인하는 테스트를 작성하고 수정합니다. 모의 서버와 실제 서비스로 전송 내용, 이미지 이해, 최종 응답을 검증합니다.

• Docker 종단 간 테스트 추가 및 수정
• 의존 서비스로 전송한 요청 내용 확인
• 실제 모델 제공 서비스의 동작 검증

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

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

Create unit, integration, and E2E tests that check complete user flows, then identify coverage gaps and investigate unreliable results. The skill also supports performance and security test plans, with findings organized by severity and suggested fixes.

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

• Writing tests for normal behavior, errors, and boundary values
• Finding gaps in test coverage
• Investigating tests that fail intermittently

Design tests for charts, dashboards, and interactive diagrams. Combine data checks, component tests, screenshot comparisons, and end-to-end workflows to catch incorrect values, broken interactions, and visual changes while keeping tests stable.

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

• Choose test coverage for a chart component
• Set up stable screenshot comparisons for a dashboard
• Verify mobile interactions and degraded network states

LoongCollector E2E Testing Framework Development Guide. Use this rule when you need to understand E2E testing framework architecture, develop new test behavior functions, or extend testing capabilities. Contains detailed BDD testing framework usage, test behavior function development and registration workflows, and comprehensive reference of existing testing capabilities. Example: When adding custom test behaviors for new plugins, use this rule to understand how to write and register new test functions. Example: When developing E2E tests, use this rule to understand the e2e framework.

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

Set up an end-to-end test suite in any repo, following practices that make e2e a reliable per-PR gate: real flows over bypass, layered assertions, a reusable auth/session helper, video+trace evidence, and a compounding suite. Use when a repo has no e2e (or weak e2e) and you want system-level tests — "set up e2e", "add end-to-end tests", "scaffold a test gate".

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

AWT — AI-Powered E2E Testing (Beta) workflow skill. Use this skill when the user needs AI-powered E2E web testing — eyes and hands for AI coding tools. Declarative YAML scenarios, Playwright execution, visual matching (OpenCV + OCR), platform auto-detection (Flutter/React/Vue), learning DB. Install: npx skills add ksgisang/awt-skill --skill awt -g and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

Set up an end-to-end test suite in any repo, following practices that make e2e a reliable per-PR gate: real flows over bypass, layered assertions, a reusable auth/session helper, video+trace evidence, and a compounding suite. Use when a repo has no e2e (or weak e2e) and you want system-level tests — "set up e2e", "add end-to-end tests", "scaffold a test gate".

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

Design, implement, and review Composio CLI commands, including user interactions, output, errors, and configuration. It guides command wiring and service changes using Effect and effect/cli, with references for implementation patterns.

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

• Designing CLI command behavior and output
• Implementing command wiring with Effect
• Reviewing configuration and error handling

Write, review, and upgrade Effect v4 code for Composio CLI and its related packages. It guides service definitions, typed errors, command APIs, and version alignment, checking unfamiliar APIs against source files and installed type definitions.

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

• Implementing and reviewing Effect v4 code
• Defining services and typed error recovery
• Checking effect/cli APIs

Test Qwen Code CLI behavior from model requests through tool execution. Reproduce bugs, check terminal interactions and MCP tool connections, and inspect API logs using real models or mock servers for controlled scenarios.

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

• Reproduce reported CLI bugs and verify fixes
• Test MCP tool connections through the CLI
• Check terminal rendering and keyboard interactions

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

Classify a failed NemoClaw GitHub Actions job using logs with sensitive information hidden and output size limited. Optionally inspect saved artifacts to identify failure patterns and gather evidence for further investigation.

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

• Classifying a failed GitHub Actions job
• Inspecting saved artifacts for failure evidence
• Gathering initial evidence for an E2E failure

Implement or review a managed runtime provider for NemoClaw. Check its required interfaces, activation requirements, saved provider identity, and lifecycle behavior, then report validation evidence and any remaining qualification requirements.

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

• Plan a new managed runtime provider
• Review provider activation requirements
• Check saved state across lifecycle operations

Create Playwright tests that check user journeys in a browser. The skill organizes reusable page interactions, configures test environments, investigates intermittent failures using execution traces, and supports API mocking, visual comparisons, and automated pipeline integration.

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

• Test login and other browser user journeys
• Investigate tests that fail intermittently
• Replace API responses with controlled test data

Launch the real iPolloWork app on Daytona or locally and run scripted end-to-end tests through its debugging connection. Collect machine-checkable assertions, validated screenshots, and reports as evidence of the tested behavior.

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

• Run scripted end-to-end tests on Daytona
• Collect screenshots and reports for a pull request
• Run tests locally when Daytona is unavailable

Build CI workflows that use mirrord to test applications against services in a real Kubernetes cluster. Configure runner access, start and stop application sessions, validate configuration files, and troubleshoot connection, permission, and logging problems.

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

• Run integration and end-to-end tests against staging
• Create mirrord workflows for GitHub Actions or GitLab CI
• Configure Kubernetes access from a CI runner

LoongCollector E2E 测试全流程指南：设计、编写、运行和调试。当需要编写新 E2E 测试、运行现有测试、或排查 E2E 测试失败时使用此 skill。

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

E2E Testing Standards Guide. Use this rule when you need to write or execute E2E tests, including test naming conventions, test workflows, and test behavior templates. This rule should be used for end-to-end integration testing scenarios to ensure test standardization and maintainability. Example: When writing new E2E tests, use this rule to ensure proper test format and workflow compliance.

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

Canonical rules for writing, rewriting, or reviewing Shift desktop Playwright E2E tests and visual goldens under `apps/desktop/e2e/`. Use whenever you add or change a `.spec.ts`, a fixture, `EditorDriver`, a screenshot baseline, or Playwright project membership, and whenever you investigate a flaky or failing E2E test. Covers waits, oracles, goldens, fixtures, projects, and flake verification.

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