A lot of development teams write automated tests to check that their code and application behave as intended. However, the quality of these tests is unfortunately often underappreciated. If any attention is paid to test quality at all, it is typically done in terms of code coverage, which, as attendees will see from examples I’m using in the talk, is a flawed metric. Yet, teams rely on the results of these tests in their software development lifecycle. Isn’t there a better way to get information about the quality of our tests? In this talk, I’ll discuss how the tests you…....