-
Notifications
You must be signed in to change notification settings - Fork 190
Set up screenshot tests #3982
Copy link
Copy link
Open
Labels
A-Developer-ExperienceWorkflow of developing: building, linting, debugging, profiling, etc.Workflow of developing: building, linting, debugging, profiling, etc.O-OccasionalAffects or can be seen by some users regularly or most users rarelyAffects or can be seen by some users regularly or most users rarelyT-TaskRefactoring, enabling or disabling functionality, other engineering tasksRefactoring, enabling or disabling functionality, other engineering tasks
Description
Metadata
Metadata
Assignees
Labels
A-Developer-ExperienceWorkflow of developing: building, linting, debugging, profiling, etc.Workflow of developing: building, linting, debugging, profiling, etc.O-OccasionalAffects or can be seen by some users regularly or most users rarelyAffects or can be seen by some users regularly or most users rarelyT-TaskRefactoring, enabling or disabling functionality, other engineering tasksRefactoring, enabling or disabling functionality, other engineering tasks
Type
Fields
Give feedbackNo fields configured for issues without a type.
I keep making UI changes that would require screenshot tests to have any practical coverage for. We should set these up with Playwright, GitHub Actions, and Docker (for updating the screenshots locally), taking notes from the existing systems in Element Web and Compound Web.