generating-tests

Generate merge-safe TestSpec artifacts for migrated tables, views, or materialized views.

3|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/accelerate-data/migration-utility --skill generating-tests-accelerate-data
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generating-tests
Source: https://github.com/accelerate-data/migration-utility/tree/main/skills/generating-tests
Command: npx skills add https://github.com/accelerate-data/migration-utility --skill generating-tests-accelerate-data

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Generate or extend a TestSpec for a migrated object (table, view, or materialized view) to produce a merge-safe artifact at test-specs/<schema.object>.json, especially after SQL changes or reviewer feedback.

Core Features & Use Cases

  • Automated generation of TestSpec from catalog context, with guardrails and invariants.
  • Merge-mode aware persistence, preserving approved scenarios while adding new coverage.
  • Context-aware fixture and branch management, guiding deterministic test data generation.

Quick Start

Run the ready test-gen flow for a target object to generate test-specs/<schema.object>.json in a merge-safe manner.

Frequently Asked Questions about generating-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate test specs for database migrations without causing merge conflicts?

Generate merge-safe TestSpec artifacts for migrated tables, views, or materialized views by applying merge rules that preserve approved scenarios while adding new coverage at test-specs/<schema.object>.json. This ensures concurrent migrations avoid conflicts during persistence.

What is a merge-safe test spec and when do I need it for a database migration?

A merge-safe test spec is a JSON artifact at test-specs/<schema.object>.json that defines testing guardrails and invariants for migrated objects. You need it after SQL changes or reviewer feedback to ensure deterministic test data generation across branches.

How to update test specs after SQL changes or reviewer feedback?

Run the test generation flow for a target object to validate its type from the catalog, apply merge rules, and persist updated artifacts and catalog summaries. This extends existing test specs without overwriting previously approved test scenarios.

Can I generate test specs for materialized views and tables, or just standard database tables?

You can generate test specs for tables, views, and materialized views. The generation process validates the specific object type from the database catalog before applying the appropriate merge rules and persisting the artifact.

Does generating test specs for migrations require manual fixture management?

Manual fixture management is not required. The generation process is context-aware, guiding deterministic test data generation with branch management and fixtures derived directly from the catalog context.

What are the limitations of automated test spec generation for database migrations?

Test spec generation targets new or updated specs at test-specs/<schema.object>.json after SQL changes, meaning it focuses on migrated objects rather than comprehensive schema-wide test orchestration or executing the generated test scenarios directly.