ADDED Requirements
Requirement: Complete Screen Coverage
The Maestro screenshot flows SHALL capture all marketing-relevant screens in the application.
Scenario: Shopping list editor captured
- WHEN main screenshot flow runs
- THEN edit_shopping_list_view.dart is navigated to and captured
- AND screenshot shows the list editing interface
Scenario: Payment editor captured
- WHEN main screenshot flow runs
- THEN manage_payment_view.dart is navigated to and captured
- AND screenshot shows the payment creation/edit interface
Requirement: Screen Exclusion Documentation
Screens excluded from screenshot capture SHALL be documented with rationale.
Scenario: Error screen excluded
- WHEN reviewing screenshot coverage
- THEN oops_view.dart is excluded from marketing screenshots
- AND exclusion is documented (error states not suitable for store listings)
Scenario: Transient auth screens excluded
- WHEN reviewing screenshot coverage
- THEN verify_email_view.dart is excluded from marketing screenshots
- AND exclusion is documented (transient state during signup)
Reacties