skilld
All skills
github avatar

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

@0b950f9 official
by githubgithub/awesome-copilot40k stars
5,040

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.

Ask your Agent

Use this Skill: https://skilld.dev/gh/github/awesome-copilot/planning-oracle-to-postgres-migration-integration-testing

This session only. Nothing lands on disk.

SKILL.md

≈126 tokens always: the name and description. ≈538 when used: this file.

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.

Source: SKILL.md on GitHub

Third-party checks

No alerts16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    The skill identifies data access artifacts in source code projects to generate a migration testing plan. It operates by reading local project files and writing a report to the project's repository. A low-risk indirect prompt injection surface exists as the skill processes untrusted source code without specific sanitization or boundary markers.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer6mo

    1 file scanned · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at 0b950f9. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 3 months ago

Topics

  • Database
  • oracle
  • postgres
  • migration
  • integration-testing
  • dotnet
  • dao
  • test-planning

README badge

README badge for github/awesome-copilot/planning-oracle-to-postgres-migration-integration-testing

What it does

Analyzes a .NET project to identify data access artifacts (repositories, DAOs, service layers) that interact with Oracle, then produces a structured integration testing plan for validating the migration to PostgreSQL. Targets Oracle-specific features like refcursors and type coercion that require explicit test coverage during database migration.

Generated from the current SKILL.md.

Frequently asked

Does this skill help plan tests for multi-project migrations?
No. The skill is scoped to a single target project only. It identifies data access artifacts within that project and produces a testing plan for those artifacts.
What Oracle-specific features does the skill flag for testing?
The skill prioritizes methods using Oracle-specific constructs like refcursors, TO_CHAR, implicit type coercion, and NO_DATA_FOUND exceptions, since these have different behavior in PostgreSQL.
Does this skill generate the actual integration tests?
No. The skill produces a structured testing plan document that lists testable artifacts, recommended test cases, seed data requirements, and known behavioral differences. You write the tests separately.
What kinds of data access code does this skill analyze?
It targets repositories, DAOs, stored procedure callers, and service layer methods that perform direct database CRUD operations. Business logic that does not touch the database is out of scope.
What is the output format?
A markdown file written to `.github/oracle-to-postgres-migration/Reports/{TARGET_PROJECT} Integration Testing Plan.md`, listing artifacts with method signatures, test cases, seed data needs, and Oracle-to-PostgreSQL behavioral differences to validate.

Generated from the current SKILL.md. These answers refresh after source changes.