In actual enterprise level applications, either web or services based, it's more and more necessary to have a suite of tests to be executed automatically in order to prevent regressions of the system.
Commercial tools actually available are quite expensive and they often retain high levels of complexity or too high learning curves.
In this presentation you will be introduced to some mature open source tools, with particular reference to FitNesse for services test and Selenium for web applications test.
Bruno Bossola starts to learn computer science since medium schools, when thanks to a Commodore Vic20 he discovers the world of programming. He begins to work in C in 1988, then from 1996 in Java, using JDK 1.02. He develops one of the first distributed objects application in Italy, continuing then in the following years building large scale application for the enterprise using RMI, CORBA and finally J2EE.
In 1999 he coaches one of the first group that adopts XP methods in Italy. In 2002 he has co-founder of Java User Group Torino, that quickly became one of the top 25 JUGS in the world. In 2005 he is recognized as Java Champion, member of the international community that collects the more representative personalities of the Java world
He has been promoting and teaching Java technologies as a well-known speaker in Italy since 2002 at developer conferences like Webbit, AgileDay, JavaConference, Javaday.
Unitils - making unit testing easy— 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.
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.
