You've probably heard it before. "We need to ensure we have at least 80% code coverage on this code base! We won't be confident everything is working otherwise!" While at first, this does sound like sound logic, it turns out code coverage isn't a goal that we should be actively striving for. It could actually make your code worse.

Before worrying about how much code coverage an application has, we should consider the application itself. Is this a mission critical system? Is it acceptable if it goes down for a period of time? Who are the stakeholders involved for each feature? Code coverage only tells you if a line is covered, but not all lines are created equal.

In this session, we'll discuss the common pitfalls of using code coverage as a goal and how we should really be using code coverage to better our applications.