Creating Oracle To Postgres Migration Integration Tests

1---2name: creating-oracle-to-postgres-migration-integration-tests3description: 'Creates integration test cases for .NET data access artifacts during Oracle-to-PostgreSQL database migrations. Generates DB-agnostic xUnit tests with deterministic seed data that validate behavior consistency across both database systems. Use when creating integration tests for a migrated project, generating test coverage for data access layers, or writing Oracle-to-PostgreSQL migration validation tests.'4---5 6# Creating Integration Tests for Oracle-to-PostgreSQL Migration7 8Generates integration test cases for data access artifacts in a single target project. Tests validate behavior consistency when running against Oracle or PostgreSQL.9 10## Prerequisites11 12- The test project must already exist and compile (scaffolded separately).13- Read the existing base test class and seed manager conventions before writing tests.14 15## Workflow16 17```18Test Creation:19- [ ] Step 1: Discover the test project conventions20- [ ] Step 2: Identify testable data access artifacts21- [ ] Step 3: Create seed data22- [ ] Step 4: Write test cases23- [ ] Step 5: Review determinism24```25 26**Step 1: Discover the test project conventions**27 28Read the base test class, seed manager, and project file to understand inheritance patterns, transaction management, and seed file conventions.29 30**Step 2: Identify testable data access artifacts**31 32Scope to the target project only. List data access methods that interact with the database — repositories, DAOs, stored procedure callers, query builders.33 34**Step 3: Create seed data**35 36- Follow seed file location and naming conventions from the existing project.37- Reuse existing seed files when possible.38- Avoid `TRUNCATE TABLE` — keep existing database data intact.39- Do not commit seed data; tests run in transactions that roll back.40- Ensure seed data does not conflict with other tests.41- Load and verify seed data before assertions depend on it.42 43**Step 4: Write test cases**44 45- Inherit from the base test class to get automatic transaction create/rollback.46- Assert logical outputs (rows, columns, counts, error types), not platform-specific messages.47- 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.48- Avoid testing code paths that do not exist or asserting behavior that cannot occur.49- Avoid redundant assertions across tests targeting the same method.50 51**Step 5: Review determinism**52 53Re-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.54 55## Key Constraints56 57- **Oracle is the golden source** — tests capture Oracle's expected behavior.58- **DB-agnostic assertions** — no platform-specific error messages or syntax in assertions.59- **Seed only against Oracle** — test project will be migrated to PostgreSQL later.60- **Scoped to one project** — do not create tests for artifacts outside the target project.