integration-test-generator

To generate integration tests for real database and API interactions, use this Skill after implementation is complete and unit tests pass. It creates end-to-end tests that validate actual dependencies, including read-after-write behavior and transaction rollbacks, ensuring components work together correctly.

You need end-to-end tests when unit tests mock dependencies and fail to validate real interactions across boundaries. Integration tests verify orchestration, deployment bugs, and actual database, API, and message queue interactions, catching contract failures that unit tests miss before reaching production.

To write integration tests runnable in CI/CD pipelines, this Skill ensures tests are idempotent and clean up after themselves. It provides guidance to configure real test databases, test servers, and message queue instances, tearing them down cleanly to maintain pipeline stability.

Yes, you can use existing testing frameworks like Jest, Vitest, node:test, or Bun for integration testing. This Skill uses the same testing framework as your unit tests and follows project naming conventions for integration and end-to-end test files.

The best way to set up and tear down test databases for integration tests is using environment setup guidance. This Skill provides repeatable processes to configure real test databases, test servers, and message queue instances, ensuring clean teardowns after verifying real system interactions.

Mocked unit tests fail to catch integration failures because they mock dependencies and do not validate real interactions across system boundaries. Integration tests exercise actual databases, APIs, and message queues to verify error propagation and orchestration, catching contract bugs early.