“assertion”的搜索结果

Verify application state with AI-powered assertions

中文简介正在准备中。当前显示原文说明。

Locate elements and verify app state with AI-powered assertions

中文简介正在准备中。当前显示原文说明。

Add new assertion function with comprehensive tests following TDD

中文简介正在准备中。当前显示原文说明。

Generates automated test oracles to verify correct software behavior. Creates assertion-based oracles (expected values), property-based oracles (invariants), differential oracles (comparing implementations), and metamorphic oracles (input transformations). Use when you need to generate assertions for test cases, identify invariants that should always hold, compare new vs legacy implementations, create metamorphic test relationships, validate function correctness, or improve test coverage with better verification strategies. Supports Python (pytest, unittest, hypothesis) and Java (JUnit, property testing).

中文简介正在准备中。当前显示原文说明。

Generate concrete counterexamples when formal verification, assertions, or specifications fail. Use this skill when debugging failed proofs, understanding why verification fails, creating minimal reproducing examples, analyzing assertion violations, investigating invariant breaks, or diagnosing specification mismatches. Produces concrete input values, execution traces, and state information that demonstrate the failure.

中文简介正在准备中。当前显示原文说明。

Explain why counterexamples violate specifications by analyzing formal specifications (temporal logic, invariants, pre/postconditions, code contracts), informal requirements (user stories, acceptance criteria), test specifications (assertions, property-based tests), and providing step-by-step traces showing state changes, comparing expected vs actual behavior, identifying root causes, and assessing violation impact. Use when debugging test failures, understanding model checker output, explaining runtime assertion violations, analyzing static analysis warnings, or teaching specification concepts. Produces structured markdown explanations with traces, comparisons, state diagrams, and cause chains. Triggers when users ask why something failed, explain a violation, understand a counterexample, debug a specification, or analyze why a test fails.

中文简介正在准备中。当前显示原文说明。

Use production telemetry as INPUT to design new tests. Covers OpenTelemetry integration with tests, trace-based assertions, log-informed test creation, production-error analysis for coverage gaps, and telemetry-driven test prioritization. Use when: "trace-based testing," "design tests from logs," "OpenTelemetry assertions," "production errors point to test gaps," "telemetry-driven testing." Not for: safe rollout techniques (flags, canary) during release — use testing-in-production. Not for: scheduled post-deploy probes — use synthetic-monitoring. Not for: triaging CI failures — use ai-bug-triage. Related: testing-in-production, synthetic-monitoring, qa-metrics, ai-bug-triage.

中文简介正在准备中。当前显示原文说明。

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).

中文简介正在准备中。当前显示原文说明。

検査器（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 へ委譲する

中文简介正在准备中。当前显示原文说明。

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.

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

将规格或需求整理成实施计划，明确要修改的文件、函数定义、测试和验证步骤。在编写代码前拆分工作，形成可交给其他人员或代理执行的任务。

• 编写代码前规划功能实施
• 将需求拆成可测试的任务
• 向其他人员或代理交接实施工作

在报告任务完成或修复成功前运行测试、构建等检查，核对完整输出，并在提交修改或创建拉取请求前，以当前实际结果为依据说明状态。

• 报告完成前核对结果
• 验证问题是否修复
• 提交或创建拉取请求前验证

围绕用户操作与可见结果，为React组件和钩子编写或修复测试，模拟网络响应并检查无障碍问题，同时判断哪些内容需要在真实浏览器中验证。

• 为React表单和组件补充测试
• 验证自定义钩子与异步更新
• 模拟API成功与失败响应

将项目质量标准及其数值、理由和检查方法写入文档，并从差异中检查跳过测试、抑制警告或降低门槛的改动，维持智能体开发质量。

• 制定智能体开发的质量标准
• 选择覆盖率与性能目标
• 发现跳过测试或抑制警告

为Paperclip Runner添加或扩展行为评估，定义判定条件、执行目标和报告验证数据，利用正常及异常证据验证结果，并保留执行记录与费用。

• 添加Runner行为评估
• 用有效与无效证据检验判定
• 更新执行列表和持续评估

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 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