planning-oracle-to-postgres-migration-integration-testing

Creates integration testing plans for .NET data access code during Oracle-to-PostgreSQL migrations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrating a .NET application from Oracle to PostgreSQL risks subtle behavioral differences in data access code, and teams often lack a structured way to decide which repositories, DAOs, and service methods need integration test coverage.

Core Features & Use Cases

  • Data Access Discovery: Scans a single target project to identify repositories, DAOs, stored procedure callers, and service layers that interact with the database.
  • Risk-Based Prioritization: Ranks artifacts by migration risk, prioritizing Oracle-specific features like refcursors, TO_CHAR, implicit type coercion, and NO_DATA_FOUND.
  • Structured Test Plan Output: Produces a markdown plan with testable artifacts, recommended test cases, seed data requirements, and Oracle-to-PostgreSQL behavioral differences covering empty string vs NULL handling and timestamp/timezone semantics.
  • Use Case: After migrating a .NET application's database layer to PostgreSQL, use this Skill to generate a complete integration testing plan ensuring every database touchpoint has at least one validating test case.

Quick Start

Analyze the target .NET project and generate an Oracle-to-PostgreSQL integration testing plan covering all data access methods.

Frequently Asked Questions about planning-oracle-to-postgres-migration-integration-testing

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

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

Identify all data access artifacts in the target project, rank them by migration risk based on Oracle-specific features, then write a plan listing test cases, seed data, and behavioral differences. This Skill automates that workflow and outputs a structured markdown plan.

What Oracle-specific features need testing when migrating to PostgreSQL?

Prioritize refcursors, TO_CHAR formatting, implicit type coercion, and NO_DATA_FOUND exception behavior, as these differ significantly in PostgreSQL. Simple CRUD operations carry lower migration risk and need less intensive coverage.

How should I test empty string versus NULL behavior in PostgreSQL?

Oracle treats empty strings as NULL while PostgreSQL distinguishes them, so test cases must explicitly cover both empty string and NULL or missing text parameters. The generated plan includes these cases for every relevant data access method.

Does this Skill analyze multiple projects at once?

No, it is scoped to a single target project only. It identifies database-interacting artifacts within that project and skips business logic that does not touch the database.

What timestamp issues occur in Oracle to PostgreSQL migration testing?

Columns using timestamp without time zone or timestamp(0) require explicit timezone-application expectations in tests. The plan includes datetime round-trip and comparison assertions to validate these behaviors against Oracle as the golden source.