Introduce visual testing process for internal development of Desktop GUI

[jennifer-shehane]

Current behavior:

There was a recent css change made to the desktop-gui package of Cypress that caused some unexpected changes to the design/css of the desktop-gui.

Original PR: #4737
Following breaking changes (that we know of): #4959 #4912 #4888 #4795

The problem is that none of our internal tests caught these issues. They were only found after using the Desktop-GUI manually within development. So, it's possible there is still some stuff that's broken.

Desired behavior:

Introduce a process into the Cypress development team to test visual changes in our own desktop-gui package.

Hopefully, after vetting and solidifying a process, we can expand this out to our other visual components, the runner and reporter packages.

This will also provide a great opportunity to put ourselves in the shoes of users of Cypress (like ourselves) so we can define the problem set and look through the solutions out there.

[bahmutov]

I am feeling this - trying to add Experiments block to the Settings tab, the entire communication is back and forth via screenshots in #6265

I want to start with a few Percy screenshots for the Settings tab and this will add a visual workflow to the PR reviews. Probably we can start with a single project for now (and not divide per package).

[cypress-bot]

The code for this is done in cypress-io/cypress#6421, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

[jennifer-shehane]

Released.

This comment thread has been locked as resolved.