Agent skill · data analytics · github
creating-oracle-to-postgres-migration-integration-tests
Creates integration test cases targeting Oracle for .NET data access artifacts. Tests capture Oracle expected behavior as the authoritative baseline; they are written once and later ported to PostgreSQL by migrating the test project in Phase 6. Use only during Phase 3, before any PostgreSQL migration work has begun. Do not invoke during Phase 6 or against a project that has already been migrated.
Why this skill is useful
Generates DB-agnostic xUnit tests with specific conventions for validating behavior consistency during Oracle-to-PostgreSQL migrations.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
Creating Integration Tests for Oracle-to-PostgreSQL Migration Generates integration test cases for data access artifacts in a single target project. Tests target Oracle and capture its behavior as the authoritative baseline. They are written to be logically portable — so they can survive Phase 6 migration without rewriting — but they do not run against PostgreSQL at this stage. Prerequisites The test project must already exist and compile (scaffolded separately). Read the existing base test class and seed manager conventions before writing tests. Workflow 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. Avoid TRUNCATE TABLE — keep existing database data intact. Assume existing business rows and lookup rows are already present; add only minimal, collision-safe seed records needed for the scenario. 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. Create or reuse a test LookupConstants class for stable lookup IDs/codes used across seed builders and assertions. Step 4: Write test cases Inherit from the base test class to get automatic transaction create/rollback. Ensure each database-touching method in scope has at least one integration test (or multiple tests for higher-risk behavior branches). Assert logical outputs (rows, columns, counts, error types), not platform-specific messages. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/creating-oracle-to-postgres-migration-integration-tests