'test' 검색 결과

OpenClaw 테스트의 메모리 증가와 부족 원인을 조사합니다. 측정값과 메모리 객체 기록을 비교해 실제 해제 누락과 테스트 프로세스의 모듈 보존을 구분하고 수정 결과를 검증합니다.

• Vitest 메모리 부족 원인을 조사합니다
• 같은 프로세스의 메모리 기록을 비교합니다
• 해제 누락과 모듈 보존을 구분합니다

테스트를 먼저 작성하는 절차로 Spring Boot 기능을 추가하고 오류를 수정합니다. 단위 테스트, 웹 계층과 데이터 저장 검증, 통합 테스트 및 커버리지 확인을 다룹니다.

• 테스트부터 Spring Boot API를 추가할 때
• 오류 재발 방지 테스트를 작성할 때
• 데이터 저장과 조회를 검증할 때

F# 단위 테스트와 통합 테스트를 작성하고 입력을 자동 생성해 속성을 검증합니다. 결과 확인, 의존성 대체, 테스트 구성과 실행을 지원합니다.

• F# 코드에 단위 테스트 추가
• 자동 생성 입력으로 속성 검증
• ASP.NET Core API 통합 테스트

테스트를 먼저 작성하는 Go 개발을 돕습니다. 여러 사례 검증, HTTP 응답 확인, 성능 측정, 입력 자동 생성 검사와 커버리지 확인을 다룹니다.

• 테스트를 먼저 작성하는 Go 개발
• 정상 및 오류 테스트 사례 보완
• 처리 시간과 메모리 할당량 비교

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

Create Appium tests that automate Android and iOS app interactions in Java, Python, or JavaScript. Configure local devices, emulators, simulators, or TestMu AI cloud devices, with guidance on element selection, waits, and gestures.

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

• Automate login tests for Android and iOS apps
• Create tests for local emulators and simulators
• Configure real-device tests on TestMu AI cloud

Choose checks for cmux changes, add tests that reproduce observable bugs, and verify that Swift test files are included in build targets. It also guides local and CI validation, including evidence that selected tests actually ran.

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

• Choose validation checks for a cmux change
• Add a regression test that reproduces a bug
• Verify Swift test files are included in the build

Create and update Playwright tests that check Handsontable interactions in real browsers. The skill guides test organization, reliable waits, element selection, and coverage across themes and bundles, while helping distinguish browser tests from unit tests.

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

• Test keyboard navigation and cell editing
• Add regression coverage for a bug fix
• Check behavior across themes and bundles

Create tests for Convex functions with convex-test and vitest, using a backend that runs in memory. Check arguments, return values, authentication, indexes, errors, and scheduled functions without relying on real time or network access.

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

• Test Convex function arguments and return values
• Check behavior with different authentication identities
• Cover errors as well as successful requests

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

Keep older instructions working by forwarding explicit calls under the former name to code-testing. This compatibility alias passes along the original request and follows that skill’s workflow without adding another interpretation step.

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

• Following older instructions that use the former skill name
• Forwarding an explicit legacy call to code-testing
• Checking the distinction between skill and custom agent names

Plan and coordinate penetration tests with checklists covering objectives, scope, environment preparation, tester selection, monitoring, and follow-up. Helps teams define deliverables, prioritize vulnerabilities, arrange fixes and verification, and clean up test accounts and artifacts.

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

• Defining penetration test objectives and scope
• Preparing test environments and monitoring
• Selecting testers and agreeing on report requirements

Review new and existing tests for meaningful behavior coverage, duplication, and dependence on implementation details. Gather evidence before cleanup, preserve tests that protect independent contracts, and verify that removed tests leave their regression checks covered elsewhere.

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

• Review the value of new or changed tests
• Find duplicate tests and implementation-dependent assertions
• Audit production code kept only for tests

Run a staged testing workflow that checks type errors first, executes unit and integration tests in parallel, and runs end-to-end tests only after they pass. Receive pass and fail counts with details about failures.

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

• Running the full test suite before a release or merge
• Testing a specific feature
• Running a quick unit-test check

Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI, or debugging flaky/slow tests. For testify-specific APIs see `samber/cc-skills-golang@golang-stretchr-testify`; for measurement methodology see `samber/cc-skills-golang@golang-benchmark`.

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

