creating-oracle-to-postgres-migration-integration-tests

Creates Oracle-targeted integration tests for .NET data access artifacts during migration Phase 3.

38.5k|4.9k|Updated Jun 11, 2025
One-click install
npx skills add https://github.com/github/awesome-copilot --skill creating-oracle-to-postgres-migration-integration-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creating-oracle-to-postgres-migration-integration-tests
Source: https://github.com/github/awesome-copilot/tree/main/skills/creating-oracle-to-postgres-migration-integration-tests
Command: npx skills add https://github.com/github/awesome-copilot --skill creating-oracle-to-postgres-migration-integration-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When migrating a .NET application from Oracle to PostgreSQL, teams need a reliable behavioral baseline before touching any PostgreSQL code. This Skill generates integration tests that capture Oracle's actual behavior as the authoritative reference, so the later migration can be validated against concrete expected results rather than guesswork.

Core Features & Use Cases

  • Convention-aware test generation: Reads the existing base test class, seed manager, and project file to match inheritance patterns, transaction rollback handling, and seed file conventions.
  • Deterministic seed data creation: Adds minimal, collision-safe seed records without truncating tables or disturbing existing business and lookup rows.
  • Portable assertion design: Writes assertions against logical outputs (rows, columns, counts, error types) rather than platform-specific messages, so tests survive the Phase 6 migration to PostgreSQL unchanged.
  • Use Case: During Phase 3 of an Oracle-to-PostgreSQL migration, point the Skill at a single target project to generate integration tests covering every database-touching repository, DAO, and stored procedure caller before any PostgreSQL work begins.

Quick Start

Ask the agent to create Oracle integration tests for the data access layer of a specific target project following the existing base test class and seed conventions.

Frequently Asked Questions about creating-oracle-to-postgres-migration-integration-tests

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

FAQPage Schema
How do I create integration tests for an Oracle to PostgreSQL migration?

Generate integration tests against Oracle first to capture its behavior as the authoritative baseline, then port the test project to PostgreSQL in a later phase. This Skill handles the Oracle-side test creation during Phase 3, following your existing base test class and seed conventions.

How to write database integration tests that survive a database migration?

Assert logical outputs such as rows, columns, counts, and error types instead of platform-specific error messages or syntax. Use seed data loaded inside transactions that roll back, and assert concrete expected values from seed data rather than non-null checks.

When should I use this Skill in the migration process?

Use it only during Phase 3, before any PostgreSQL migration work has begun. Do not invoke it during Phase 6 or against a project that has already been migrated to PostgreSQL, since the tests must capture Oracle behavior as the golden source.

Can the tests modify existing database data during seeding?

No. Seed data must be minimal and collision-safe, never using TRUNCATE TABLE or rewriting existing business and lookup rows. Tests run inside transactions that roll back, so seed data is never committed to the database.

What are the limitations of Oracle-baseline integration tests?

They only run against Oracle and cannot validate PostgreSQL behavior directly. They are also scoped to a single target project and require an existing compilable test project with established base test class and seed manager conventions.