Oh, I am not able to participate in such training now, but at least you can see the direction you need to work from Outline.
The following is taken from
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 DevelopredReducing The Cost (and "of changehow to build better Software, Fasterwriting Junit Tests
Test Casestest FixTureStest Suitesjunit Best Practices "What Should i Test?" Asserting Your Expectations
Test-Driven Development DemystifiedRed, Green, Refactor Rhythmextensive Hands-OnErcisesusing TDD AS Design FeedBack
Object-Oriented Design InsightsDecreasing Coupling, Increasing Cohesionusing Mock Objects EffectivelyExtensive Hands-on EXERCISESREFAANG
Why and when to refactorwriting code That responds to changeetecting code smellsexamples of quick and value refactoringsrefactoring and code reviewstesting legacy code
"How can I Test this?" Refactoring for TestabilityTechniques for Breaking Dependenciesextensive Hands-on EXERCISESEXAMPLES from Your ProjectExpanding Your Toolbox
Testing the database layer with DbUnitTesting web applications with HtmlUnit, Canoo WebTest, etc.Using Cactus to test server-side J2EE componentsContinuous performance testing with JUnitPerfAcceptance testing with FitNesseRolling your own integration / acceptance testing harness atop JUnitMaking Testing Part of Your Build Process
Integrating Junit with Antsetting Up A Continuous Integration Environment Using CruiseControlmonitoring The Build and Test Status
