Results for “assertion”

JUnit 5, Mockito, AssertJ, and Testcontainers patterns for any JVM project. Covers test structure, parameterised tests, mocking discipline, fluent assertions, and integration testing with real containers. Stack-agnostic — referenced by every Java plugin in the marketplace. Use this skill to: - Write clear, maintainable unit tests with JUnit 5. - Mock dependencies with Mockito without overusing mocks. - Write expressive assertions with AssertJ. - Spin up real infrastructure (DBs, message brokers) with Testcontainers for integration tests. Do NOT use this skill for: - Spring-specific test slices (@SpringBootTest, @WebMvcTest, @DataJpaTest — those are in spring-boot-plugin skills). - Framework-specific mocking utilities (MockMvc, WebTestClient).

The English summary is being prepared. Showing the original description.

検査器（linter / ガード / CI ゲート / バリデータ / フィルタ）そのものの検出力が差分で静かに落ちていないか、また新設した検査が実際に検出できることが実証されているかを diff-time で検出する。Check 1 unverified detection reduction（検査器の検出ロジック（正規表現・除外パターン・解決集合・allowlist・baseline）を変更して検出件数が減ったのに、減った 1 件ずつが誤検出であった根拠が示されないまま「誤検出を潰した」「N → M 件に減少」と改善として主張している）、Check 2 unproven guard detection power（新しい検査ロジック・CI ゲート・バリデーションを追加・変更したのに、検出すべき入力を注入して検出されること／検出すべきでない入力で黙ることを示す変異注入の証跡が無く、「追加した」「CI が緑」を検出力の証拠として扱っている）、の 2 Check を対象とする report-only。テスト自身のアサーションが実質何も検証していない構造は test-assertion-effectiveness、レビュー基準・品質ゲートの明示的な弱体化（ルールの削除・閾値の引き下げ・suppression entry 追加・lint ルールの無効化）は review-criteria-integrity、リファクタ完了主張一般の検証は refactor-claim-audit、workflow の permissions と action pin は gha-workflow-security、設定ファイルの構文・型の妥当性は config-json へ委譲する

The English summary is being prepared. Showing the original description.

Migrate test files from `as` assertions to @total-typescript/shoehorn helpers. Use when tests need partial fixtures, intentionally invalid data, or safer replacements for TypeScript assertions.

The English summary is being prepared. Showing the original description.

Complete guide for ASP.NET Core Web API integration testing. Use when performing integration testing on Web API endpoints or validating ProblemDetails error format. Covers WebApplicationFactory, IExceptionHandler, Testcontainers multi-container orchestration, Flurl URL construction, and AwesomeAssertions HTTP validation. Keywords: webapi integration testing, WebApplicationFactory, asp.net core integration test, webapi integration test, IExceptionHandler, ProblemDetails, ValidationProblemDetails, AwesomeAssertions, Flurl, Respawn, Be201Created, Be400BadRequest, multi-container testing, Collection Fixture, global exception handling

The English summary is being prepared. Showing the original description.

Complete guide for TUnit new-generation testing framework. Use when creating test projects with TUnit or migrating from xUnit to TUnit. Covers Source Generator driven test discovery, AOT compilation support, fluent async assertions. Includes project creation, [Test] attribute, lifecycle management, parallel control, and xUnit syntax comparison. Keywords: TUnit, tunit testing, source generator testing, AOT testing, new generation testing framework, [Test], [Arguments], TUnit.Assertions, Assert.That, Before(Test), After(Test), NotInParallel, TUnit.Templates, Microsoft.Testing.Platform, TUnit vs xUnit, parallel execution

The English summary is being prepared. Showing the original description.

Turn specifications or requirements into an implementation plan before coding begins. Break work into testable tasks with exact files, function definitions, test assertions, and verification commands, so another developer or agent can follow the plan.

• Planning a feature before writing code
• Breaking requirements into testable tasks
• Handing implementation work to another developer or agent

Checks whether work is truly complete before reporting success, committing changes, or creating a pull request. It runs the relevant checks, reads their full output, and ties status reports to current evidence.

• Checking results before reporting completion
• Confirming that a bug fix resolves the original problem
• Verifying work before a commit or pull request

Write or repair React tests around user actions and visible results. Cover components and hooks, simulate network responses, check accessibility, and decide when real browser component tests or end-to-end tests across pages are needed.

• Adding behavior tests to React forms and components
• Testing custom hooks and asynchronous updates
• Simulating successful and failed API responses

Define project quality standards in CONSTRAINTS.md, connect measurable targets to checks, and inspect changes for weakened safeguards. It helps teams choose thresholds and catch skipped tests, suppressed warnings, unfinished code, or lowered standards during agent development.

