27 lines
1.4 KiB
Markdown
27 lines
1.4 KiB
Markdown
## MODIFIED Requirements
|
||
|
||
### Requirement: Public screens have desktop and mobile visual baselines
|
||
|
||
The system SHALL keep versioned screenshot baselines for the public screens available in this phase (SPEC §13.5): Home, Serviços, Portfólio, Detalhe do portfólio, Sobre, Contato, Privacidade and branded 404, at 1440×1000 desktop and 390×844 mobile, under the Heritage Editorial identity. A rendering change that alters those screens MUST fail the browser suite until the diff is reviewed and baselines are explicitly updated.
|
||
|
||
#### Scenario: Unintended visual change fails the suite
|
||
|
||
- **GIVEN** approved baselines exist
|
||
- **WHEN** a code change alters the rendering of a covered screen
|
||
- **THEN** the visual assertion MUST fail and report the diff
|
||
|
||
#### Scenario: Both viewports are covered
|
||
|
||
- **WHEN** the visual suite runs
|
||
- **THEN** each covered screen MUST be asserted at 1440×1000 and 390×844
|
||
|
||
#### Scenario: Heritage Editorial identity is captured
|
||
|
||
- **WHEN** approved baselines for the home are reviewed after this change
|
||
- **THEN** they MUST reflect EB Garamond typography, olive/paper palette and sharp-edged editorial layout rather than the previous gold/rounded placeholder look
|
||
|
||
#### Scenario: Motion does not destabilize new baselines
|
||
|
||
- **WHEN** Sobre, Contato, Privacidade, or 404 is captured
|
||
- **THEN** the browser MUST use the final reduced-motion state before asserting the screenshot
|