Problem Statement
Playwright mobile visual snapshots trigger mismatches and conflicts in PR integrations even when zero visual or code changes occurred.
Goal
Determine the root causes of snapshot inconsistencies (like OS configuration or environment package updates) and stabilize visual snapshot testing.
Non-Goals
Updating actual UI layout code or changing Playwright target viewports.
Proposed Approach
- Inspect font-render inconsistencies in Noble Docker image.
- Test visual outputs locally vs. GHA runner to identify discrepancy triggers.
Alternatives Considered
| Approach |
Rejected because |
| Disabling Playwright mobile checks entirely |
Reduces visual regression coverage |
Architectural Impact
Scope
Files expected to change
- UNDERSTAND THE ISSUE
Restate the problem in your own words:
Snapshots drift across environments, causing false test failures.
State the underlying GOAL:
Establish consistent test environments.
Flag any ambiguity in the issue as written:
None.
- DETERMINE APPROACH
Propose the most likely correct solution approach:
Analyze render differences and apply environment alignment configurations (like font packages).
Identify at least one alternative approach and state why it was rejected:
Accepting manual updates on every run (rejected as it pollutes PR history).
Call out any architectural decisions this approach forces:
None.
Flag if the approach touches shared/core code used by multiple features:
Yes, impacts CI test suites.
- SPECIFY SCOPE
IN SCOPE:
Debugging Playwright snapshot execution and environment properties.
OUT OF SCOPE:
Altering actual client application view layouts.
Flag if achieving the goal is impossible without violating the out-of-scope boundary:
No.
- DEFINITION OF DONE
List concrete, verifiable completion criteria:
State what must be manually verified vs. what can be automated:
Playwright snapshot tests verification is automated.
State explicitly what is NOT required for this issue to be considered done:
No redesign of component code.
Problem Statement
Playwright mobile visual snapshots trigger mismatches and conflicts in PR integrations even when zero visual or code changes occurred.
Goal
Determine the root causes of snapshot inconsistencies (like OS configuration or environment package updates) and stabilize visual snapshot testing.
Non-Goals
Updating actual UI layout code or changing Playwright target viewports.
Proposed Approach
Alternatives Considered
Architectural Impact
Scope
Files expected to change
tests/visual.spec.tsRestate the problem in your own words:
Snapshots drift across environments, causing false test failures.
State the underlying GOAL:
Establish consistent test environments.
Flag any ambiguity in the issue as written:
None.
Propose the most likely correct solution approach:
Analyze render differences and apply environment alignment configurations (like font packages).
Identify at least one alternative approach and state why it was rejected:
Accepting manual updates on every run (rejected as it pollutes PR history).
Call out any architectural decisions this approach forces:
None.
Flag if the approach touches shared/core code used by multiple features:
Yes, impacts CI test suites.
IN SCOPE:
Debugging Playwright snapshot execution and environment properties.
OUT OF SCOPE:
Altering actual client application view layouts.
Flag if achieving the goal is impossible without violating the out-of-scope boundary:
No.
List concrete, verifiable completion criteria:
State what must be manually verified vs. what can be automated:
Playwright snapshot tests verification is automated.
State explicitly what is NOT required for this issue to be considered done:
No redesign of component code.