Comprehensive seed data representing production patterns #203

Open
opened 2026-06-13 20:22:31 +00:00 by ldraney · 0 comments
Owner

Type

Feature

Lineage

Standalone -- discovered during today-view feature work. Dev DB had no last-week data, missing properties, no daily notes.

Repo

ldraney/landscaping-assistant

User Story

As a developer
I want bin/rails db:seed to populate every UI section with realistic data
So that I can test features without manually creating data

Context

Current seeds only create 3 services. All properties and work queue items must be created manually, which means dev testing misses sections that only appear with specific data patterns (last week, still undone, done by other crew). Seed data should mirror production: ~15-20 properties across multiple cities, a full week of queue history, daily notes, multiple crew members with different roles.

File Targets

Files the agent should modify or create:

  • db/seeds.rb -- expand with properties, queue items, daily notes, crew members

Files the agent should NOT touch:

  • db/schema.rb -- no schema changes needed
  • app/models/ -- no model changes

Feature Flag

None -- dev tooling only, not user-facing.

Acceptance Criteria

  • bin/rails db:seed on a fresh DB populates every today-page section
  • Navigating to different days shows varying data
  • Last-week-same-day section shows items with Done/Other crew badges
  • Still Undone section has items from earlier this week
  • Not Done This Week section has active properties without completions
  • Done by Other Crew section has items
  • Daily notes have content for at least 2 days
  • Seed is idempotent (safe to run multiple times)
  • All dates are relative to Date.current, not hardcoded

Test Expectations

  • Manual: bin/rails db:reset then verify all sections render
  • Run command: bin/rails db:seed

Constraints

  • Use find_or_create_by patterns for idempotency
  • No hardcoded dates
  • Property names/addresses should be realistic but obviously fake

Checklist

  • PR opened
  • Tests pass
  • No unrelated changes
  • landscaping-assistant project
### Type Feature ### Lineage Standalone -- discovered during today-view feature work. Dev DB had no last-week data, missing properties, no daily notes. ### Repo `ldraney/landscaping-assistant` ### User Story As a developer I want `bin/rails db:seed` to populate every UI section with realistic data So that I can test features without manually creating data ### Context Current seeds only create 3 services. All properties and work queue items must be created manually, which means dev testing misses sections that only appear with specific data patterns (last week, still undone, done by other crew). Seed data should mirror production: ~15-20 properties across multiple cities, a full week of queue history, daily notes, multiple crew members with different roles. ### File Targets Files the agent should modify or create: - `db/seeds.rb` -- expand with properties, queue items, daily notes, crew members Files the agent should NOT touch: - `db/schema.rb` -- no schema changes needed - `app/models/` -- no model changes ### Feature Flag None -- dev tooling only, not user-facing. ### Acceptance Criteria - [ ] `bin/rails db:seed` on a fresh DB populates every today-page section - [ ] Navigating to different days shows varying data - [ ] Last-week-same-day section shows items with Done/Other crew badges - [ ] Still Undone section has items from earlier this week - [ ] Not Done This Week section has active properties without completions - [ ] Done by Other Crew section has items - [ ] Daily notes have content for at least 2 days - [ ] Seed is idempotent (safe to run multiple times) - [ ] All dates are relative to `Date.current`, not hardcoded ### Test Expectations - [ ] Manual: `bin/rails db:reset` then verify all sections render - Run command: `bin/rails db:seed` ### Constraints - Use `find_or_create_by` patterns for idempotency - No hardcoded dates - Property names/addresses should be realistic but obviously fake ### Checklist - [ ] PR opened - [ ] Tests pass - [ ] No unrelated changes ### Related - `landscaping-assistant` project
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ldraney/landscaping-assistant#203
No description provided.