<<< Previous speaker Next speaker >>>

Erik Doernenburg

 Erik  Doernenburg

Erik Dörnenburg is an application architect and developer at ThoughtWorks Inc., where he is helping clients with the design and implementation of large-scale enterprise solutions. Building on his experience with J2EE, Microsoft .NET and other environments, Erik is continually exploring new patterns of enterprise software.

Before joining ThoughtWorks Erik was Technical Director at Pixelpark UK, a new media company, where he integrated enterprise systems with web-based solutions and a variety of digital delivery channels. His career in enterprise software began in the early nineties on the NeXTSTEP platform and Erik has been an advocate of agile, test-driven, object-oriented development and Open Source software for many years. He holds a degree in Informatics from the University of Dortmund and has studied Computer Science and Linguistics at the University College Dublin.

Presentation: "Automated Web Application Testing with Selenium"

Track:   Solution Track 1

Time: Wednesday 13:00 - 14:00

Location: Wordsworth Room


Selenium is a test tool that allows you to write automated web application tests in many programming languages. The test use any mainstream browser with JavaScript support and can target arbitrary websites.

This talk starts with a quick demo of creating automated tests using the Selenium IDE and then show how these tests can be integrated with existing Java, C#, or Ruby test suites. We'll end with a discussion on how to write robust tests, and how to structure tests to make them more reusable.

Password protected Download slides

Tutorial: "Test-Driven Development"

Track:   Tutorial

Time: Monday 13:00 - 16:00

Location: To be announced


This tutorial demonstrates the development of a small example application using test-driven development and related technologies. The system will comprise a handful of Java classes that exemplify typical components found in enterprise applications, including domain objects and a service layer. The tutorial is structured into three 'iterations' which cover

  1. state-based testing with JUnit
  2. interaction-based testing with JUnit and jMock
  3. deployment in lightweight containers such as PicoContainer and Spring.

The iterations not only introduce the concepts but also provide room for the discussion of trade-offs and edge cases, e.g. how to deal with testing private methods and when not to use dynamic mocks but fake objects.

Attendees gain an understanding of how proper use of test-driven development fosters good design; through decoupling and interface discovery for example. Attendees will also gather a nice catalogue of the most commonly used patterns used in conjunction with test-driven development.