'assertion' 검색 결과

Fix "ref.listen can only be used within the build method of a ConsumerWidget" assertion error in Flutter Riverpod 3.x. Use when: (1) ConsumerStatefulWidget crashes with "Failed assertion: line 492 pos 7: 'debugDoingBuild'" in flutter_riverpod consumer.dart, (2) ref.listen is called inside initState, addPostFrameCallback, or any lifecycle method other than build(), (3) All widget tests fail with this assertion from scheduler callback. Applies to flutter_riverpod 3.0+ with ConsumerStatefulWidget.

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

Automatically infer formal correctness properties from Verilog/SystemVerilog RTL code and generate SystemVerilog Assertions (SVA). Identifies control-flow invariants (mutual exclusion, valid-ready handshakes, pipeline ordering, safety properties), liveness expectations, and temporal properties. Use when working with RTL designs that need formal property generation, when adding assertions to existing RTL, or when users ask to infer properties, generate assertions, or create formal specifications from hardware designs.

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

Automatically infer loop invariants for code verification and correctness proofs. Use when analyzing loops to identify properties that hold throughout execution, generating assertions for verification, proving loop correctness, or documenting loop behavior. Supports Python, Java, C/C++, and language-agnostic analysis. Generates invariants as code assertions (assert statements). Triggers when users ask to infer invariants, find loop properties, generate loop assertions, prove loop correctness, or verify loop behavior.

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

Generate test assertions from existing code implementation. Use when the user has implementation code without tests or incomplete test coverage, and needs assertions synthesized by analyzing the code's behavior, inputs, outputs, and state changes. Supports Python (pytest/unittest), Java (JUnit/AssertJ), and JavaScript/TypeScript (Jest/Chai). Handles equality checks, collections, exceptions, and state verification.

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

SAML SSO assertion attack playbook. Use when testing signature validation, assertion wrapping, audience restrictions, ACS handling, XML trust boundaries, and enterprise SSO flaws.

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

.NET testing fundamentals overview and navigation center. Triggered when users ask about "how to write .NET tests", ".NET testing getting started", "required testing tools", "testing best practices", "learn testing from scratch", and other general testing needs. Recommends appropriate sub-skills based on specific requirements, covering testing fundamentals, test data, assertions, mocking, special scenarios, and other 19 fundamental skills. Keywords: dotnet testing, .NET testing, testing getting started, how to write tests, testing best practices, unit test, unit test, xunit, 3A pattern, FIRST principle, assertion, assertion, mock, stub, NSubstitute, test data, AutoFixture, Bogus, validator, FluentValidation, TimeProvider, IFileSystem, code coverage, ITestOutputHelper, test naming

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

Refactors brittle snapshot tests into resilient, focused assertions. Provides strategies for reducing snapshot size, extracting meaningful assertions, and maintaining snapshots. Use for "snapshot testing", "snapshot refactoring", "brittle tests", or "assertion improvement".

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

Hunting skill for auth bypass vulnerabilities. Built from 12 public bug bounty reports across SAML XSW / parser-differential (GitHub Enterprise CVE-2025-25291/25292), SAML signature stripping (Uber, Rocket.Chat, samlify CVE-2025-47949), SAML domain enforcement bypass via control characters (HackerOne 2024), partner-portal cross-IdP assertion reuse (Slack), WordPress XMLRPC bypassing SSO (Uber), JWT alg-confusion HS256/RS256 (Jitsi), JWT signature-validation skip (Linktree, Newspack), and token-audience confusion (Argo CD CVE-2023-22482). For standalone JWT signature/crypto forging (alg:none, key confusion, kid/jku) see hunt-jwt-crypto; this skill covers JWT only inside SSO/SAML/token-trust bypass chains. SAML assertion-layer attacks (XSW, comment injection, signature stripping, XXE-in-assertion) are owned by hunt-saml; this skill owns the broader cross-protocol auth-bypass taxonomy. Use when hunting auth bypass — see the Legacy-Protocol Matrix for branded-UI vs legacy-endpoint patterns.

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

xUnit 등의 구현 예제로 C#과 .NET 테스트를 작성하고 검토합니다. 단위 테스트, API·데이터베이스 통합 테스트와 테스트 데이터 및 배치를 다룹니다.

• C# 서비스에 테스트를 추가할 때
• ASP.NET Core API 응답 검증
• 데이터베이스 저장 결과 확인

Retrieve public evidence and linked publications for a supported genetic variant, or look up gene–disease relationships. Preserve sources, conflicting assertions, and explicit search outcomes so qualified professionals can review the findings.

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

• Review public evidence for a single genetic variant
• Find publications linked to a resolved variant
• Look up gene–disease relationships

Stabilize a test that fails and then passes on the same commit. Apply a minimal fix to timing, randomness, clock behavior, or shared resources while preserving assertions, then verify it through repeated runs.

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

