Skip to content

#250 child: Establish Atlas screenshot/golden governance without brittle pixel-locking #270

Description

@Joncallim

Parent: #250. Test-governance pass.

Use screenshots to protect visual quality without making every browser/font antialiasing difference a blocker.

Separate: (1) semantic golden AtlasModel/layout JSON, which should be exact; (2) geometry assertions, which are numeric/toleranced only where browser measurement requires it; (3) screenshot baselines on controlled browser/theme/viewports for visual regression; and (4) human visual approval for intentional redesigns.

An intentional projection/layout version change must update exact semantic/layout goldens with review (#264). Screenshot diffs alone cannot authorize semantic change. Avoid enormous fixture snapshot churn: select a representative visual matrix while property tests cover combinatorial permutations.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions