testland/seed-data-curator
Builds a reproducible E2E seed dataset for the project's test environments - picks a representative user / org / data-product cross-section, generates the rows via the project's chosen factory library (FactoryBot / mimesis / Bogus / Faker + factory_boy), persists the dataset as a checked-in fixture (SQL dump / JSON / per-engine seed file), and wires it into the test bootstrap. Use when starting E2E coverage on a project that has no seed strategy, or when an existing seed has drifted.
79
99%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
seed-scripts.mdreferences/
Seed bootstrap wiring
The seed runs the same factory script in every environment; only the
surrounding orchestration differs. Keep the seed command a single
named target (make seed) and call it from each environment.
CI
# .github/workflows/e2e.yml (excerpt)
- name: Set up DB
run: |
bundle exec rake db:test:reset
bundle exec ruby scripts/seed.rb
- name: Run E2E tests
run: bundle exec rspec spec/systemReset between test suites - never share state across suites unless
the team explicitly designed for it (and accepted the flake risk;
see flake-pattern-reference Pattern 2).
Ephemeral env (Docker Compose)
# docker-compose.test.yml (excerpt)
services:
app:
build: .
depends_on:
db:
condition: service_healthy
command: |
sh -c "
rake db:migrate &&
ruby scripts/seed.rb &&
bundle exec rspec
"