「assertion」の検索結果

Test UI components the way users interact with them using Testing Library — query by role, text, and label instead of implementation details. Use when someone asks to "test React components", "Testing Library", "user-centric testing", "test accessibility", "test without implementation details", or "render and query components in tests". Covers React Testing Library, queries, user events, async testing, and accessibility assertions.

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

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

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

On-Behalf-Of (OBO) Flow for web APIs to call downstream APIs while preserving user identity in MSAL.NET

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

QA Automation Engineer skill. Use this to write or refactor unit tests. Ensures tests follow the project's xUnit, FluentAssertions, and Moq standards.

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

C# and .NET testing patterns with xUnit, FluentAssertions, mocking, integration tests, and test organization best practices.

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

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

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

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

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

Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.

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

GEODE prompt-writing standards. Use when creating or editing runtime prompts, system prompts, tool/developer instructions, model-facing identity text, prompt templates, or scaffold rules that affect model behavior; especially when avoiding identity assertions such as "You are ...".

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

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

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

Audit whether tests detect broken behavior by tracing assertions and running narrow controlled mutations in an isolated workspace; use for test-quality reviews, not routine test execution.

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

Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.

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

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

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

BEFORE writing/changing tests, mocks, or test-only methods on production classes — mocking-the-mock, production pollution, overfit assertions; for order, `test-driven-development` wins.

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

Use when a diff may lack tests — missing assertions, uncovered branches, over-mocking, no regression test for a bug fix — dispatched by /review-changes, /do-and-judge, /judge, even without 'tests'.

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

Use when writing API endpoint tests — integration tests, contract validation, response assertions, mocked external services — even when the user says 'test this route' without naming API testing.

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

[Code Quality] Use when you need to review integration tests for assertion quality, bug protection, repeatability, and test-spec traceability — AND verify the review target (changed production code) has test coverage (integration-first) with spec↔test↔code alignment.

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

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

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

SOP for the micro-execution C.O.R.E. phase. Trigger when: - Implementing plan steps, managing code changes at commit boundaries, and verifying incremental progress. - Navigating states: Absorb, Clarify, Plan, Execute. - Prompt contains: /core, core workflow, absorb, clarify, execution invariants, commit boundary, verify assertion.

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

TDD methodology for production-quality tests. Write tests FIRST driven by PRD, Tech Spec, Implementation Plan. Covers minimal mocking, realistic test data, strong assertions, test independence.

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

XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.

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

Generate audit-ready internal control design documents from As-Is business process inventories. Produces control IDs, assertion mappings, procedures, SoD analysis, KPIs, materiality thresholds, and implementation roadmaps. Use when building internal controls for new audit engagements, SOX/J-SOX compliance, or process improvement initiatives.

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

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.

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

반복되는 null 검사를 Special Case(Null Object) 클래스로 대체하여 다형성으로 처리. "null 객체 패턴", "null 체크 반복 제거", "특수 케이스 클래스", "/introduce-special-case" 요청 시 사용. 단, 단순 전제 조건 명시는 /introduce-assertion, 타입별 분기 전반은 /replace-conditional-with-poly가 적합. /introduce-special-case [commit-ref]로 호출.

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