Planning Oracle To Postgres Migration Integration Testing

This walks through a single .NET project and flags every repository, DAO, and service layer method that touches the database, then writes out a structured testing plan focused on Oracle to Postgres migration risks. It's scoped deliberately narrow: one project at a time, database interactions only, with priority given to Oracle-specific features like refcursors and type coercion that tend to break subtly when you switch engines. The output is a markdown file listing what needs tests, what seed data you'll need, and which behavioral differences to watch for. It's honest about the constraints: Oracle is your source of truth, and it assumes you're running side-by-side app instances rather than trying to test both databases through one codebase.

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 planning-oracle-to-postgres-migration-integration-testing --agent claude-code

Installs into .claude/skills of the current project.

Files

Planning Integration Testing for Oracle-to-PostgreSQL Migration

Analyze a single target project to identify data access artifacts that require integration testing, then produce a structured, actionable testing plan.

Workflow

Progress:
- [ ] Step 1: Identify data access artifacts
- [ ] Step 2: Classify testing priorities
- [ ] Step 3: Write the testing plan

Step 1: Identify data access artifacts

Scope to the target project only. Find classes and methods that interact directly with the database — repositories, DAOs, stored procedure callers, service layers performing CRUD operations.

Step 2: Classify testing priorities

Rank artifacts by migration risk. Prioritize methods that use Oracle-specific features (refcursors, TO_CHAR, implicit type coercion, NO_DATA_FOUND) over simple CRUD.

Step 3: Write the testing plan

SKILL.md on GitHub