planning-oracle-to-postgres-migration-integration-testing by github/awesome-copilot
npx skills add https://github.com/github/awesome-copilot --skill planning-oracle-to-postgres-migration-integration-testing分析单个目标项目,识别需要进行集成测试的数据访问构件,然后生成一份结构化、可操作的测试计划。
进度:
- [ ] 步骤 1:识别数据访问构件
- [ ] 步骤 2:划分测试优先级
- [ ] 步骤 3:编写测试计划
步骤 1:识别数据访问构件
仅限目标项目范围。查找直接与数据库交互的类和方法——存储库、DAO、存储过程调用者、执行 CRUD 操作的服务层。
步骤 2:划分测试优先级
根据迁移风险对构件进行排序。优先处理使用 Oracle 特定功能(refcursors、TO_CHAR、隐式类型转换、NO_DATA_FOUND)的方法,而非简单的 CRUD 操作。
步骤 3:编写测试计划
编写一份 Markdown 计划,涵盖:
将计划写入:.github/oracle-to-postgres-migration/Reports/{TARGET_PROJECT} Integration Testing Plan.md
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
MyApp.Postgres),因此每个实例仅针对一个数据库。每周安装次数
449
代码仓库
GitHub 星标数
26.7K
首次出现
13 天前
安全审计
安装于
gemini-cli397
codex396
opencode386
cursor383
github-copilot380
kimi-cli379
Analyze a single target project to identify data access artifacts that require integration testing, then produce a structured, actionable testing plan.
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:
Write the plan to: .github/oracle-to-postgres-migration/Reports/{TARGET_PROJECT} Integration Testing Plan.md
MyApp.Postgres), so each instance targets one database.Weekly Installs
449
Repository
GitHub Stars
26.7K
First Seen
13 days ago
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
gemini-cli397
codex396
opencode386
cursor383
github-copilot380
kimi-cli379
Google Slides 演示文稿创建与共享自动化教程 - 使用 Google Workspace CLI
6,500 周安装