When thinking about tests against code, have you "done enough?" How do you know that the code is covered appropriately, that odd bugs aren't going to crop up? Did you cover all the use cases and what if someone changes the code down-the-road? This session is about the unit and integration tests that a developer writes to test their code immediately, not about higher level tests that are written by a QA individual or department. This session will examine the code and tests holistically against the various lifecycle stages of code and how the testing needs to adjust: • Define Inputs and Outputs • Write Initial Test Coverage • Handling Bug Coverage • Refactoring • Abstraction • Future Work (how are tests affected?)