• Set quality standards before starting agent development
• Choose coverage and performance thresholds
• Detect skipped tests and suppressed warnings

Add or extend Paperclip Runner evaluations that test real sessions against a mock control service. Define observable pass conditions, validate cases and run selections, and retain source revisions, evidence, and costs for authorized live runs.

• Adding a focused Runner protocol evaluation
• Testing grading rules with valid and invalid evidence
• Updating evaluation selections and campaign membership

Develop Rust filters for RTK through tests written before implementation. Use real command output as test inputs, check output snapshots and unexpected inputs, verify a minimum reduction target, and complete formatting, linting, and test checks before finishing.

• Adding a new RTK command filter
• Checking filtered output against saved snapshots
• Testing empty, malformed, or ANSI-colored input

Find TypeScript values that bypass type checking through any, including inferred types and assertions. Suggest unknown, generics that preserve type relationships, or Zod validation for external data, with the checks needed where each value is used.

• Addressing ESLint warnings about explicit any
• Reviewing type safety around external API data
• Checking functions that pass any to their callers

Set up Pact tests that record what a frontend expects from an API and verify those expectations against the backend. Review these contract tests to catch incompatible changes and help services be tested and deployed independently.

• Set up tests for frontend and backend API compatibility
• Check whether services can be deployed independently
• Replace selected slow end-to-end tests with contract tests

Test Android app flows defined in XML by performing taps, swipes, and text entry, then checking screen states. Produce a JSON report with step results, commands, and failure reasons, stopping at the first failure.

• Verify login flows against an XML test specification
• Test product search and cart navigation
• Investigate UI failures on devices or emulators

Assess authorized single sign-on systems using SAML, OIDC, and OAuth2. Map the login flow, check signatures, redirects, and token validation, then document reproducible findings and their impact, including identity or tenant confusion.

• Review redirect and token checks in a single sign-on flow
• Assess SAML signatures and assertion handling
• Investigate tenant confusion and logout failures

Migrate existing PowerShell Pester tests through major versions from v3 to v6. The skill guides assertion updates, setup restructuring, mock changes, and execution configuration, using before-and-after test results to investigate failures while preserving what each test checks.

• Migrating Pester tests one major version at a time
• Fixing tests broken by a Pester upgrade
• Updating legacy Should and Invoke-Pester syntax

Write focused Java unit tests with JUnit 5, including tests that repeat checks across different inputs. Covers clear test structure, exception checks, mock objects that replace dependencies, and ways to organize test suites.

• Writing a unit test for a Java method
• Checking the same behavior with multiple input values
• Testing exceptions and related assertions

Write JavaScript and TypeScript tests with Jest using consistent structure, dependency mocking, and checks for asynchronous code. Includes guidance for snapshots and React components, focusing on user interactions, accessibility, and choosing appropriate assertions for expected results.

• Organize Jest test files and test names
• Replace API or database dependencies with mocks
• Test asynchronous results and errors

Write C# unit tests with TUnit using clear test structure, asynchronous checks, and multiple input cases. Get guidance on setup and cleanup, execution controls, test organization, and converting existing xUnit tests to TUnit.

• Setting up a TUnit test project
• Testing one behavior with multiple input cases
• Organizing test setup and cleanup

Review and improve .NET/C# code against project conventions. Cover public API documentation, dependency injection for supplying services to classes, asynchronous operations, tests, configuration, logging, and input validation, including guidance for Semantic Kernel integrations.

• Review C# code against project conventions
• Improve XML documentation for public APIs
• Review asynchronous operations and dependency injection

Write C# unit tests with NUnit using clear naming, focused assertions, and independent test cases. Covers project setup, testing with multiple input values, exception checks, and replacing dependencies with mocks to test components in isolation.

• Setting up an NUnit test project
• Testing the same behavior with multiple inputs
• Checking exceptions and collection contents

Write focused C# unit tests with XUnit, including tests that run against multiple input datasets. Apply consistent naming, setup, assertions, shared fixtures, and mock dependencies to keep tests readable, independent, and organized.

• Set up an XUnit test project for C#
• Test multiple input cases with Theory and data attributes
• Check exceptions and isolate dependencies with mocks

Investigate CUDA crashes in SGLang using logs and inputs saved before execution. Inspect tensor shapes, data types, and numerical anomalies, with guidance for separate process logs and additional CUDA debugging tools.

• Investigating illegal memory access and device-side assertions
• Tracing NaN or Inf values through kernel calls
• Saving inputs before a CUDA crash

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