'test' 검색 결과

Review EXISTING test code for quality, smells, and testability issues. Detects test smells across six dimensions — readability, reliability, diagnostic value, design, AI-generated, and coverage — analyzes testability of application code, and backs the qualitative smells with mutation testing. Use when: "review my tests," "test quality audit," "test smells," "testability analysis," "are these tests any good." Not for: generating new tests — use `ai-test-generation`. Not for: testing AI features in your product — use `ai-system-testing`. Related: unit-testing, shift-left-testing, coverage-analysis, ai-test-generation.

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

ソフトウェアテストを書く時の心得。何をtestし、何をtestしないかの判断基準と、アクセス権限のtestの書き方、fixtureの仮名、落ちたtestの直し方、test runnerを移行する時の確かめ方を定める。 testを書く時、足すか決める時、落ちたtestを直す時、test runnerを移行する時、レビューする時に読み込む。

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

Use when testing, evaluating, or building regression suites for Agentforce agents: conversation testing in Agent Builder, topic (now subagent) coverage and utterance testing, Testing API and AiEvaluationDefinition metadata, Agentforce DX CLI test runs (sf agent generate test-spec, sf agent test create/run/resume/results/list), evaluation metrics (containment rate, escalation rate, CSAT, topic activation accuracy), and post-deploy analytics via Enhanced Event Logs. Triggers: 'how do I test my Agentforce agent', 'agent routes to wrong subagent', 'write utterance tests', 'regression test after topic change', 'measure agent quality', 'agent containment rate', 'run agent tests from the CLI'. NOT for agent creation, topic design, or action contract design — use agentforce/agentforce-agent-creation, agentforce/agent-topic-design, or agentforce/agent-actions respectively.

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

Use when you need to write or improve integration tests for Quarkus — including @QuarkusTest, Dev Services for automatic container provisioning, Testcontainers via QuarkusTestResourceLifecycleManager, WireMock for external HTTP stubs, @QuarkusIntegrationTest for black-box testing against packaged artifacts, REST Assured, data isolation strategies (@TestTransaction vs @BeforeEach cleanup), and Maven Surefire/Failsafe three-tier split (*Test, *IT, *AT). This should trigger for requests such as Add or improve integration tests in a Quarkus project; Configure Testcontainers or Dev Services for Quarkus tests; Add WireMock stubs for external HTTP dependencies in Quarkus integration tests; Set up @QuarkusIntegrationTest for packaged artifact or native binary testing; Fix test data isolation or configure Maven Surefire/Failsafe split. Part of cursor-rules-java project

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

Gates whether a new test should exist and forces it to be efficient, protecting CI from low-value test bloat. Use before any change to what a pytest, Jest, or Playwright test asserts or sets up, down to one fixture or one assertion added to an existing block. Front-loads the value bar (every test must catch a realistic regression no existing test already catches; extend the nearest existing test before writing a new standalone one; test behavior through the public interface, not implementation details; collapse near-duplicates into parameterized cases) and the efficiency bar (deterministic, isolated, fast; pick the cheapest test level; Django TestCase over TransactionTestCase; no sleeps, no real network; no time bombs from absolute dates left to age against the real clock; no database a test never uses). Includes a "don't write it" decision tree. For fixing an existing flaky test use `/fixing-flaky-tests`; after this gate says a Playwright test is warranted, use `/playwright-test` for mechanics.

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

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

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

Add end-to-end tests, which check complete usage flows, and API tests for features that already work. Follow the project's existing test setup to extend automated coverage without introducing a separate testing approach.

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

• Adding automated tests to an existing feature
• Testing complete usage flows with E2E tests
• Adding API tests using the existing test setup

Plan tests for APIs, interfaces, data pipelines, and infrastructure. Choose suitable test types, prioritize critical behavior, and produce a plan with coverage targets and example cases while balancing thoroughness, execution speed, and maintenance effort.

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

• Planning tests for a new feature
• Finding gaps in existing test coverage
• Choosing test types for APIs and interfaces

Write and update Handsontable unit tests with Jest and type tests with TypeScript. Explains file placement, focused test runs, boundary cases, and checks for public types, while helping choose between isolated logic tests and browser tests.

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

• Adding unit tests for calculations and data transformations
• Covering bug fixes and internal refactoring
• Checking TypeScript declarations and public exports

