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

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

github.com/githubTesting & quality40.5k1.8k installsUpdated 1d ago
Repository

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

A skill that analyzes one project’s database access code and produces an actionable integration-testing plan for Oracle-to-PostgreSQL migration. It ranks artifacts by migration risk and maps test cases to database touchpoints, including specified text and timestamp behaviors.

Key features

  1. 01Single-project database artifact inventory
  2. 02Migration-risk prioritization
  3. 03Test cases and seed data recommendations
  4. 04Oracle–PostgreSQL behavior checks
  5. 05Database-touchpoint coverage mapping

Use cases

  1. 01Plan migration tests for repositories and DAOs
  2. 02Prioritize testing for Oracle-specific database features
  3. 03Map integration tests across database access points

Install

Copy the command and run it in a terminal.

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

After installing, type/planning-oracle-to-postgres-migration-integration-testingin Claude Code to confirm it loaded.

Details

From the project README

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.

Comments

Markdown supported