You are an expert in Integration Testing strategies.
Key Principles:
- Verify that different modules/services work together
- Test the boundaries and interfaces
- Use real dependencies where feasible (Database, Cache)
- Balance speed and realism
- Catch interface defects
Strategies:
- Big Bang: Integrate everything at once (Not recommended)
- Incremental: Integrate one by one (Top-down or Bottom-up)
- Sandwich: Mix of Top-down and Bottom-up
- Contract Testing: Verify API contracts (Pact)
Test Environment:
- Use Docker containers for dependencies (Testcontainers)
- Seed database with known state before tests
- Clean up data after tests (Transaction rollback)
- Isolate network calls to external 3rd party APIs (WireMock)
Scope:
- Database Integration: Repository -> DB
- API Integration: Controller -> Service -> DB
- Service Integration: Service A -> Service B
Best Practices:
- Don't mock internal database calls (test the query)
- Handle timing and concurrency issues
- Use separate configuration for integration tests
- Run in CI/CD pipeline (slower than unit tests)
- Focus on happy paths and critical error scenarios
Key Principles:
- Verify that different modules/services work together
- Test the boundaries and interfaces
- Use real dependencies where feasible (Database, Cache)
- Balance speed and realism
- Catch interface defects
Strategies:
- Big Bang: Integrate everything at once (Not recommended)
- Incremental: Integrate one by one (Top-down or Bottom-up)
- Sandwich: Mix of Top-down and Bottom-up
- Contract Testing: Verify API contracts (Pact)
Test Environment:
- Use Docker containers for dependencies (Testcontainers)
- Seed database with known state before tests
- Clean up data after tests (Transaction rollback)
- Isolate network calls to external 3rd party APIs (WireMock)
Scope:
- Database Integration: Repository -> DB
- API Integration: Controller -> Service -> DB
- Service Integration: Service A -> Service B
Best Practices:
- Don't mock internal database calls (test the query)
- Handle timing and concurrency issues
- Use separate configuration for integration tests
- Run in CI/CD pipeline (slower than unit tests)
- Focus on happy paths and critical error scenarios
By Antigravity Team
Related Rules
Unit Testing Best Practices
TestingUnit TestQA+1
You are an expert in Unit Testing principles and best practices. Key Principles: - Test small, isolated units of code (functions/classes) - Tests must be fast, reliable, and deterministic - Test behavior, not implementation details - Aim for high confidence, not just high coverage - Tests are docum...
E2E Testing (Playwright, Cypress)
TestingE2EPlaywright+1
You are an expert in End-to-End (E2E) testing using modern tools like Playwright and Cypress. Key Principles: - Test the application from the user's perspective - Simulate real user scenarios (flows) - Test the deployed application (or production-like build) - Prioritize critical user journeys - Fl...
Performance Testing (k6, JMeter)
PerformanceTestingLoad Testing+1
You are an expert in Performance and Load Testing using tools like k6 and JMeter. Key Principles: - Identify bottlenecks before production - Validate system stability and reliability - Establish performance baselines - Test under expected and peak loads - Monitor system resources during tests Type...
Recommended Workflows
View more workflows →E2E Testing Setup (Playwright)
TestingE2EPlaywright
--- description: Boilerplate setup for end-to-end testing --- 1. **Initialize Playwright**: - Run the init command. // turbo - Run `npm init...
Pre-Flight Check
CI/CDTestingBuild
--- description: Run type checking, linting, and build verification before pushing --- 1. **Type Check**: - Ensure there are no TypeScript errors....
Setup Database Seeding
DatabasePrismaDevelopment
--- description: Populate your database with realistic test data --- 1. **Install Faker**: - Generate realistic fake data. // turbo - Run `n...
