Description:
Test-driven development received a lot of attention in 2003, and the interest will grow in 2004. For good reason: everyone agrees testing is important, but now many programmers are claiming that by writing tests first, they see better designs emerge. These same programmers quickly point out that test-driven development makes them feel more productive and less stressed. It all sounds good, but how do you get started on a real project?

Writing tests doesn't have to be difficult or time-consuming. We'll explore 12 practical ways to start writing JUnit tests, and keep writing them, regardless of your development process. You'll be able to immediately apply these no-nonsense techniques toward improving your design and testing skills. In no time you'll be writing better code, and faster!

Speaker
Mike Clark helps teams build better software faster. He is a perennial feature speaker on the No Fluff, Just Stuff circuit, co-author of Bitter EJB (Manning), editor of the JUnit FAQ, and publisher of his popular weblog. He has created several open source tools including JUnitPerf and JDepend. He's been crafting software professionally since 1992, immersed in Java since 1997. Mike is president of Clarkware Consulting, Inc. based in Denver, CO.

Resources
Download presentation files (200403_testing.pdf)
Clarkware Consulting, Inc
Bitter EJB
Article on Testing (1/22/04)