Creator of Xunit and Nunit V2 James Newkirk, Microsoft

James Newkirk is the Product Unit Manager for CodePlex, Microsoft's community open source project hosting site. In this role, he is responsible for the site's strategic direction and product development. He is the co-author of "Test Driven Development in Microsoft .NET" (Microsoft Press, March 2004). Prior to joining Microsoft he co-authored "Enterprise Solution Patterns in .NET" (Microsoft patterns & practices) and "Extreme Programming in Practice" (Addison-Wesley). In between writing books and consulting on software projects, James led the development of NUnit V2.

Go to James' blog here

Presentation: "Evolutionary Design"

Time: Tuesday 13:00 - 13:45

Location: To be announced

Abstract: How much of the design of a system changes during implementation? When these inevitable changes occur the design must evolve to meet the new requirements. If it is truly inevitable then an interesting question can be posed? Instead of spending a large amount of time upfront on the design can you put in place a series of practices to enable the design to evolve during the implementation? This session highlights the various practices of Evolutionary Design (i.e. Test-Driven Development, Refactoring, Simple Design, and Continuous Integration) and how these practices work together to allow the design to evolve as requirements change.

Presentation: "Lessons Learned in Programmer Testing"

Time: Tuesday 14:00 - 14:45

Location: To be announced

Abstract: It has been more than seven years since the first release of NUnit 2.0, an open source unit testing tool. In that time, literally millions of tests have been written using the tool. Many of these tests have become and continue to be invaluable resources for their teams. Unfortunately, many other NUnit-based tests have not been maintained and are now viewed as having been a waste of effort from the beginning. What separates tests that are used, maintained, and highly valued from tests that are quickly discarded? This session describes seven key ideas that will increase the readability of NUnit tests and make them much easier to maintain. Learn about the impact of test fixture size, dependency injection, and mock frameworks on unit testing. Other lessons include information on usage of [ExpectedException], [Setup], and [TearDown]. Incorporating these and the other lessons can make the difference between tests that become a burden to the team and tests that become practical, growing resources.