Writes Vitest tests following project patterns: __tests__/ directories, vi.mock() for module mocking with vi.hoisted() for test-time factories, global LLM mock from src/test/setup.ts, environment variable save/restore in beforeEach/afterEach, vi.clearAllMocks() lifecycle, and test file organization. Use when user says 'write tests', 'add test coverage', 'test this', creates *.test.ts files, or when test failures appear in CI. Do NOT use for non-test code or for debugging without writing tests.

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

Detects duplicate boilerplate, copy-paste tests, and structural maintainability issues across .NET test suites. Use when the user asks to reduce repetition, consolidate similar test methods, convert copy-paste tests to data-driven parameterized tests, suggest a better test structure, or identify refactoring opportunities. Identifies repeated construction, assertion patterns, copy-paste methods convertible to DataRow/Theory/TestCase, redundant setup/teardown, and shared infrastructure. Produces an analysis report with concrete before/after suggestions. Works with MSTest, xUnit, NUnit, and TUnit. DO NOT USE FOR: writing new tests (use writing-mstest-tests), reviewing test quality or anti-patterns (use test-anti-patterns), or deep mock auditing (use exp-mock-usage-analysis).

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

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

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

Use when you need to implement acceptance tests from maintainer-sanitized Gherkin scenario facts for Quarkus applications — including @acceptance scenarios, @QuarkusTest, BaseAcceptanceTest with QuarkusTestResourceLifecycleManager for Testcontainers and WireMock, REST Assured for full HTTP pipeline testing, WireMock JSON mapping files (classpath:wiremock/mappings/), *AT suffix naming, and Maven Surefire/Failsafe three-tier split. Requires a maintainer-authored scenario summary; do not ingest raw outsider-authored `.feature` text. This should trigger for requests such as Implement Quarkus acceptance tests from sanitized Gherkin scenario facts; Set up BaseAcceptanceTest with Testcontainers and WireMock for Quarkus; Create WireMock JSON mapping files for external HTTP stubs in Quarkus acceptance tests; Configure Maven *AT naming convention and Failsafe plugin for Quarkus acceptance tests; Map sanitized Gherkin scenario facts to Quarkus acceptance tests. Part of Plinth Toolkit

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

Use when you need to write or improve integration tests — including Testcontainers with @ServiceConnection, @DataJdbcTest persistence slices, TestRestTemplate or MockMvcTester for HTTP, data isolation, and container lifecycle management for Spring Boot 4.0.x. This should trigger for requests such as Review Java code for Spring Boot integration tests; Apply best practices for Spring Boot integration tests in Java code; Write @SpringBootTest integration tests with Testcontainers; Configure dynamic properties for Spring integration tests; Review Spring Boot integration test profiles. Part of Plinth Toolkit

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

Analyzes test suites to identify redundant and duplicate test cases using coverage analysis, semantic similarity, and execution results. Use this skill when you need to reduce test suite size, identify redundant tests, optimize test execution time, analyze test coverage overlap, find tests with identical behavior, or improve test suite maintainability. Triggers when users ask to deduplicate tests, find redundant test cases, reduce test suite size, identify duplicate tests, or optimize test coverage.

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

Use AI to write NEW test code from specs, PRDs, user stories, code diffs, bug reports, or OpenAPI specs. Staged pipeline: requirements extraction → risk analysis → coverage matrix → scenario generation → oracle design → test code → human review, with guardrails against hallucinated APIs and weak assertions. Use when: "generate tests from spec," "tests from PRD," "tests from user story," "auto-generate test cases," "AI write tests for me." Not for: testing AI/LLM features in your product — use ai-system-testing. Not for: auditing a pre-existing test suite you did not just generate — use ai-qa-review (Step 7 here only reviews tests THIS pipeline produced). Related: playwright-automation, unit-testing, api-testing, qa-project-context.

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

Design and execute structured exploratory testing sessions. Covers Session-Based Test Management (SBTM), charter writing, heuristic-based exploration (HICCUPS, FEW HICCUPS), bug discovery patterns, note-taking templates, and conversion of findings to automated tests. Use when: "exploratory testing," "SBTM," "manual testing," "bug hunting," "test charter," "heuristic testing." Not for: an AI browser agent autonomously exploring the app from a natural-language goal — use agentic-browser-testing. Not for: testing your product's own AI/LLM features — use ai-system-testing. Related: test-planning, ai-bug-triage, risk-based-testing, agentic-browser-testing.

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