'tests' 검색 결과

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

Plan and write tests for changes to agent behavior, favoring integration tests that check components together. Identify key logic changes and user-visible behavior to cover, reuse existing helpers, and keep unit tests in dedicated files.

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

• Identify test coverage for changes to agent logic
• Add integration tests for user-visible behavior
• Organize unit tests in dedicated files

Check whether tests detect faults in changed Python code by deliberately modifying the changed lines. Add tests for missed behavior, confirm which tests fail against the previous code, and report measured evidence alongside any remaining gaps.

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

• Verify test coverage for a Python feature or fix
• Add tests for faults the current suite misses
• Confirm new tests fail against the previous code

Choose and run checks for TypeScript SDK changes, including type checks, linting, builds, Vitest suites, and tests of complete runtime flows. Also guides writing or adapting CLI tests for Effect v4.

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

• Validate changes to TypeScript packages
• Choose focused checks for a change
• Investigate failing TypeScript CI checks

Create or improve unit tests for Apache ShardingSphere classes. Cover the target class’s behavior and affected branches, verify explicitly requested coverage goals, and consolidate suitable scenarios into parameterized tests, which run the same checks with different inputs.

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

• Add missing unit tests for a target class
• Verify an explicitly requested coverage target
• Consolidate suitable tests with different input data

Build end-to-end tests that follow user journeys in browsers and mobile simulators or emulators. Guides e2e configuration, AI-driven actions, precise outcome checks, failure investigation, and exploratory bug hunts backed by reproducible tests.

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

• Testing browser user journeys with AI-driven actions
• Checking app flows on mobile simulators and emulators
• Investigating failed tests through reports and traces

Create unit, integration, and E2E tests that check complete user flows, then identify coverage gaps and investigate unreliable results. The skill also supports performance and security test plans, with findings organized by severity and suggested fixes.

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

• Writing tests for normal behavior, errors, and boundary values
• Finding gaps in test coverage
• Investigating tests that fail intermittently

Evaluate how well existing tests catch code changes, then combine the results with function relationships. Get a report separating harmless findings, missing unit tests, and targets for fuzzing, which tests many generated inputs.

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

• Triage code changes that existing tests failed to catch
• Prioritize missing unit tests
• Find functions suited to fuzzing

Generate tests for a specified file or module using the project’s testing conventions. Cover expected behavior, unusual inputs, boundaries, failures, and external interactions, with independent tests and mock substitutes for external dependencies.

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

• Add tests for existing functions or modules
• Check empty inputs and boundary values
• Test failures in APIs, databases, and file operations

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

Correct and improve existing MSTest tests using APIs supported by the installed version. Refine assertions and failure messages, update data-driven tests, fix setup and cleanup, and address MSTest diagnostics while preserving the project's established conventions.

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

• Making assertion failures easier to understand
• Correcting expected and actual argument order
• Improving existing data-driven tests

Review existing tests to see whether their assertions, the checks that verify expected behavior, are meaningful and varied. Get metrics, examples of weak checks, and specific recommendations for improving verification.

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

• Reviewing whether passing tests check meaningful behavior
• Finding tests with missing or trivial assertions
• Measuring the variety of checks across a test suite

Analyze .NET test suites for repeated setup, assertions, and copied test methods. Get a report with file locations, before-and-after refactoring examples, priorities, and readability trade-offs, without changing the source files.

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

• Finding repeated setup and assertions
• Combining copied tests into parameterized tests
• Identifying shared setup and cleanup opportunities

This skill should be used when the user asks to "write a test", "review these tests", "audit tests", "prune low-value tests", or "find duplicate tests", and whenever writing, changing, reviewing, or sweeping tests. Gates new tests and audits low-value, implementation-coupled, or duplicative tests and the test-only production seams they demand.

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

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 when you need to write unit tests for Micronaut applications — Mockito-first with @ExtendWith(MockitoExtension.class), @MicronautTest with @MockBean, HttpClient @Client(/) assertions, @Property overrides, @ParameterizedTest, and *Test vs *IT naming. For framework-agnostic Java use @131-java-testing-unit-testing. This should trigger for requests such as Add or improve unit tests in a Micronaut project; Reduce unnecessary @MicronautTest usage with Mockito-first tests; Write Mockito-first unit tests for Micronaut services; Mock Micronaut bean collaborators in unit tests; Review fast Micronaut tests without application context. Part of Plinth Toolkit

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

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

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

