「engine」の検索結果

Builds, hardens or reviews container images and local runtime packaging with startup and shutdown evidence; not remote deployment or host administration.

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

Implements or repairs identity verification and session or credential lifecycle; not operation permissions, resource access policy or a new identity provider by default.

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

Implements transactions, idempotency and interrupted-operation recovery; not schema migration or a mandatory background-job platform.

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

Implements permissions and tenant or owner scoped resource access while preserving approved grants; not authentication or role redesign.

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

Implements safe error boundaries, cancellation and user recovery contracts; not telemetry pipelines or durable retry machinery.

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

Implements structured diagnostics, correlation and justified metrics or traces; not incident investigation or a mandatory telemetry platform.

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

Creates project technical rules and recurring local procedures from the actual stack; edits guidance only, not architecture targets or application code.

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

Prepares and verifies schema migrations, database roles and isolated recovery or test resources; not query tuning or runtime mutation orchestration.

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

Establishes configuration ownership, validation, secret boundaries and environment isolation; not credential identity policy or live deployment.

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

Prepares CI/CD and remote infrastructure, then executes authorized rollouts with health and recovery checks; not standalone local container packaging.

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

Turn acceptance criteria into an executable test plan (scenarios, seed, selector gaps) before generating E2E code. Use when ACs exist but no runnable test plan does yet.

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

Audit test coverage health, gaps, and QE debt for Jira stories or epics. Produces coverage_analysis_report.md with AC-to-TC heatmap, risk scores, and prioritized action plan. Use when assessing coverage percentage, pre-release readiness, sprint readiness, or identifying missing test cases. Do NOT use for TC creation — use zephyr-test-generation instead.

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

Failure taxonomy and allowed/forbidden repairs for a failing E2E test. Use when a Playwright/Maestro/Detox/XCUITest/Espresso/Appium test fails and you must decide whether to repair the test or route to a real bug.

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

Investigate requirements via atomic AC decomposition, actor/permission matrices, and truth-table edge cases; enforce User Story standards (scope fences, platform tags, toggles). Use when writing/reviewing Stories or AC with multi-condition logic, feature toggles, or market variants (VN/MY/SG).

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

Write or review manual Zephyr test cases with 1-condition-per-TC granularity, Module_Action on Screen when Condition naming, platform prefix rules, and High/Normal/Low priority classification. Use for test-case authoring and review; defer Jira traceability, linking, and pushing cases to Zephyr.

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

Cross-stack selector and test-id policy for web and mobile automation. Use when writing or reviewing E2E/UI test locators, or adding data-testid/accessibility identifiers to components.

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

Trigger only when the user explicitly requests live Jira or Zephyr retrieval, existing-link inspection, linking authored test cases, label updates, or stale-link audits. Do not trigger for analysis-only prompts such as 'Analyze the acceptance criteria for TICK-4521', supplied acceptance criteria, test-case authoring, or AC-to-test generation.

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

Standardizes token-efficient browser automation via playwright-cli, with Playwright MCP as the fallback driver. Runs a preflight, picks the driver rung, captures aria snapshots/console/screenshots into a named evidence dir. Use for web verification, navigation, and capturing snapshots/logs.

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

Drives iOS/Android mobile devices via Appium MCP. Runs a preflight, picks local emulator/simulator/USB or a device cloud, captures screenshots/page source into a named evidence dir. Use for verifying mobile bugs, E2E tests, and navigating real device clouds (LambdaTest/BrowserStack).

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

Quarantines an intermittently failing test behind a ticket with an owner and expiry, assigns a root-cause bucket from isolated reruns, and defines when the test leaves quarantine. Use when a test is a QUARANTINE_CANDIDATE or fails without a code change; not for deterministic failures.

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

Generate Zephyr test cases from Jira stories: parse acceptance criteria and business rules, impact-analyze existing TCs (update vs. create new), and draft correctly named test cases. Use for AC-to-test generation; defer post-generation Jira linking and manual test-case quality review.

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

Captures, masks, compares, and updates screenshot baselines for web and mobile suites, with per-region thresholds and a reviewed-diff rule for every baseline change. Use when a screenshot assertion fails, a baseline needs updating, or visual checks are being added; not for deciding what to verify.

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

Measures whether an automation suite builds release confidence via feedback-loop length, suite reliability, release cadence, and production escape rate, and emits a release_confidence verdict. Use when judging suite value, ROI, or pre-release trust; not for writing or healing tests.

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

Generates Playwright page objects from an executable test plan, one class per screen with ladder-compliant locators and no assertions, wired into a shared fixture. Use when a web scenario needs a page object that does not exist yet, or when locators drift and the page object must be rebuilt.

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