Planning Oracle To Postgres Migration Integration Testing
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.
Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.
What it does
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
When to use it
planning integration test coverage for a migrated project, identifying which data access methods need tests, or preparing for Oracle-to-PostgreSQL migration validation
How agents load it
Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Planning Integration Testing for Oracle-to-PostgreSQL Migration; Workflow; Output; Key Constraints. It includes spec-recommended sections: step-by-step instructions.
File analysis
File analysis: instruction-only skill (SKILL.md). The agent loads the full body when activated.
Planning Integration Testing for Oracle-to-PostgreSQL MigrationWorkflowOutputKey Constraints
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.
DiscoverThe client exposes names and descriptions to the agent.
ActivateYour request or the task context selects the skill and loads its instructions.
Load resourcesReferenced scripts, documentation and assets are used when needed.
Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.
Ask your Agent to install
Copy these instructions to a compatible agent and confirm the target directory matches your client.
Install the agent skill "planning-oracle-to-postgres-migration-integration-testing" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-5a43d29db624a6c2-Planning-Oracle-To-Postgres-Migration-In.html
Save it as .cursor/skills/planning-oracle-to-postgres-migration-integration-testing/SKILL.md or .claude/skills/planning-oracle-to-postgres-migration-integration-testing/SKILL.md and keep the frontmatter name and description exactly as-is.
The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.
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.