メニュー
Comprehensive testing strategies including TDD, unit, integration, E2E, and property-based testing. Ensures code quality and prevents regressions. Use when writing tests, implementing features test-first, or improving coverage.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | testing |
| description | Comprehensive testing strategies including TDD, unit, integration, E2E, and property-based testing. Ensures code quality and prevents regressions. Use when writing tests, implementing features test-first, or improving coverage. |
Testing strategies for code quality and regression prevention.
# 1. Find existing test patterns
serena.search_for_pattern("test|spec|describe", relative_path="test/")
# 2. Check test utilities
serena.get_symbols_overview(relative_path="test/support/")
# 3. Find similar tests
serena.find_symbol("*Test", depth=1, include_body=False)
# 4. Framework testing patterns
context7.get-library-docs("<testing-framework>", topic="testing")
/\
/E2E\ Few, slow, high confidence
/------\
/Integration\ Some, medium speed
/--------------\
/ Unit Tests \ Many, fast, focused
/------------------\
- Write minimal test for expected behavior
- Run test - verify it FAILS correctly
- Commit: "test: add failing test for [feature]"
- Write minimal code to pass
- Run test - verify it PASSES
- Commit: "feat: implement [feature]"
- Improve code structure
- Run tests - must still pass
- Commit: "refactor: improve [component]"
test "should [behavior] when [condition]":
# Arrange - setup
input = create_test_input()
sut = create_system_under_test()
# Act - execute
result = sut.execute(input)
# Assert - verify
assert result.status == expected
| Type | Purpose | Use When |
|---|---|---|
| Stub | Canned responses | Predictable input |
| Mock | Verify interactions | Verify calls |
| Spy | Record + real impl | Both needed |
| Fake | Working test impl | Real is slow |
Mock at boundaries: external APIs, databases, file systems. Don't mock: private methods, value objects, simple utilities.
1. REPRODUCE: Write failing test
2. VERIFY: Confirm it fails correctly
3. FIX: Implement minimal fix
4. CONFIRM: Test passes
5. EXPAND: Add edge case tests
## Testing: [Scope]
| Category | Count | Status |
|----------|-------|--------|
| Unit | N | PASS/FAIL |
| Integration | M | PASS/FAIL |
### New Tests
1. `test_should_create_when_valid`
2. `test_should_reject_duplicate`
### Issues
- [failures or gaps]
JetBrains MCP 도구를 활용한 빠른 개발 워크플로우. IDE 검사, Run Configuration 실행, 리팩토링, 파일 검색 등을 통해 Gradle 의존도를 줄이고 개발 속도를 10배 향상시킵니다. Kotlin/Spring 개발 시 필수로 사용하세요.
Kotlin testing with JUnit 5, MockK, Spring test slices, and fast feedback commands. Provides single test execution, incremental builds, and JetBrains MCP integration for rapid TDD cycles. Use when writing tests for Kotlin/Spring code, running specific tests, or debugging test failures.
Kotlin testing with JUnit 5, MockK, Spring test slices, and Testcontainers. Provides mocking patterns, test slice selection, and TDD workflow for Spring Boot + Kotlin. Use when writing tests for Kotlin/Spring code, setting up test infrastructure, or debugging test failures.
System architecture analysis and design. Validates architecture patterns, generates dependency graphs, and evaluates module boundaries. Use when analyzing structure, checking layer compliance, or making design decisions.
Token-efficient codebase exploration using MCP-first approach. Locates functions, classes, patterns, and traces dependencies with 80-90% token savings. Use when searching code, finding implementations, or tracing call chains.
Hypothesis-driven debugging with systematic investigation. Identifies root causes, creates minimal reproductions, and implements fixes. Use when investigating errors, bugs, crashes, or unexpected behavior.