DownLoad

To practise XP successfully you need repeatable tests. When we say repeatable, we mean the computer should be doing them! (They're very pedantic, and make good testers)

• Java
  • JUnit
    • We use JUnit for testing our Java code, we have a separate package for all our tests. This means that if you do want to rumage around in internal state e.g. when low level unit testing package scoping rules may not allow you to do this. In this case we make an object in the package being tested, and call it something like "OnlyForTesting?", and use this to broker calls from the testing package to package scope methods. There is an idea to use Java2's method signing functionality to allow test packages to see the internals of a class, it's doesn't seem like a compelling reason to move to Java2, especially in the light of [Wiki.DoTheSimplestThingThatCouldPossiblyWork]
    • c2.com/cgi/wiki?JavaUnit
    • www.XProgramming.com and navigate through "Software" to find the latest version of JUnit. They'll be moving from armaties to XProgramming soon. --rj
    • JesTer MutationTestingTools and CodeCoverageTools
  • BigBenTools
    • Tools to help you optimise your use of VisualAge, JUnitCreator helps you quickly create JUnit test fixtures.