Back to Details

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

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Planning Integration Testing for Oracle-to-PostgreSQL Migration

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

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
进度:
- [ ] 步骤1：识别数据访问组件
- [ ] 步骤2：划分测试优先级
- [ ] 步骤3：编写测试计划
步骤1：识别数据访问组件
仅局限于目标项目范围。查找直接与数据库交互的类和方法——仓储、DAO、存储过程调用程序、执行CRUD操作的服务层。
步骤2：划分测试优先级
根据迁移风险对组件进行排序。优先测试使用Oracle特定功能（如refcursors、
TO_CHAR
、隐式类型转换、
NO_DATA_FOUND
）的方法，而非简单的CRUD操作。
步骤3：编写测试计划
编写Markdown格式的计划，涵盖：
  • 带方法签名的可测试组件列表
  • 每个组件的推荐测试用例
  • 种子数据要求
  • 需要验证的Oracle→PostgreSQL已知行为差异

Output

输出

Write the plan to: 
.github/oracle-to-postgres-migration/Reports/{TARGET_PROJECT} Integration Testing Plan.md
将计划写入：
.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.
  • 单一项目范围 —— 仅为目标项目内的组件规划测试。
  • 仅关注数据库交互 —— 跳过不涉及数据库的业务逻辑。
  • 以Oracle为基准源 —— 测试应捕获Oracle的预期行为，以便与PostgreSQL进行对比。
  • 不支持多连接管理 —— 迁移后的应用会被复制并重命名（例如
    MyApp.Postgres
    ），因此每个实例仅指向一个数据库。