Generate and run tests for Adobe App Builder actions and UI components. Scaffolds Jest unit tests, integration tests against deployed actions, contract tests for Adobe API interactions, and React component tests using Testing Library. Provides mock helpers for State, Files, Events SDKs, @adobe/aio-lib-* clients, ExC Shell context (@adobe/exc-app), and UIX Guest SDK (@adobe/uix-guest). Use this skill whenever the user mentions testing App Builder actions, writing unit tests for Runtime actions, creating integration tests, mocking Adobe SDKs, setting up test fixtures, running aio app test, or wants to verify action behavior before deployment. Also trigger when users mention Jest configuration for App Builder, test coverage, CI test setup, React component test, Testing Library, UI test, Provider wrapper, test my page, test my form, test my table, test my component, mock shell context, mock extension context, debug test failures, or fix Jest errors.

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

Generate and run tests for Adobe App Builder actions and UI components. Scaffolds Jest unit tests, integration tests against deployed actions, contract tests for Adobe API interactions, and React component tests using Testing Library. Provides mock helpers for State, Files, Events SDKs, @adobe/aio-lib-* clients, ExC Shell context (@adobe/exc-app), and UIX Guest SDK (@adobe/uix-guest). Use this skill whenever the user mentions testing App Builder actions, writing unit tests for Runtime actions, creating integration tests, mocking Adobe SDKs, setting up test fixtures, running aio app test, or wants to verify action behavior before deployment. Also trigger when users mention Jest configuration for App Builder, test coverage, CI test setup, React component test, Testing Library, UI test, Provider wrapper, test my page, test my form, test my table, test my component, mock shell context, mock extension context, debug test failures, or fix Jest errors.

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

사용자 조작과 화면 결과를 중심으로 React 컴포넌트와 훅을 테스트합니다. 통신 응답 모의와 접근성 점검을 지원하고 실제 브라우저에서 검증할 범위도 정리합니다.

• React 폼과 컴포넌트 테스트 추가
• 사용자 정의 훅과 비동기 갱신 검증
• API 성공 및 실패 응답 모의

테스트를 먼저 작성하는 흐름으로 Rust 단위·통합·비동기 테스트를 구성합니다. 다양한 입력 검증, 의존성 대체, 성능 측정과 커버리지 확인도 다룹니다.

• 테스트부터 Rust 코드 개발
• 기존 코드에 테스트 추가
• 비동기 처리와 시간 초과 검증

PHPUnit 또는 Pest로 Laravel 기능을 테스트부터 구현합니다. 모델, API, 인증과 권한을 검증하고 외부 서비스를 모의 처리하며 테스트가 실행한 코드 범위를 확인합니다.

• Laravel 기능을 테스트부터 구현합니다
• API 인증과 권한을 검증합니다
• 결제, 메일과 큐를 모의 처리합니다

Kotlin 테스트를 먼저 작성하고 Kotest와 MockK로 동작과 의존성을 검증합니다. 비동기 테스트부터 Kover를 통한 커버리지 확인까지 진행합니다.

• 기존 Kotlin 코드에 테스트 추가
• 테스트를 먼저 작성해 새 기능 개발
• 코루틴과 Flow 동작 검증

C++ 테스트 작성과 수정, GoogleTest·CTest 설정, 실패 원인 조사를 돕습니다. 불안정한 테스트 개선, 커버리지 측정과 실행 중 메모리 오류·동시성 경쟁 검사도 다룹니다.

• C++ 단위·통합 테스트를 작성합니다
• GoogleTest와 CTest를 설정합니다
• 불안정한 테스트의 원인을 조사합니다