Summary: So you have a large project code base that you keep changing, with a team of members with mixed skills. You need to ensure that the code you write, including the tests, is of high enough quality so that two moths from now you can still read them, understand what they do, understand why they do that, and change them. At the same time, you want to give others the time and tools to adjust to test infected development and hopefully eventually test-driven development.

Does the above sound challenging enough? That is what we are trying to do at Guidewire through the releases. I would like to share three things with others who are facing the similar situation: design of the JUnit extension, continuous integration tool, and the branching strategy.

Format and duration: I would like to keep it short. So I'll go over one topic for no more than half an hour and start the conversation. I think with the three items it will run over time so we should keep a cap at two hours.