Sebastian is an experienced and dedicated software engineer specializing in object-oriented design and programming, software architecture, code quality and agile. His interests include testing, programming, software engineering and agile software craftsmanship. He's also a speaker (JDD, GeeCon, NDC), writer and contributor to several blogs (DZone, JavaCodeGeeks) about Software Development and Agile Software Craftsmanship.
How often did you hear developers who were proving quality of their application’s code by sharing information about really high coverage and a huge number of unit tests? How often did you hear how unit tests can make your life easier. How having unit tests makes it possible to introduce changes and make refactoring safier? Do you believe in it? What’s your experience? I will show you why all of those “proofs” are invalid and wrong. I will show you the false impression of feeling safe in those dangerous places where your code is covered only with tones of unit tests. But it won’t be all. I won’t leave you alone in this place. I will tell you what you can do to make things better. I will show you the difference between coverage and quality. Between unit tests and safety.