Plan tests for APIs, interfaces, data pipelines, and infrastructure. Choose suitable test types, prioritize critical behavior, and produce a plan with coverage targets and example cases while balancing thoroughness, execution speed, and maintenance effort.

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

• Planning tests for a new feature
• Finding gaps in existing test coverage
• Choosing test types for APIs and interfaces

Migrate .NET tests from xUnit.net v2 to v3 while preserving the existing test runner. Update packages, project settings, and affected test code, then verify test discovery, execution, and skip behavior.

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

• Upgrading xUnit.net v2 test projects to v3
• Fixing compilation errors caused by v3 changes
• Updating custom test attributes and async tests

Find source files with no matching test references by parsing code without building or running tests. Produces a source-to-test map and suggested test locations, helping plan test additions across supported programming languages.

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

• List source files with no matching tests
• Choose locations for new test files
• Check source-to-test pairing after adding tests

Applies proven testing patterns — Arrange-Act-Assert (AAA), Given-When-Then, Test Data Builders, Object Mother, parameterized tests, fixtures, spies, and test doubles — to help write maintainable, reliable, and readable test suites. Use when the user asks about writing unit tests, integration tests, or end-to-end tests; structuring test cases or test suites; applying TDD or BDD practices; working with mocks, stubs, spies, or fakes; improving test coverage or reducing flakiness; or needs guidance on test organization, naming conventions, or assertions in frameworks like Jest, Vitest, pytest, or similar.

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

Writes and migrates Swift Testing framework tests with @Test, @Suite, #expect, #require, confirmation, traits, withKnownIssue, Attachment.record, processExitsWith exit tests and capture lists, Test.cancel, Issue.record warnings/manual failures, XCTest-to-Swift Testing migration, Xcode 27 interoperability modes, XCUITest UI-test boundaries, performance/snapshot boundaries, mocking, async patterns, and test organization. Use when writing tests, converting XCTest assertions such as XCTUnwrap or XCTFail, reviewing advanced Swift Testing API availability, or deciding when to keep XCTest/XCUITest.

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

Audit a test file or suite; produce a severity-ranked diagnostic report. ALWAYS USE for tests that verify nothing, missing/tautological assertions, swallowed/broad exceptions, flaky/order-dependent tests, duplication, or magic values. Polyglot. DO NOT USE for direct edits: writing-mstest-tests owns supplied MSTest assertions/attributes/lifecycle; code-testing owns new tests. Exclude running tests, migration, assertion metrics (assertion-quality), raw .NET coverage collection (run-tests), non-.NET coverage collection/analysis (native tooling), project-wide .NET coverage/CRAP (coverage-analysis), named-target .NET CRAP (crap-score), behavioral/pseudo-mutation gaps (test-gap-analysis), test-mix/ happy-vs-error classification and trait distributions (test-tagging), or the testsmells.org catalog (test-smell-detection).

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

Use this skill before answering, planning, or editing whenever .NET tests or CI are switching from VSTest to Microsoft.Testing.Platform (MTP), or an MTP migration behaves differently. Triggers include "switch from VSTest"; MSTest/NUnit/xUnit MTP enablement; OutputType=Exe only for test projects in Directory.Build.props; EnableMSTestRunner, EnableNUnitRunner, UseMicrosoftTestingPlatformRunner, or YTest.MTP.XUnit2; .NET 10 global.json test.runner and TestingPlatformDotnetTestSupport; translating VSTest filters, logger, coverage, blame, or dump arguments; replacing VSTest@3; and exit code 8 or zero tests. Also use for xUnit v3 MTP filters during a v2-to-v3 upgrade. Do not use for framework conversion, TFM, UWP, or WinUI.

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

Identifies non-deterministic or unreliable tests through static code analysis and test result analysis. Use when Claude needs to find flaky tests, analyze test reliability, or investigate intermittent test failures. Supports Python (pytest, unittest) and Java (JUnit, TestNG) test frameworks. Trigger when users mention "flaky tests", "intermittent failures", "non-deterministic tests", "unreliable tests", or ask to "find flaky tests", "analyze test stability", or "why tests fail randomly".

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

