Presentation: TweetAbout Rules and Runners

Developers are faced with two problems if they write tests with JUnit. The first one is very common: a piece of code that is used by several tests. Test inheritance, test utility classes and even copy-and-paste are the solutions on hand. The second problem is less common: changing parts of JUnits default behaviour. This includes the way how JUnit locates tests and how it handles assertions. It is even possible to define a test with something else but a method.
 
JUnit provides extension points that solve this problem. This talk will explain them and the way JUnit works in general. It includes examples that point out the power of the extension points and how they support writing beautiful tests.