GRI-1856: MVP acceptance test plan #80
No reviewers
Labels
No labels
Area/Backend
Area/Database
Area/Docs
Area/Frontend
Area/Infra
Area/Security
Area/Tests
Area/Tooling
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Lang/Python
Lang/Rust
Lang/Shell
Lang/SQL
Lang/TypeScript
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Routing
Auto
Routing
Hold
Routing
Human
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Grimoirix/grimoire-of-digital-signage!80
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/GRI-1856-mvp-acceptance-test-plan"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Step 1 of GRI-1856: the MVP acceptance test plan,
plan/tests/mvp-acceptance.md.Every case is derived from the GRI-1761 scope table (rev 9) plus the enrolment,
media-pipeline, content-model, offline-first and protocol docs already on
dev. No implementation exists yet (GRI-1838 skeleton still in progress, noserver routes or crates/server tests), so nothing here was read from code.
42 cases across the six scope-table rows: first-user setup, enrolment pending
to approved, IP auto-approve, blocklist, trusted-proxy header spoofing, upload
image/video/PDF/URL, playlist order and durations, offline playback, and
reconnect. Each case has Given/When/Then, a CI level (Unit/Integration/
Contract/E2E/Hardware per
testing-strategy.md), and a happy/unhappy pairing.Packaging rows are marked Hardware-only, matching the existing rule in
testing-strategy.mdthat there is no Pi/mini-PC in CI to gate on — forge#28/#29 verify those by hand in the test week.
Step 2 (automated HTTP/WebSocket integration tests) waits on server routes
landing per the parent issue; none have yet.
Test plan
./scripts/local-gates.shpassed locally (Rust + cargo-deny +frontend-web check/build)