Validate database integrity, test migrations forward and backward, verify schema constraints, manage seed data, detect migration drift, and identify query performance issues. Covers PostgreSQL, MySQL, MongoDB with Prisma, TypeORM, Drizzle, and SQLAlchemy, plus Testcontainers test databases. Use when: "database test," "migration test," "migration rollback," "rollback test," "data integrity," "SQL test," "schema validation," "seed data," "query performance," "Testcontainers." Not for: synthetic data generation/masking at scale — use test-data-management; Docker/IaC test-environment provisioning — use test-environments; SQL injection — use security-testing. Related: test-data-management, test-environments, security-testing, ci-cd-integration.

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

Test application security against OWASP Top 10 (2025) with automated CI tooling: OWASP ZAP (DAST), dependency/supply-chain scanning (OSV-Scanner, SBOM, provenance), Semgrep SAST, auth/session tests (JWT, OAuth, RBAC), and XSS/CSRF/SQLi/SSRF Playwright patterns. Use when: "security test," "OWASP," "vulnerability," "ZAP," "XSS," "SSRF," "dependency scan," "auth testing," "OWASP LLM Top 10." Scope is automated scanning + negative-path security tests in CI, not manual penetration testing. Not for: mapping security controls to regulations (SOC 2, HIPAA, PCI, GDPR) — use compliance-testing; pipeline stage wiring and deploy gating mechanics — use ci-cd-integration; purely functional API auth/input tests with no attacker model — see api-testing; testing your product's own LLM features or defending the agent itself (prompt-injection detector, indirect injection, jailbreak red-teaming) — use ai-system-testing. Related: ci-cd-integration, compliance-testing, api-testing, shift-left-testing, ai-system-testing.

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

Plan and run manual tests of the project's running app. Runs a session in one of five modes: exploratory, verification, smoke, assessment (UX, localization, accessibility, improvement review), or AI probe. Also writes a manual test plan that holds only what automated tests cannot judge. Use whenever the user asks, in any language, for something to be tested by hand or for a manual test plan — "manual test", "exploratory test", "bug hunt", "verify the bug fix", "smoke test", "QA this screen", "review this screen's UX", "what would you improve", "check the localized copy", "test the AI agent's answers", "write manual test cases", "kịch bản test manual" — or assigns a test design, test plan or test-case IDs to execute by hand. Not for writing automated tests.

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

Design and write QA test artifacts - test cases, test plans, acceptance criteria, API test specs, and PR testability reviews. Use this skill whenever a QA engineer or SDET needs to translate requirements, user stories, or feature specs into structured test documentation. Trigger on phrases like "write test cases", "create a test plan", "define acceptance criteria", "review this PR for testability", "write API test specs", "test coverage for this feature", "what should we test", "how do we test this", or any request to structure what and how to test before execution begins. Also trigger when a developer asks "is this testable?" or a PM asks "what are the edge cases?".

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

Specialized skill for ASP.NET Core integration testing. Use when testing Web API endpoints, HTTP request/response, middleware, and dependency injection. Covers WebApplicationFactory, TestServer, HttpClient testing, in-memory database configuration. Keywords: integration testing, web api testing, WebApplicationFactory, TestServer, HttpClient testing, controller testing, endpoint testing, RESTful API testing, Microsoft.AspNetCore.Mvc.Testing, CreateClient, ConfigureWebHost, AwesomeAssertions.Web, Be200Ok, Be404NotFound, middleware testing, dependency injection testing

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

Complete guide for .NET Aspire Testing integration testing framework. Use when testing .NET Aspire distributed applications, configuring AppHost tests, or migrating from Testcontainers to Aspire testing. Covers DistributedApplicationTestingBuilder, container lifecycle management, multi-service orchestration, Respawn configuration, and time testability design. Keywords: aspire testing, .NET Aspire, DistributedApplicationTestingBuilder, AppHost testing, distributed testing, AspireAppFixture, IAsyncLifetime, ContainerLifetime.Session, cloud-native testing, multi-service integration, Aspire.Hosting.Testing, Respawn

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

Rust 구현과 버그 수정을 실패하는 테스트부터 진행합니다. 통과에 필요한 최소 구현, 동작을 유지하는 리팩터링, 코드 서식·정적 분석·테스트 확인까지 다룹니다.

• 테스트부터 작성해 Rust 기능 추가
• 테스트로 버그를 재현한 뒤 수정
• 잘못된 입력과 오류 경로 테스트