'e2e' 검색 결과

Build end-to-end tests that follow user journeys in browsers and mobile simulators or emulators. Guides e2e configuration, AI-driven actions, precise outcome checks, failure investigation, and exploratory bug hunts backed by reproducible tests.

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

• Testing browser user journeys with AI-driven actions
• Checking app flows on mobile simulators and emulators
• Investigating failed tests through reports and traces

E2E テストの spec を書く・編集する・レビューする際に必ず発火させる。新しいシナリオの追加、既存 E2E テストの修正・デバッグ、E2E テストの書き方の相談、slice-tdd skill から E2E spec が必要と判断された場面で使う。触る範囲に対応するプロジェクトの E2E の流儀 (spec の書き方・構造・命名) を探して従わせる入口。E2E を実行する手順は扱わない (別スキルの責務)。

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

Create, update, and debug Docker-based end-to-end tests for the Composio CLI. Covers running the executable, keeping test data separate, checking command output, and maintaining package manifests within the CLI test suite.

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

• Add end-to-end tests for CLI commands
• Debug unexpected CLI test output
• Keep test data isolated between tests

Maintain existing Handsontable browser tests built with Jasmine and Puppeteer. Covers asynchronous operations, simulated user input, assertions that work across themes, targeted test runs, and guidance for moving broken or unreliable tests to Playwright.

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

• Updating an existing Jasmine browser test
• Fixing assertions that fail under different themes
• Checking simulated mouse, keyboard, and touch input

実装済みE2Eテストのテストシナリオ解説を生成し、解説とコードの整合を独立に検証する。Triggers on: '/explain-e2e', 'E2Eを解説して', 'E2Eのシナリオ解説', 'E2Eを検証して'

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

Run NemoClaw live end-to-end tests, which check complete workflows, or inspect existing release evidence. Routes requests to local or trusted GitHub workflows and reports the tested commit, results, workflow link, and relevant job links.

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

• Run end-to-end tests for the latest pull request commit
• Run end-to-end tests for the current main commit
• Test working-tree source in a requested local run

Write and review Apache SeaTunnel unit tests and E2E tests that check complete jobs using Testcontainers. It provides concrete rules for container setup, waiting, resource cleanup, and assertions to address intermittent failures and resource leaks.

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

• Writing a new connector E2E test
• Reviewing a test diff before a pull request
• Fixing intermittent failures or resource leaks in tests

Add end-to-end tests, which check complete usage flows, and API tests for features that already work. Follow the project's existing test setup to extend automated coverage without introducing a separate testing approach.

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

• Adding automated tests to an existing feature
• Testing complete usage flows with E2E tests
• Adding API tests using the existing test setup

E2E テストを実行する手順に沿って E2E を動かす際に発火させる。実行環境のセットアップ、実行コマンド、CI 統合、実行が失敗したときの対処など、E2E を「動かす」場面で使う。触る範囲に対応するプロジェクトの実行手順を探して従わせる入口。E2E spec を書く・レビューするのとは別の責務 (spec の書き方は扱わない)。

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

仕様（チケットの完了条件・受入基準）からE2Eテストを実装する（非対話）。Triggers on: '/create-e2e', 'E2Eテストを書いて', 'E2Eテストを追加して'

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

Investigate failing or flaky NemoClaw end-to-end tests, which check complete workflows. Trace each assertion through its inputs and implementation, including cleanup and dependent jobs, and produce an evidence ledger to guide authorized repairs and reruns.

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

• Investigate a failing end-to-end test
• Audit assertions that execution has not reached
• Review cleanup and dependent job requirements

計画・差分レビュー・E2E計画・E2E結果を 1 つのブラウザページ（タブ切替）に統合表示する review-hub の操作手順。agent-review-kit のページを iframe で束ね、タブごとの承認ボタン（計画承認・E2E実行承認・PR作成承認）を wait-approval で受け取る。ステータスバー（フェーズ進行・作業メモ）と中断ボタン、セッション再開手順（status / resume）も定義する。計画→実装→PR のように承認ゲートを挟むフロー系スキルから参照される。Use when a skill needs to show plans, diffs, or E2E results in one tabbed browser page, wait for a browser-side approval gate, or resume an interrupted review session.

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

Build end-to-end tests with Playwright and Cypress to check complete user workflows, such as login and checkout. Improve test reliability through stable element selection, independent test data, appropriate waits, and debugging with traces and screenshots.

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

• Automate tests for login and checkout workflows
• Investigate tests that fail intermittently
• Run browser tests in CI/CD pipelines

Continuously monitor automatic end-to-end tests on NemoClaw main, group failures by root cause, and coordinate fixes and peer reviews through GitHub. Track ownership and merge readiness while checking whether later runs confirm each repair.

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

• Continuously monitor automatic test failures on main
• Coordinate repair ownership across maintainers
• Review peer fixes and assess merge readiness

Create and update Playwright tests that check Handsontable interactions in real browsers. The skill guides test organization, reliable waits, element selection, and coverage across themes and bundles, while helping distinguish browser tests from unit tests.

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

• Test keyboard navigation and cell editing
• Add regression coverage for a bug fix
• Check behavior across themes and bundles

E2Eテストケースカタログと突き合わせ、1ケースずつ解説→実演（Headed Playwright）→人間判定を繰り返す。Triggers on: '/demo-e2e', 'テストケースごとにデモして', 'カタログと突き合わせてデモ', 'E2Eケースを1件ずつ確認して'

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

Windows 데스크톱 앱을 직접 조작하는 자동 테스트를 만듭니다. 화면 요소 식별, 표시 대기, 실패 기록과 CI 연동을 다룹니다.

• Windows 앱 조작 테스트 작성
• 결과가 불안정한 GUI 테스트 조사
• 화면 요소에 안정적인 식별자 추가

Playwright로 브라우저 조작을 재현하는 테스트를 만들고 화면별 작업 정리와 자동 실행을 지원합니다. 간헐적 실패를 조사하고 이미지, 영상, 실행 기록을 저장합니다.

• 로그인과 검색 동작을 확인할 때
• 화면별 테스트 작업을 정리할 때
• 간헐적으로 실패하는 테스트를 조사할 때

Select, inspect, validate, and report Paperclip evaluations for Runner protocol behavior or complete product workflows. Interpret results with evidence, source revisions, costs, and failure categories, and refresh reports from retained evidence without new provider calls.

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

• Choosing between Runner and Product E2E evaluations
• Inspecting evaluation catalogs without credentials
• Interpreting failures using evidence and execution records

Add or extend Paperclip end-to-end evaluations that exercise real browser workflows across the server, database, and runner. Define expected outcomes, check independent evidence, and connect results to the existing reporting pipeline for local or Daytona execution.

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

• Adding an evaluation for a complete user workflow
• Updating test data and outcome checks
• Including screenshots and artifacts in evaluation reports

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

Guide substantial qwen-code feature development from investigation and design through implementation, testing, and review. Produce design documents and end-to-end test plans, compare behavior before and after changes, and address verified review findings.

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

• Developing features that span multiple files
• Documenting a design before implementation
• Comparing behavior before and after a change

Run Openwork end-to-end tests, which verify complete user journeys, locally or on Daytona. Check the exact commit and runtime, investigate failures or skipped tests, and report results with commands, counts, and an explicit overall verdict.

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

• Running a single end-to-end test
• Verifying the exact commit intended for a PR
• Investigating skipped tests and missing prerequisites

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