• Fixing tests that pass only after a rerun
• Improving timeout budgets and condition-based waiting
• Making clock-dependent or random tests deterministic

Review test files and manual verification records for development tasks. Check whether expected behavior, edge cases, screenshots, and required approvals are covered, then report evidence gaps and distinguish completion blockers from advisory improvements.

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

• Reviewing test evidence for a single development task
• Auditing evidence across a sprint or system
• Checking screenshots and required visual approvals

Evaluate AI agent outputs with code checks and model-based grading. Run repeated trials to measure reliability, compare prompts or models, and check whether changes reduce quality, with saved transcripts for reviewing the results.

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

• Comparing two prompts on the same test cases
• Checking quality after agent configuration changes
• Turning real failures into repeatable evaluation cases

Write and review Apache SeaTunnel unit tests and E2E tests that check complete jobs using Testcontainers. It provides concrete rules for container setup, waiting, resource cleanup, and assertions to address intermittent failures and resource leaks.

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

• Writing a new connector E2E test
• Reviewing a test diff before a pull request
• Fixing intermittent failures or resource leaks in tests

Investigate failing macOS tests in Xcode or SwiftPM by running a focused test scope, classifying errors, and separating setup issues from code regressions. Get a concise explanation of likely causes and the next verification step.

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

• Narrowing down failing macOS tests
• Distinguishing setup issues from code regressions
• Investigating assertions and crashes

Review existing tests using 19 research-backed test smell categories, meaning patterns that can weaken test quality. Get findings ranked by demonstrated risk, with precise code evidence and fixes suited to the test framework in use.

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

• Request a test review using formal academic categories
• Prioritize test problems by their demonstrated risk
• Find causes of flaky tests or misleading passes

Convert .NET tests from xUnit.net v2 or v3 to MSTest v4 while keeping the existing test runner and target framework. Preserve assertions, shared setup, and parallel execution, then compare test counts and outcomes.

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

• Converting xUnit tests to MSTest v4
• Preserving shared setup and parallel execution
• Checking test counts and outcomes after migration

Find changes in observable behavior that existing tests could miss. Map public results to test assertions, identify gaps in boundaries, permissions, and calculations, and propose focused tests, with optional verification when requested.

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

• Check whether existing tests would catch a bug
• Find missing boundary and permission-denial tests
• Review exact amounts and rounding in financial calculations

Convert NUnit 3 or 4 tests to MSTest v4 while keeping the existing target framework and test runner. The workflow translates assertions, test data, setup, and concurrency settings, then compares test counts and results.

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

• Migrating NUnit 3 or 4 tests to MSTest v4
• Preserving parameterized tests and test data
• Reviewing shared state and parallel execution during migration

Keep tests aligned with API changes and actual project files. This skill guides agents to update related tests in the same commit, refresh expected counts and lists, and check stale assertions when automated checks fail.

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

• Updating tests alongside API changes
• Refreshing expected lists after adding or deleting files
• Checking stale assertions when CI fails

Golang struct and interface design patterns — composition, embedding, type assertions, type switches, interface segregation, dependency injection via interfaces, struct field tags, and pointer vs value receivers. Use this skill when designing Go types, defining or implementing interfaces, embedding structs or interfaces, writing type assertions or type switches, adding struct field tags for JSON/YAML/DB serialization, or choosing between pointer and value receivers. Also use when the user asks about "accept interfaces, return structs", compile-time interface checks, or composing small interfaces into larger ones.

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

Provides file paths to language-specific reference files for the test ANALYSIS skills (assertion-quality, test-anti-patterns, test-gap-analysis, test-smell-detection, test-tagging). Read this catalog to discover available extension files (e.g., dotnet.md for .NET/MSTest/xUnit/NUnit/TUnit, python.md for pytest/unittest, typescript.md for Jest/Vitest/Mocha, java.md for JUnit/TestNG, etc.). Do not invoke this reference-only skill — its bundled files are read by the quality agent and analysis skills needing framework-specific lookup tables (test markers, assertion APIs, skip annotations, sleep patterns, mystery guest indicators, integration markers, setup/teardown, tag-support capability).

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

Audits existing tests in any language using formal, research-backed test smell names and the testsmells.org 19-smell academic taxonomy. Use when the caller asks for an academic or citable test-smell review, named smell categories, or a formal severity-ranked smell assessment. Covers Assertion Roulette, Conditional Test Logic, Mystery Guest, Eager Test, Sleepy Test, Unknown Test, Sensitive Equality, and the rest of the catalog across .NET, Python, JavaScript/TypeScript, Java, Go, Ruby, Rust, Swift, Kotlin, PowerShell, and C++. DO NOT USE FOR a quick pragmatic test review (use test-anti-patterns), writing or running tests, framework migration, coverage, or assertion-diversity metrics.

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

Verify application state with AI-powered assertions

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