'e2e' 검색 결과

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.

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

Acceptance testing workflow for the Software Metrics Machine CLI e2e suite. Use when writing, extending, debugging, or reviewing bashunit acceptance tests under apps/cli/e2e, including command help checks, cached fixture flows, GitHub MSW-backed flows, local git repository fixtures, SMM_STORE_DATA_AT workspaces, and pnpm run test:cli:acceptance. USE FOR: CLI acceptance tests, e2e tests, bashunit, apps/cli/e2e, command smoke tests, persisted CLI output tests. DO NOT USE FOR: unit tests or Vitest tests (use tdd skill), linting (use lint skill), webapp browser tests.

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

アプリのテストはすべてこのスキルを使う。開発中のTDD（テストファースト）から、 ユーザー目線のE2E・受入テスト、インフラ/デプロイ検証、リリース前の網羅テストまでを1つに統合。 「テストを書いて」「テストして」「動作確認して」「TDDで進めて」「カバレッジを確認」 「E2Eテスト」「リリース前にちゃんとテストしたい」「本番で動くか確認」「回帰テスト」 などの文脈で必ず使用する。§0「適用段階」に従い、たたき台〜v1 では「壊れたら困る順」の最小テスト、 固定化段階(v1 到達後のブラッシュアップ)ではユーザーがテストと明示しなくてもTDDサイクルを適用する。 セキュリティ・コスト・パフォーマンスの監査は Skill launch-security を併用する。

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

テストの追加・補強・作り直し。TDDモード（実装前テスト先行生成）にも対応。 Playwright・Jest等のE2Eテスト、ユニットテスト、APIテストの新規作成・補強を行う。 「テストを書いて」「カバレッジを上げて」「テストを作り直して」「E2Eテストを作って」 「自動テストを作成して」「Playwrightでテストして」「操作テストを作って」 「○○のテストを実装して」「バックエンドテストを作って」などのリクエストで使用する。

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

Use this skill whenever the user wants browser-based end-to-end tests for an Adobe App Builder application. Covers Playwright E2E testing for ExC Shell SPAs, AEM extension UIs, and full-stack flows. Use when the user mentions: "E2E test", "end-to-end test", "Playwright", "browser test", "test my SPA in the browser", "test my AEM extension", "test the full flow", "integration test with UI", "headless browser test", "E2E in CI". This skill is for BROWSER-based testing only. For Jest unit tests of actions or React components, use appbuilder-testing instead.

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

agent-browser CLIでブラウザ検証をサブエージェント実行。 E2Eテスト、UI確認、フォーム検証、スクリーンショット取得に使用。 Trigger: agent-browser, ブラウザで確認, ブラウザ検証, E2E確認, UIテスト, スクリーンショット撮って, 画面確認, ブラウザテスト

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

Use this skill whenever the user wants browser-based end-to-end tests for an Adobe App Builder application. Covers Playwright E2E testing for ExC Shell SPAs, AEM extension UIs, and full-stack flows. Use when the user mentions: "E2E test", "end-to-end test", "Playwright", "browser test", "test my SPA in the browser", "test my AEM extension", "test the full flow", "integration test with UI", "headless browser test", "E2E in CI". This skill is for BROWSER-based testing only. For Jest unit tests of actions or React components, use appbuilder-testing instead.

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

This skill should be used when the user asks for "browser tests", "playwright tests", "end-to-end testing", "test user flows", "E2E coverage", "integration tests for UI", "page object pattern", "/e2e command", or discusses automated browser testing. Covers the E2E test loop workflow, Playwright patterns, page objects, and selector strategies.

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

기존 테스트와 부족한 부분을 점검합니다. 요구 사항, 업무 규칙, 결함을 식별 번호와 실행 결과에 연결하고 테스트 대장으로 검증 여부를 추적합니다.

• 기존 테스트와 부족한 부분을 점검합니다
• 결함 수정의 재발 방지를 확인합니다
• 클라이언트와 서버의 계약 검증을 살핍니다

