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

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.

Files1

1 files · 1.0 KB

Select a file to preview

Overall Score

74/100

Grade

B

Good

Safety

88

Quality

72

Clarity

76

Completeness

65

Summary

A structured planning skill that guides agents through analyzing .NET projects to identify data access artifacts (repositories, DAOs, service layers) that require integration testing during Oracle-to-PostgreSQL migrations. The skill produces a markdown testing plan document that prioritizes test coverage by migration risk and captures Oracle-specific behavioral expectations.

Detected Capabilities

File read (codebase analysis)File write (markdown plan generation)Code pattern analysisData access layer classification

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

oracle to postgres migrationintegration test planningdata access layer migrationdao testing strategyrepository pattern testing

Use Cases

.NET project assessment for database migration readiness
integration test planning for Oracle-to-PostgreSQL data layer migration
Risk prioritization of data access methods based on Oracle-specific feature usage
Generating test case specifications for repository and DAO classes
Documenting behavioral differences between Oracle and PostgreSQL to validate in migration testing

Quality Notes

Skill is well-scoped to a single project with clear data access artifact boundaries
Clear workflow with 3-step progression (identify, classify, write)
Specific output path documented (.github/oracle-to-postgres-migration/Reports/)
Oracle behavior is correctly designated as the source of truth for test expectations
Constraints section explicitly prevents multi-database confusion and out-of-scope analysis
Database-only focus prevents inclusion of irrelevant business logic
Lacks examples of what 'Oracle-specific features' look like in actual code (e.g., code samples of refcursor or TO_CHAR usage)
No error handling guidance for edge cases (e.g., classes with mixed concerns, legacy code without clear patterns)
Plan structure is described at a high level but no markdown template or structure example provided
No guidance on how to measure test coverage completeness or validate the plan

Model: claude-haiku-4-5-20251001Analyzed: Jun 26, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

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