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.
Profile →npx skills add github/awesome-copilot --skill planning-oracle-to-postgres-migration-integration-testing --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
- Workflow
- Output
- Key Constraints
What does the planning-oracle-to-postgres-migration-integration-testing skill do?
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.
How do I install it?
Run `npx skills add github/awesome-copilot --skill planning-oracle-to-postgres-migration-integration-testing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.