Skip to content
Development
Command

/integration-test

Generate integration tests for a module, testing real interactions between components.

From plugin
rohitg00-claude-code-toolkit
2.5k199 skills138 agents199 commands
Install
$ npx -y skills add rohitg00/awesome-claude-code-toolkit --agent claude-code

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/integration-test

Context preview

What this command does when you run it.

Generate integration tests for a module, testing real interactions between components.

Command definition

integration-test.md

Generate integration tests for a module, testing real interactions between components.

Steps

1. Identify the target module or file from the argument or current context. 2. Analyze imports and dependencies to determine what external systems are involved (database, API, filesystem, message queue). 3. Detect the test framework in use (Jest, Vitest, pytest, Go testing, etc.) from project config. 4. For each public function or endpoint in the module:

  • Write a test that exercises the real integration path.
  • Set up required test fixtures (seed data, mock servers, temp files).
  • Test the happy path with realistic input data.
  • Test at least one error/failure scenario per integration point.
  • Add proper teardown to clean up test state.

5. Group tests logically using `describe`/`context` blocks. 6. Add setup and teardown hooks (`beforeAll`/`afterAll`) for shared resources. 7. Run the generated tests to verify they pass.

Format

Generated: <N> integration tests in <file>

Tests:
  - <TestName>: <what it verifies>
  - <TestName>: <what it verifies>

Coverage: <modules/functions covered>

Rules

  • Integration tests must use real dependencies where possible; mock only external services.
  • Each test must be independent and not rely on execution order.
  • Use realistic test data, not trivial values like "test" or "foo".
  • Include timeout configuration for async operations.
  • Name test files with `.integration.test` or `_integration_test` suffix.
Read more
Ships withrohitg00-claude-code-toolkit

The most comprehensive toolkit for Claude Code -- 135 agents, 35 curated skills (+400,000 via SkillKit), 42 commands, 176+ plugins, 20 hooks, 15 rules, 7 templates, 15 MCP configs, 26 companion apps, 53 ecosystem entries, and more.

Get the whole plugin