integration-testing

Validate integration boundaries using real PostgreSQL databases and migrations.

Updated Apr 9, 2026

Search Tags:#postgresql #migrations #integration-testing #test-automation #test-setup #real-database

Ready to run

npx skills add https://github.com/SergeuMatyasov/dotnet-shared-skills --skill integration-testing-sergeumatyasov

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: integration-testing
Source: https://github.com/SergeuMatyasov/dotnet-shared-skills/tree/main/integration-testing
Command: npx skills add https://github.com/SergeuMatyasov/dotnet-shared-skills --skill integration-testing-sergeumatyasov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides guidelines and best practices for writing integration tests that exercise real databases and infrastructure, ensuring proper isolation, migrations, reset state and end-to-end verification.

Core Features & Use Cases

Guidelines for separating integration tests into dedicated projects with clear boundaries
Best practices for using real PostgreSQL, migrations, and deterministic database resets
Clear criteria to ensure tests cover end-to-end scenarios without leaking state between tests
Practical examples of structuring tests to verify wiring, SQL, and provider-specific behaviors

Quick Start

Set up a dedicated integration-test project and run the tests against a real database to validate the integration boundary.

Frequently Asked Questions about integration-testing

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

FAQPage Schema

How do I set up integration testing with a real PostgreSQL database?▼

Achieve isolated integration testing by using real databases with deterministic resets and dedicated test projects. This approach enforces isolated environments, preventing state leakage between test runs.

Why use real databases for integration tests instead of mocks?▼

Validate integration boundaries by running tests against real databases and infrastructure. This verifies migrations, wiring, and end-to-end behavior across test environments and CI pipelines.

How do I ensure deterministic database resets between integration test runs?▼

Ensure deterministic database resets by applying migrations to a real PostgreSQL instance within an isolated environment. This approach enforces a clean, reset state for every test execution.

Can I run integration tests against real databases in CI environments?▼

Yes, you can run integration tests against real databases in CI. Use a dedicated integration-test project to validate migrations, wiring, and end-to-end behavior across test environments.

What is the best way to structure integration tests to prevent state leaking?▼

Structure integration tests by separating them into a dedicated project with clear boundaries. Use real PostgreSQL, migrations, and deterministic database resets to ensure tests cover end-to-end scenarios without leaking state.