This Wednesday evening (May 5th) I have the pleasure of being invited to talk at the Canberra Java Users Group, where I will be giving a talk entitled "Real Developers Don't Need Unit Tests".
In a well-organized build process, you want lightning-fast unit tests to run first, and provide whatever feedback they can very quickly. A nice way to do this is to be able to class your tests into different categories. For example, this can make it easier to distinguish between faster running unit tests, and slower tests such as integration, performance, load or acceptance tests.
Until April 9th (this Friday!), get a 20% discount on the Melbourne 'Testing and TDD for Java Developers' workshop (running April 15-16)!
A new draft chapter of the 'Continuous Integration with Hudson' book is now available online. This new chapter covers all the subtleties of installing Hudson. You can download the PDF version on the book web page.
I'm proud to say that I will be participating in the upcoming Über Conf 2010 in Colorado this June.
I will be in Melbourne on April 15-16 for the next Testing and TDD for Java Developers workshop.
Continuous Integration with Hudson is a new open source book project in the works. In the spirit of 'eating our own dogfood', this book is produced using Hudson. In this article, I discuss the build framework used for the 'Continuous Integration with Hudson' book.
Continuous Integration is a cornerstone of modern software development best practices. Hudson, an Open Source Continuous Integration tool, is by far the most popular Continuous Integration tool on the market, and for good reason!
The Testing and TDD for Java Developers workshop is coming to Melbourne again on April 15-16.
Sometimes, you may need to move or copy Hudson build jobs from one Hudson instance to another, without copying the entire Hudson configuration. For example, you might be migrating your build jobs to a Hudson instance on a brand new box, with system configuration details that vary from the original machine.