False Errors in Test Tooling - TestQuality

Traditional GUI automation is linear; it follows a set of steps. The first time you run it, it can’t add any value, as the feature isn’t done until the automation runs. Once test automation runs a second time, it effectively becomes change detection. This leads to a large number of “failures” that are not actually failures. Whether they are false positives or false negatives, we need a way to fix the automation tooling.

Original Article at Sticky Minds