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

github/awesome-copilot

Plan integration tests for Oracle-to-PostgreSQL .NET migrations by analyzing data access artifacts.

What is planning-oracle-to-postgres-migration-integration-testing?

This skill analyzes a single .NET project to identify repositories, DAOs, and service layers that interact with databases, then generates a structured integration testing plan for Oracle-to-PostgreSQL migrations. Use it when preparing migration validation, determining test coverage for data access methods, or planning integration tests for migrated projects.

Identifies data access artifacts (repositories, DAOs, stored procedure callers, service layers) in a target project
Classifies testing priorities by migration risk, prioritizing Oracle-specific features like refcursors and implicit type coercion
Generates a markdown testing plan with testable artifacts, recommended test cases, and seed data requirements
Documents Oracle-to-PostgreSQL behavioral differences to validate, including text parameters, datetime/timezone handling, and timestamp precision
Maps coverage to ensure every database touchpoint has at least one test case or justified set of cases for high-risk methods

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

npx skills add https://github.com/github/awesome-copilot --skill planning-oracle-to-postgres-migration-integration-testing

Claude Code

Cursor

Windsurf

Cline

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

1.Provide the target .NET project path or repository to analyze
2.Review the identified data access artifacts (repositories, DAOs, service layers) for accuracy
3.Examine the classified testing priorities based on Oracle-specific features and migration risk
4.Review the generated testing plan in `.github/oracle-to-postgres-migration/Reports/{TARGET_PROJECT} Integration Testing Plan.md`
5.Use the recommended test cases, seed data requirements, and behavioral difference validations to implement integration tests

Use cases

Good for

Planning integration test coverage when migrating a .NET application from Oracle to PostgreSQL
Identifying which data access methods in a project require migration validation tests
Preparing a structured testing strategy before executing an Oracle-to-PostgreSQL database migration
Documenting expected behavioral differences between Oracle and PostgreSQL for a specific project's data layer
Creating seed data and test case specifications for migrated repository and DAO classes

Who it's for

Database migration engineers planning Oracle-to-PostgreSQL transitions
QA engineers designing integration test suites for migrated .NET applications
.NET developers validating data access layer compatibility after database migration
Technical leads preparing migration validation strategies

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

What types of database interactions does this skill identify?

It identifies repositories, DAOs, stored procedure callers, and service layers that perform CRUD operations or directly interact with the database. Business logic without database touches is excluded.

How are testing priorities determined?

Artifacts are ranked by migration risk, prioritizing methods using Oracle-specific features (refcursors, TO_CHAR, implicit type coercion, NO_DATA_FOUND) over simple CRUD operations.

What behavioral differences does the plan cover?

The plan includes text parameter handling (empty strings vs. NULL), datetime/timezone assertions, round-trip behavior, timestamp precision (with/without timezone), and other Oracle-to-PostgreSQL compatibility issues.

Can this skill analyze multiple projects at once?

No, it is scoped to a single target project only. Run it separately for each project requiring migration testing.

Where is the testing plan output?

The plan is written to `.github/oracle-to-postgres-migration/Reports/{TARGET_PROJECT} Integration Testing Plan.md` in markdown format.

Full instructions (SKILL.md)

Source of truth, from github/awesome-copilot.

name: planning-oracle-to-postgres-migration-integration-testing description: 'Creates an integration testing plan for .NET data access artifacts during Oracle-to-PostgreSQL database migrations. Analyzes a single project to identify repositories, DAOs, and service layers that interact with the database, then produces a structured testing plan. Use when planning integration test coverage for a migrated project, identifying which data access methods need tests, or preparing for Oracle-to-PostgreSQL migration validation.'

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

Write a markdown plan covering:

List of testable artifacts with method signatures
Recommended test cases per artifact
Seed data requirements
Known Oracle→PostgreSQL behavioral differences to validate
Coverage mapping that ensures every database touchpoint has at least one test case (or a justified set of cases for high-risk methods)

When defining recommended test cases, explicitly include:

Text parameter behavior for both empty string and NULL/missing values.
Datetime/timezone assertions, including round-trip and comparison behavior.
Cases where destination columns use timestamp without time zone or timestamp(0), with explicit timezone-application expectations.

Output

Write the plan to: .github/oracle-to-postgres-migration/Reports/{TARGET_PROJECT} Integration Testing Plan.md

Key Constraints

Single project scope — only plan tests for artifacts within the target project.
Database interactions only — skip business logic that does not touch the database.
Oracle is the golden source — tests should capture Oracle's expected behavior for comparison against PostgreSQL.
No multi-connection harnessing — migrated applications are copied and renamed (e.g., MyApp.Postgres), so each instance targets one database.