Short answer: Yes, I do trust all that stuff. However, it keeps breaking, and clients keep getting frustrated. I will trust them more when I we don't find any

Short answer: Yes, I do trust all that stuff. However, it keeps breaking, and clients keep getting frustrated. I will trust them more when I we don't find any last-minute bugs that delay releases based on whatever testing configuration the client decided to use. Long answer: > Why do you need to test against multiple languages? Don't you trust the review process for when you add i18n translations? The product was designed without a proper i18n process in place, and it's being bootstrapped as I write this. However, as an example, some English strings are shorter than their non-English equivalents. Some languages with more characters per word may include strings that overrun the screen. > Why do you test Chrome and Edge? Don't you trust that they're basically the same browser? No, we've had use cases where something worked on Chrome but didn't work on Edge. Furthermore, I don't think their lists of supported locales matches. > Why do you test against both a Macbook and an HP? Don't you trust you can render buttons and image similarly on both platforms ? Again, cases that have worked on one have failed on the other in the past.