seed-save-flow-test-coverage

ARCHIVED

review my test coverage of these seed flows. An inability to hit save should not be left untested.

STAGES

  1. proposal05-19
  2. requirements05-19
  3. design05-19predates the Figma as-is + proposed pair
  4. tasks05-19
  5. build—
  6. archived—

CAPABILITY

  • seed-persistence-test-harness5 requirements

OUTCOMES — AND HOW EACH IS MEASURED

  • ✓1.1CI fails when insert returns a Supabase error (Scenario: Insert fails when Supabase returns an error)not stated
  • ✓1.2CI fails when update returns a Supabase error (Scenario: Update fails when Supabase returns an error)not stated
  • ✓1.3CI proves insert and update succeed when Supabase returns a row (Scenario: Insert and update succeed when Supabase returns a row)not stated
  • ✓1.4CI cannot hang indefinitely on persistence async tests (Scenario: Persistence async tests are time-bounded)not stated
  • ✓1.5Empty list partial updates emit JSON arrays not SQL null (Scenario: Partial update clears annotations to empty list)not stated
  • ✓1.6Minimal insert seeds get empty JSON arrays for required JSONB columns (Scenario: Insert supplies empty JSON arrays for required JSONB columns)not stated
  • ✓1.7Invalid year never becomes NaN in the DB payload (Scenario: Non-numeric year input yields no invalid DB value)not stated
  • ✓1.8Unchanged HTTPS packet previews do not trigger upload or fetch (Scenario: Existing HTTPS preview with path skips upload helpers)not stated
  • ✓1.9New blob or data packet images still trigger upload path (Scenario: New local blob image triggers upload)not stated
  • ✓1.10Tests that hit fetch for upload cannot hang (Scenario: Upload path tests do not hang on `fetch`)not stated
  • ✓1.11Documented command runs persistence tests in a clean install (Scenario: Documented test command runs in prototype app)not stated

WHAT HAPPENED

  1. TASKS

    proposal and specs and design and tasks landed

    2026-05-19
    • chore(openspec): archive seed-save-flow-test-coverage

History read from a manifest built at 2026-09-30 (09e7bcc).

0 pull requests, found by commits touching the change folder · 1 commit(s) carry no pull request number