실패하는 테스트를 먼저 확인하고 최소한의 구현으로 통과시킨 뒤 코드를 정리합니다. 기능 개발과 버그 수정에서 80% 이상의 테스트 커버리지를 확인하고 검증 결과를 기록합니다.

• 테스트부터 새 기능 구현하기
• 버그를 재현한 뒤 수정하기
• 테스트 통과를 유지하며 코드 정리하기

Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.

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

• Review accessibility coverage for shared components
• Add accessibility checks to page flow tests
• Run accessibility tests in CI

Operate and test terminal apps without a display using named background sessions. Wait for visible screen changes, send keystrokes, reproduce Cline CLI bugs, capture text or PNG evidence, and write automated tests of interactive behavior.

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

• Reproducing Cline CLI interface bugs without a display
• Running an interactive process in the background
• Writing automated tests for terminal interactions

Test the Senpi adapter and task engine against the real senpi binary in an isolated environment. Check task and team behavior, record evidence in a consistent location, and verify that the existing agent directory remains untouched.

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

• Verify adapter behavior after code changes
• Test task execution and team recovery
• Check that skills reach child tasks

Coordinate large migrations, refactors, and bulk renames by splitting them into independent tasks. After plan approval, 5–30 agents work in separate Git worktrees, isolated working directories, then review, test, and open a pull request for each task.

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

• Migrate code across many files
• Refactor independent modules in parallel
• Rename identifiers across directories

Check a Twenty pull request through real browser scenarios derived from its changes. Verify database effects and server logs alongside visible results, then produce screenshots, a structured verdict, and a report of any failures or uncertainty.

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

• Validate user flows before or after merging a Twenty pull request
• Check database writes and timeline activity after saving records
• Investigate backend errors hidden behind a successful screen

Write and register SGLang unit and end-to-end tests, from choosing models and file locations to reusing server fixtures. Follow project rules for meaningful assertions, CI registration, dependency mocking, and safe server cleanup after tests.

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

• Adding CPU-only unit tests for component logic
• Testing features through a running SGLang server
• Registering tests in an appropriate CI suite

Choose and run checks for TypeScript SDK changes, including type checks, linting, builds, Vitest suites, and tests of complete runtime flows. Also guides writing or adapting CLI tests for Effect v4.

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

• Validate changes to TypeScript packages
• Choose focused checks for a change
• Investigate failing TypeScript CI checks

Set up Playwright, a browser testing tool, for an existing web project. Generate configuration, test folders, an example test, and applicable CI automation, then run the test and address setup failures.

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

• Adding browser tests to an existing web project
• Configuring tests for the project's framework
• Running browser tests automatically in CI

Close a NemoClaw maintenance day by consolidating documentation and changelog updates, reviewing merged and unfinished work, and preparing a release handoff. When requested, pass the version to the dedicated skill that verifies and creates the release tag.

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

• Prepare an end-of-day release handoff
• Consolidate documentation for merged changes
• Review unfinished work and verification status

Prepare and create a signed NemoClaw release tag for a requested version, then monitor release workflows, documentation, and published images. It records maintainer decisions and drafts an announcement after verifying the remote tag.

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

• Preparing a tag for a requested release version
• Recording documentation and end-to-end test decisions
• Checking workflows and images after tagging

Write and review Handsontable tests that check intended behavior. The skill guides bug reproduction, meaningful assertions, failure diagnosis, and fresh test runs, while covering mock boundaries and migration of broken legacy tests to Playwright.

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

• Reproducing a bug with a failing test
• Diagnosing whether code or test expectations are wrong
• Reviewing assertions for meaningful behavior checks

Add tests to a completed development phase using its records and implementation. Review the proposed coverage, then generate unit tests for individual components and browser tests for full workflows, verify them, and commit the test files.

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

• Adding automated tests after a development phase is complete
• Turning acceptance criteria into test coverage
• Reviewing which code needs unit or browser tests