Creating Oracle To Postgres Migration Integration Tests

This walks you through creating xUnit integration tests for .NET data access code during an Oracle to Postgres migration. It generates tests that run against both databases to prove behavioral consistency, using deterministic seed data and database-agnostic assertions. The workflow is prescriptive: discover your test project conventions, identify repositories and DAOs to test, create seed files, write test cases that inherit from your base class for automatic transaction rollback, then review every assertion for determinism. Oracle is treated as the source of truth. The main value is keeping test logic portable so the same tests validate both pre-migration Oracle behavior and post-migration Postgres behavior without rewriting assertions around platform-specific error messages or syntax quirks.

skills.sh installs: 1.8K
GitHub stars: 41K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add github/awesome-copilot --skill creating-oracle-to-postgres-migration-integration-tests --agent claude-code

Installs into .claude/skills of the current project.

Files

Creating Integration Tests for Oracle-to-PostgreSQL Migration

Generates integration test cases for data access artifacts in a single target project. Tests target Oracle and capture its behavior as the authoritative baseline. They are written to be logically portable — so they can survive Phase 6 migration without rewriting — but they do not run against PostgreSQL at this stage.

Prerequisites

The test project must already exist and compile (scaffolded separately).
Read the existing base test class and seed manager conventions before writing tests.

Workflow

Test Creation:
- [ ] Step 1: Discover the test project conventions
- [ ] Step 2: Identify testable data access artifacts
- [ ] Step 3: Create seed data
- [ ] Step 4: Write test cases
- [ ] Step 5: Review determinism

Step 1: Discover the test project conventions

Read the base test class, seed manager, and project file to understand inheritance patterns, transaction management, and seed file conventions.

Step 2: Identify testable data access artifacts

SKILL.md on GitHub