Agent skill · data analytics · github
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.
Why this skill is useful
Provides a structured testing plan specifically for Oracle-to-PostgreSQL migrations, detailing niche testing requirements and behaviors that the AI wouldn't reliably generate on its own.
What it needs
About 1k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
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 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, TOCHAR, implicit type coercion, NODATAFOUND) 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/{TARGETPROJECT} 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.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/planning-oracle-to-postgres-migration-integration-testing