Skip to main content

Use Cases

Seedling fits into several key workflows — from CI pipelines to local development.

CI Pipeline Data Seeding

The most common use case: generate fresh test data in CI before running your test suite.
Benefits: No stale snapshots, no manual SQL files, every CI run gets fresh referentially-valid data.

E2E Workflow Testing with Replay

Pair Seedling with Replay — an E2E workflow testing engine — for a complete data-backed CI pipeline:
Seedling produces fresh, referentially-valid rows every run. Using --seed 42 guarantees the same data set across CI runs, so your Replay assertions never flake due to changing data. For local development, chain both tools in one command:

Integration Testing

Seed directly into your test database with deterministic seeds for reproducible tests:
Use --seed 42 for reproducible test data — the same seed produces the same rows every time, making tests predictable and debug-friendly.

Staging Environment Refresh

Quickly populate a staging environment with realistic data:

Local Development

Generate a small dataset for local development without needing production data:

Load Testing

Scale up to production-level volumes for performance testing:

Schema Migration Testing

After running migrations, regenerate data to verify the new schema works:

Data Analysis & ML

Generate CSV or JSONL datasets for analytics workflows: