scaffolding-oracle-to-postgres-migration-test-project
Scaffolds an xUnit integration test project for validating Oracle-to-PostgreSQL database migration behavior in .NET solutions. Creates the test project, transaction-rollback base class, and seed data manager. Use when setting up test infrastructure before writing migration integration tests, or when a test project is needed for Oracle-to-PostgreSQL validation.
Best use case
scaffolding-oracle-to-postgres-migration-test-project is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Scaffolds an xUnit integration test project for validating Oracle-to-PostgreSQL database migration behavior in .NET solutions. Creates the test project, transaction-rollback base class, and seed data manager. Use when setting up test infrastructure before writing migration integration tests, or when a test project is needed for Oracle-to-PostgreSQL validation.
Teams using scaffolding-oracle-to-postgres-migration-test-project should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/scaffolding-oracle-to-postgres-migration-test-project/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How scaffolding-oracle-to-postgres-migration-test-project Compares
| Feature / Agent | scaffolding-oracle-to-postgres-migration-test-project | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Scaffolds an xUnit integration test project for validating Oracle-to-PostgreSQL database migration behavior in .NET solutions. Creates the test project, transaction-rollback base class, and seed data manager. Use when setting up test infrastructure before writing migration integration tests, or when a test project is needed for Oracle-to-PostgreSQL validation.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
AI Agents for Startups
Explore AI agent skills for startup validation, product research, growth experiments, documentation, and fast execution with small teams.
AI Agent for Product Research
Browse AI agent skills for product research, competitive analysis, customer discovery, and structured product decision support.
SKILL.md Source
# Scaffolding an Integration Test Project for Oracle-to-PostgreSQL Migration Creates a compilable, empty xUnit test project with transaction management and seed data infrastructure for a single target project. Run once per project before writing tests. ## Workflow ``` Progress: - [ ] Step 1: Inspect the target project - [ ] Step 2: Create the xUnit test project - [ ] Step 3: Implement transaction-rollback base class - [ ] Step 4: Implement seed data manager - [ ] Step 5: Verify the project compiles ``` **Step 1: Inspect the target project** Read the target project's `.csproj` to determine the .NET version and existing package references. Match these versions exactly — do not upgrade. **Step 2: Create the xUnit test project** - Target the same .NET version as the application under test. - Add NuGet packages for Oracle database connectivity and xUnit. - Add a project reference to the target project only — no other application projects. - Add an `appsettings.json` configured for Oracle database connectivity. **Step 3: Implement transaction-rollback base class** - Create a base test class that opens a transaction before each test and rolls it back after. - Catch and handle all exceptions to guarantee rollback. - Make the pattern inheritable by all downstream test classes. **Step 4: Implement seed data manager** - Create a global seed manager for loading test data within the transaction scope. - Do not commit seed data — transactions roll back after each test. - Do not use `TRUNCATE TABLE` — preserve existing database data. - Reuse existing seed files if available. - Establish a naming convention for seed file location that downstream test creation will follow. **Step 5: Verify the project compiles** Build the test project and confirm it compiles with zero errors before finishing. ## Key Constraints - Oracle is the golden behavior source — scaffold for Oracle first. - Keep to existing .NET and C# versions; do not introduce newer language or runtime features. - Output is an empty test project with infrastructure only — no test cases.
Related Skills
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
unit-test-vue-pinia
Write and review unit tests for Vue 3 + TypeScript + Vitest + Pinia codebases. Use when creating or updating tests for components, composables, and stores; mocking Pinia with createTestingPinia; applying Vue Test Utils patterns; and enforcing black-box assertions over implementation details.
spring-boot-testing
Expert Spring Boot 4 testing specialist that selects the best Spring Boot testing techniques for your situation with Junit 6 and AssertJ.
scoutqa-test
This skill should be used when the user asks to "test this website", "run exploratory testing", "check for accessibility issues", "verify the login flow works", "find bugs on this page", or requests automated QA testing. Triggers on web application testing scenarios including smoke tests, accessibility audits, e-commerce flows, and user flow validation using ScoutQA CLI. Use this skill proactively after implementing web application features to verify they work correctly.
pytest-coverage
Run pytest tests with coverage, discover lines missing coverage, and increase coverage to 100%.
project-workflow-analysis-blueprint-generator
Comprehensive technology-agnostic prompt generator for documenting end-to-end application workflows. Automatically detects project architecture patterns, technology stacks, and data flow patterns to generate detailed implementation blueprints covering entry points, service layers, data access, error handling, and testing approaches across multiple technologies including .NET, Java/Spring, React, and microservices architectures.
issue-fields-migration
Bulk-migrate metadata to GitHub issue fields from two sources: repo labels (e.g. priority labels to a Priority field) and Project V2 fields. Use when users say "migrate my labels to issue fields", "migrate project fields to issue fields", "convert labels to issue fields", "copy project field values to issue fields", or ask about adopting issue fields. Issue fields are org-level typed metadata (single select, text, number, date) that replace label-based workarounds with structured, searchable, cross-repo fields.
create-spring-boot-kotlin-project
Create Spring Boot Kotlin Project Skeleton
breakdown-test
Test Planning and Quality Assurance prompt that generates comprehensive test strategies, task breakdowns, and quality validation plans for GitHub projects.
winui3-migration-guide
UWP-to-WinUI 3 migration reference. Maps legacy UWP APIs to correct Windows App SDK equivalents with before/after code snippets. Covers namespace changes, threading (CoreDispatcher to DispatcherQueue), windowing (CoreWindow to AppWindow), dialogs, pickers, sharing, printing, background tasks, and the most common Copilot code generation mistakes.
polyglot-test-agent
Generates comprehensive, workable unit tests for any programming language using a multi-agent pipeline. Use when asked to generate tests, write unit tests, improve test coverage, add test coverage, create test files, or test a codebase. Supports C#, TypeScript, JavaScript, Python, Go, Rust, Java, and more. Orchestrates research, planning, and implementation phases to produce tests that compile, pass, and follow project conventions.
reviewing-oracle-to-postgres-migration
Identifies Oracle-to-PostgreSQL migration risks by cross-referencing code against known behavioral differences (empty strings, refcursors, type coercion, sorting, timestamps, concurrent transactions, etc.). Use when planning a database migration, reviewing migration artifacts, or validating that integration tests cover Oracle/PostgreSQL differences.