Mike Clark的Test-Driven Development with JUnit Workshop

呵呵，自己现在是没有可能参加这样的培训了，不过从Outline中至少可以看看需要努力的方向。

以下内容摘自 Clarkware Consulting的 Test-Driven Development with JUnit Workshop ：

Workshop Outline

In this workshop, we'll cover a dozen ways to get the testing bug through a combination of lecture and hands-on exercises. Topics covered include:

• Why Test-Driven Development?
  
  • The benefits of test-driven development
  • Reducing the cost (and fear) of change
  • How to build better software, faster
• Writing JUnit Tests
  
  • Test cases
  • Test fixtures
  • Test suites
  • JUnit best practices
  • "What should I test?"
• Asserting Your Expectations
  
  • Test-driven development demystified
  • Red, green, refactor rhythm
  • Extensive hands-on exercises
• Using TDD as Design Feedback
  
  • Object-oriented design insights
  • Decreasing coupling, increasing cohesion
  • Using mock objects effectively
  • Extensive hands-on exercises
• Refactoring
  
  • Why and when to refactor
  • Writing code that responds to change
  • Detecting code smells
  • Examples of quick and valuable refactorings
  • Refactoring and code reviews
• Testing Legacy Code
  
  • "How can I test this?"
  • Refactoring for testability
  • Techniques for breaking dependencies
  • Extensive hands-on exercises
  • Examples from your project
• Expanding Your Toolbox
  
  • Testing the database layer with DbUnit
  • Testing web applications with HtmlUnit, Canoo WebTest, etc.
  • Using Cactus to test server-side J2EE components
  • Continuous performance testing with JUnitPerf
  • Acceptance testing with FitNesse
  • Rolling your own integration/acceptance testing harness atop JUnit
• Making Testing Part of Your Build Process
  
  • Integrating JUnit with Ant
  • Setting up a continuous integration environment using CruiseControl
  • Monitoring the build and test status