api-integration-test

Run real HTTP requests against a live Docker API container to detect regressions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/apireaisecurity/apire-ai-security-platform --skill api-integration-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-integration-test
Source: https://github.com/apireaisecurity/apire-ai-security-platform/tree/main/apire-redteam-kit/.agent/skills/api-integration-test
Command: npx skills add https://github.com/apireaisecurity/apire-ai-security-platform --skill api-integration-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Integration testing for API stacks running in Docker containers to ensure end-to-end functionality across controller, service, and database.

Core Features & Use Cases

  • End-to-end API testing against a live container and verifying HTTP responses, database interactions, and cross-module flows.
  • Regressions detection across endpoints during CI and local development.

Quick Start

Run the integration tests against your running Docker container to verify API endpoints and data persistence.

Frequently Asked Questions about api-integration-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run end-to-end API tests against a live Docker container?

End-to-end API tests against a live Docker container are executed by sending real HTTP requests using supertest and jest to verify controller, service, and database interactions without mocks.

Why do my API regressions keep appearing after environment changes in CI?

API regressions after environment changes occur when tests rely on mocks. Running real HTTP integration tests against a live Docker container detects endpoint regressions and cross-service integration issues immediately in CI or local development.

Can I use supertest and jest for integration testing with a NestJS API?

Yes, supertest and jest provide the Node.js testing stack needed to exercise NestJS API endpoints directly. This integration testing approach validates cross-module flows and data persistence against a running Docker container.

What is the best way to validate API database interactions without mocks?

The best way to validate API database interactions without mocks is running end-to-end integration tests that send real HTTP requests to a live Docker API container, ensuring database persistence and controller reliability across migrations.

When do I need integration testing instead of unit testing for API endpoints?

Integration testing is needed when validating cross-service integration issues, endpoint regressions, and database interactions across migrations or environment changes, ensuring full end-to-end reliability that unit tests with mocks cannot verify.

Do I need Docker to run integration tests with supertest and jest?

Docker is required to host the live API container for integration testing with supertest and jest. The tests send real HTTP requests directly to the running container to validate end-to-end functionality and data persistence.