Index of every page on this site: llms.txt
All skills
github avatar

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

@f10fdb8 official
by githubgithub/awesome-copilot41k stars
5,399
Run it yourself

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.

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈114 tokens for metadata: the name and description. ≈958 when used: this file.

Description uses 5.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈457 characters, or 5.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

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.
  • 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.
  • 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.
  • For text parameters, include both empty-string and NULL/missing input coverage where applicable.
  • For datetime behavior, include assertions that validate the value written and read back matches — use the Oracle column's precision (e.g., seconds-only for a date/time column with no fractional seconds) rather than assuming any particular database type syntax.

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

  • Phase 3 only — these tests target Oracle. Do not invoke this skill during Phase 6 or against a PostgreSQL-targeting project.
  • Oracle is the golden source — tests capture Oracle's expected behavior.
  • Assertion portability — avoid platform-specific error messages or syntax in assertions so that when the test project is migrated to PostgreSQL in Phase 6, assertions require no changes.
  • Seed only against Oracle — the test project will be migrated to PostgreSQL in Phase 6; seed data and infrastructure stay Oracle-targeted until then.
  • Scoped to one project — do not create tests for artifacts outside the target project.
  • Preserve existing data — never rewrite or wipe pre-existing business or lookup rows.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides instructions for an AI agent to generate integration tests for .NET projects during a migration phase. It emphasizes preserving existing data and using safe testing patterns like transactions and deterministic assertions. No malicious behavior or security risks were identified.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer8mo

    1/1 file flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at f10fdb8. 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
  • Testing
  • oracle
  • postgres
  • migration
  • xunit
  • integration-tests
  • dotnet
  • data-access
  • sql

README badge

README badge for github/awesome-copilot/creating-oracle-to-postgres-migration-integration-tests

Generates integration test cases for .NET data access artifacts during Oracle-to-PostgreSQL migrations, using deterministic seed data and xUnit to validate behavior consistency across both databases. Targets projects with existing test infrastructure and focuses on repositories, DAOs, and query builders that need cross-database validation.

Generated from the current SKILL.md.

Does this skill generate tests for both Oracle and PostgreSQL?
Tests are written once against Oracle (the golden source) and designed to run against both databases. The skill generates DB-agnostic assertions so the same test cases validate behavior consistency when the project migrates to PostgreSQL.
What kind of data access code can these tests cover?
Repositories, DAOs, stored procedure callers, and query builders in a single target .NET project. The skill does not generate tests for artifacts outside the scoped project.
Do the generated tests modify the database permanently?
No. Tests run in transactions that roll back automatically, and seed data is not committed. The skill enforces that existing database data remains intact.
What test framework does this skill use?
xUnit for .NET. Tests inherit from a base test class that handles transaction management and rollback.
Do I need an existing test project to use this skill?
Yes. The test project must already exist and compile. The skill discovers its base test class conventions and seed manager patterns before generating new test cases.

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