Disable Percy (#11852)

* Disable Percy

While visual regression testing is without doubt an essential part of
quality assurance, the way we're currently using Percy brings little
to no value while causing mainenance overhead. Therefore, we're disabling it
until we have figure out https://github.com/vector-im/wat-internal/issues/36
and https://github.com/vector-im/wat-internal/issues/56.

* Also disable nightly build

* Comment out Percy step instead of fiddling with the output value

* Appease the frigging linter
This commit is contained in:
Johannes Marbach 2023-11-10 22:25:18 +01:00 committed by GitHub
parent bef8aec483
commit 7a56d61a9e
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
4 changed files with 30 additions and 12 deletions

View file

@ -238,6 +238,10 @@ should generally try to adhere to them.
## Screenshot testing with Percy
**⚠️ Percy is disabled while we're figuring out https://github.com/vector-im/wat-internal/issues/36**
**and https://github.com/vector-im/wat-internal/issues/56. We're hoping to turn it back on or switch**
**to an alternative in the future.**
We also support visual testing via [Percy](https://percy.io). Within many of our
Cypress tests you can see lines calling `cy.percySnapshot()`. This creates a
screenshot and uses Percy to check whether it has changed from the last time