Reports Persistence
3 requirements
·
6 scenarios
Reports Listing API
JR-reports-persistence-001
The system SHALL provide an authenticated API endpoint to list past workflow-generated reports for a user. The endpoint SHALL return an empty result set for domains without persistence enabled.
2 test scenarios
- Authenticated user lists their reports JR-reports-persistence-001.1
- Non-persistent domain returns empty list JR-reports-persistence-001.2
Report Download API
JR-reports-persistence-002
The system SHALL provide an authenticated API endpoint to download a specific past report. The endpoint SHALL deny access when the requesting user is not the report owner.
2 test scenarios
- Report owner downloads successfully JR-reports-persistence-002.1
- Non-owner download request denied JR-reports-persistence-002.2
Reports Tab in User Interface
JR-reports-persistence-004
The system SHALL provide a reports tab in the user interface that loads persisted reports on activation. The reports tab SHALL be hidden for domains without persistence enabled.
2 test scenarios
- Reports loaded on tab activation JR-reports-persistence-004.1
- Tab hidden for non-persistent domains JR-reports-persistence-004.2