Our VRT tests currently have a difference threshold of 5%, owing to some historical issues with SVGs. This means that some small changes don't actually trigger VRT updates, which is not great.
A 0% threshold can be a bit too aggressive, but in testing we found a 1% threshold was enough to catch a lot of legitimate differences and we should switch to that and update our current VRT references accordingly.
develop branch without changes0.05 to 0.01npm run test:visualtest_Do not alter or remove anything below. The following sections will be managed by moderators only._
misMatchThreshold should be 0.01 instead of 0.05.external prop on a Link should trigger a VRT failure, as in the past it would not.)0.05 to 0.01npm run test:visualtest and ensure the changes are valid.npm run test:visualapprove to check in the new VRT reference imagesexternal prop on a Link should trigger a VRT failure, as in the past it would not.)(Larger estimate on this one as it will involve ensuring a lot of VRT test updates are appropriate and might involve creating new issues when something has changed unintentionally.)
IB ✅
As a clarification to the description here, the misMatchThreshold is the percentage to use for the threshold, not a decimal representation of a percentage, so 0.05 is actually half of 1%, not 5%. The default value used by Backstop is .1; see Changing test sensitivity.
@aaemnnosttv @tofumatt @eugene-manuilov I believe we can close this issue now as this has already been taken care of in https://github.com/google/site-kit-wp/pull/2213/files#diff-632eaaf92e395d37506eda70160a8476d57c224d5bd3dcedfd3f6dbf6a52b5fdR56.
@felixarntz yes, we can close it. It has been already addressed.
Most helpful comment
@aaemnnosttv @tofumatt @eugene-manuilov I believe we can close this issue now as this has already been taken care of in https://github.com/google/site-kit-wp/pull/2213/files#diff-632eaaf92e395d37506eda70160a8476d57c224d5bd3dcedfd3f6dbf6a52b5fdR56.