Writing unit tests should be easy and intuitively... at least in theory. In practice, you need a lot of infrastructure, libraries and boilerplate code before you get to do something productive on a database driven enterprise project.
Unitils is an open source library, written by a number of colleagues from Ordina J-Technologies , aimed at making unit testing easy and maintainable. Unitils builds further on existing libraries like DBUnit and EasyMock and integrates with JUnit and TestNG. The framework includes general assertion utilities, support for database testing, for testing with mock objects and offers integration with Spring and Hibernate. It has been designed to offer these services to unit tests in a very configurable and loosely coupled way.
During this presentation we will discuss unit test guidelines and best practices. We will make use of examples to demonstrate how Unitils can help you in writing simple and maintainable unit tests.
Frederick Beernaert is a senior software engineer at Ordina Belgium with more than 5 years of experience in Java and J2EE. As a competence leader of the Java and Tooling Competence Center, he is co-responsible for the Ordina J-Technologies strategy and gathering / spreading knowledge in the J2EE domain.
Frederick is one of the developers in the Unitils project. He is also active on the Alfresco forum and contributes to the forge.
Filip Neven is senior software engineer at Ordina Belgium with more than 5 years of experience in Java and J2EE. He has a strong interest for agile development, code quality and unit testing. For the past 2 years, he has been responsible for quality and unit testing on projects in one of the largest companies in Belgium.
Filip is one of the two founders and lead developers of the Unitils project.
UI Test Automation— UI test automation is, nowadays, a commonly used approach. First, because of the tools offering, second because different organization started to realize (if they did not do it before) how high is the defect cost, so they started to think about getting more from testing while spending less on it. For many, it becomes obvious pretty soon that the automation is not as beneficial as if first seemed.
