Everyone agrees that unit tests are essential for building robust and maintainable software components. But how much code coverage should a project have? We claim that even 100% coverage is not enough.

I want to show the concept of unit, integration and acceptance tests by using PHPUnit. You will learn more about how to structure your source code (SOLID/DDD) to make it easier testable and more robust at the same time. On top, the audience will see that the goal of 100% coverage is reachable.

## What you will learn from this talk
- How to properly separate classes and dependencies.
- How to properly separate between unit, integration and acceptance tests.
- How to get to 100% code coverage.

## Why should you accept this talk
This is a completely new talk I'd like to prepare for your conference.
In this talk, I want to build up a better understanding of how to write more robust and better testable code at the same time with just a few simple rules.

In addition, I show that even 100% code coverage is not enough and why we do integration-, acceptance- and even SmokeTests by using PHPUnit. This helps to reduce the number of bugs extremely.

Feel free to have a look into some slides of a similar talk we held some years ago: http://www.sebastianthoss.de/en/talks/99-percent-is-not-enough.html