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

Analyze a single target project to identify data access artifacts that require integration testing, then produce a structured, actionable 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: Write the plan to: .github/oracle-to-postgres-migration/Reports/{TARGET_PROJECT} Integration Testing Plan.md - List of testable artifacts with method signatures - Recommended test cases per artifact - Seed data requirements - Known Oracle→PostgreSQL behavioral differences to validate - 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.