What is migration-validator?

A skill that validates functional equivalence after migration through side-by-side comparison and behavioral verification.

What outputs does it produce?

An Output Schema containing fields like validationId, timestamp, source and target environments, results, comparisons, and acceptance status.

Which tools integrate and how?

Diffy for response comparison, contract testing via CLI, Cypress, Playwright, and custom validators integrate to support migration validation and execution workflows.

migration-validator

npx machina-cli add skill a5c-ai/babysitter/migration-validator --openclaw

Files (1)

SKILL.md

2.5 KB

Migration Validator Skill

Validates functional equivalence between source and target systems after migration through comprehensive comparison and behavioral verification.

Purpose

Enable migration validation for:

Side-by-side comparison
Output diffing
Behavioral verification
Data consistency checking
Acceptance criteria verification

Capabilities

1. Side-by-Side Comparison

Run parallel requests
Compare responses
Track differences
Document discrepancies

2. Output Diffing

Compare API responses
Diff file outputs
Check data formats
Validate transformations

3. Behavioral Verification

Test user flows
Verify business logic
Check edge cases
Validate error handling

4. Data Consistency Checking

Compare data states
Verify calculations
Check relationships
Validate constraints

5. Integration Validation

Test external integrations
Verify API contracts
Check message flows
Validate events

6. Acceptance Criteria Verification

Check feature completeness
Verify requirements
Validate user stories
Document coverage

Tool Integrations

Tool	Purpose	Integration Method
Diffy	Response comparison	API
Contract testing	API verification	CLI
Cypress	E2E validation	CLI
Playwright	Browser testing	CLI
Custom validators	Business rules	CLI

Output Schema

{
  "validationId": "string",
  "timestamp": "ISO8601",
  "source": {
    "environment": "string",
    "version": "string"
  },
  "target": {
    "environment": "string",
    "version": "string"
  },
  "results": {
    "total": "number",
    "passed": "number",
    "failed": "number",
    "skipped": "number"
  },
  "comparisons": [
    {
      "test": "string",
      "status": "passed|failed",
      "source": {},
      "target": {},
      "differences": []
    }
  ],
  "acceptance": {
    "criteria": [],
    "met": "boolean"
  }
}

Integration with Migration Processes

migration-testing-strategy: Validation execution
parallel-run-validation: Parallel comparison

Related Skills

performance-baseline-capturer: Performance comparison
data-migration-validator: Data validation

Related Agents

parallel-run-validator: Parallel validation
regression-detector: Regression detection

Source

git clone https://github.com/a5c-ai/babysitter/blob/main/plugins/babysitter/skills/babysit/process/specializations/code-migration-modernization/skills/migration-validator/SKILL.md

View on GitHub

Overview

Migration Validator evaluates functional equivalence between source and target systems after migration. It achieves this through side-by-side comparisons, output diffing, behavioral verification, data consistency checks, and acceptance criteria verification to ensure no regression.

How This Skill Works

The skill runs parallel requests against source and target, collects responses, and records discrepancies. It uses integrated tools (Diffy for response comparison, contract testing, Cypress, Playwright, and custom validators) to validate API contracts, data formats, and business logic.

When to Use It

After migrating a microservice, run side-by-side comparisons to validate parity.
During ETL migrations, perform output diffing and data consistency checks.
Validate end-to-end user flows across migrated systems to ensure seamless user experience.
Test external integrations and API contracts post-migration to catch contract violations.
Confirm acceptance criteria and user stories are met for migrated features.

Quick Start

Step 1: Configure source and target environments and establish baseline expectations.
Step 2: Run parallel requests and perform side-by-side comparisons using the Diffy-based workflow.
Step 3: Review differences, execute behavioral tests, and generate the validation results with an acceptance verdict.

Best Practices

Establish a baseline from the source system before migration.
Run parallel validations to minimize drift and accelerate feedback.
Automate side-by-side and behavioral tests with robust edge-case coverage.
Validate data consistency, calculations, and relationships across systems.
Document discrepancies and trace them to acceptance criteria and user stories.

Example Use Cases

Side-by-side API response comparison for a migrated order service across environments.
Output diffing of ETL data transforms during a data migration.
Behavioral verification of login and checkout flows after system migration.
API contract validation for an external payment gateway integration post-migration.
Acceptance criteria verification ensuring feature completeness after migration.

Frequently Asked Questions

Add this skill to your agents