Labsco
github logo

creating-oracle-to-postgres-migration-integration-tests

✓ Official★ 36,200

by github · part of github/awesome-copilot

Creates integration test cases for .NET data access artifacts during Oracle-to-PostgreSQL database migrations. Generates DB-agnostic xUnit tests with…

🔥🔥🔥✓ VerifiedFreeAdvanced setup
#automation#database#git#maps
🧩 One of 7 skills in the github/awesome-copilot package — works on its own, and pairs well with its siblings.

Creates integration test cases for .NET data access artifacts during Oracle-to-PostgreSQL database migrations. Generates DB-agnostic xUnit tests with…

Inspect the full instructions your agent will receiveExpand

This is the exact playbook injected into your agent when the skill activates — shown here so you can audit it before installing. You don't need to read it to use the skill.

by github

Creates integration test cases for .NET data access artifacts during Oracle-to-PostgreSQL database migrations. Generates DB-agnostic xUnit tests with… npx skills add https://github.com/github/awesome-copilot --skill creating-oracle-to-postgres-migration-integration-tests Download ZIPGitHub36.2k

Creating Integration Tests for Oracle-to-PostgreSQL Migration

Generates integration test cases for data access artifacts in a single target project. Tests validate behavior consistency when running against Oracle or PostgreSQL.

Workflow

Copy & paste — that's it
Test Creation:
- [ ] Step 1: Discover the test project conventions
- [ ] Step 2: Identify testable data access artifacts
- [ ] Step 3: Create seed data
- [ ] Step 4: Write test cases
- [ ] Step 5: Review determinism

Step 1: Discover the test project conventions

Read the base test class, seed manager, and project file to understand inheritance patterns, transaction management, and seed file conventions.

Step 2: Identify testable data access artifacts

Scope to the target project only. List data access methods that interact with the database — repositories, DAOs, stored procedure callers, query builders.

Step 3: Create seed data

  • Follow seed file location and naming conventions from the existing project.

  • Reuse existing seed files when possible.

  • Avoid TRUNCATE TABLE — keep existing database data intact.

  • Do not commit seed data; tests run in transactions that roll back.

  • Ensure seed data does not conflict with other tests.

  • Load and verify seed data before assertions depend on it.

Step 4: Write test cases

  • Inherit from the base test class to get automatic transaction create/rollback.

  • Assert logical outputs (rows, columns, counts, error types), not platform-specific messages.

  • Assert specific expected values — never assert that a value is merely non-null or non-empty when a concrete value is available from seed data.

  • Avoid testing code paths that do not exist or asserting behavior that cannot occur.

  • Avoid redundant assertions across tests targeting the same method.

Step 5: Review determinism

Re-examine every assertion against non-null values. Confirm each is deterministic against the seeded data. Fix any assertion that depends on database state outside the test's control.

Key Constraints

  • Oracle is the golden source — tests capture Oracle's expected behavior.

  • DB-agnostic assertions — no platform-specific error messages or syntax in assertions.

  • Seed only against Oracle — test project will be migrated to PostgreSQL later.

  • Scoped to one project — do not create tests for artifacts outside the target project.