---
id: sm3-planning-oracle-to-postgres-migration-integration-testing
name: "planning-oracle-to-postgres-migration-integration-testing"
url: https://skills.yangsir.net/skill/sm3-planning-oracle-to-postgres-migration-integration-testing
author: github
domain: testing
tags: ["integration-test-planning", "database-migration-testing", "oracle-to-postgresql", "test-strategy"]
install_count: 1800
rating: 4.30 (20 reviews)
github: https://github.com/github/awesome-copilot
---

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

> 规划Oracle到PostgreSQL数据库迁移的集成测试，确保迁移后系统功能和数据完整性。

**Stats**: 1,800 installs · 4.3/5 (20 reviews)

## Before / After 对比

### Oracle到PostgreSQL迁移集成测试规划

## Readme

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

# 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

## 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.

Weekly Installs236Repository[github/awesome-copilot](https://github.com/github/awesome-copilot)GitHub Stars25.7KFirst Seen7 days agoSecurity Audits[Gen Agent Trust HubPass](/github/awesome-copilot/planning-oracle-to-postgres-migration-integration-testing/security/agent-trust-hub)[SocketPass](/github/awesome-copilot/planning-oracle-to-postgres-migration-integration-testing/security/socket)[SnykPass](/github/awesome-copilot/planning-oracle-to-postgres-migration-integration-testing/security/snyk)Installed ongemini-cli204codex203opencode196cursor195kimi-cli193github-copilot193

---
*Source: https://skills.yangsir.net/skill/sm3-planning-oracle-to-postgres-migration-integration-testing*
*Markdown mirror: https://skills.yangsir.net/api/skill/sm3-planning-oracle-to-postgres-migration-integration-testing/markdown*