JUnit Integration - Workflow Integration

• the latest version of i-net Doqua
  • rename the file com.inet.doqua_X.X.X.jar to com.inet.doqua.jar
• a version of JTidy (jtidy.jar): http://jtidy.sourceforge.net/

Creating an i-net Doqua Test Suite for an existing Eclipse Java project is simple.

• add the two libraries com.inet.doqua.jar and jtidy.jar to your Java Build Path Libraries
• create a new launcher configuration
  • open the Run Configurations… menu
  • select the group JUnit and click on New launch configuration
    • a new JUnit launcher will be created
  • In the Test tab:
    • select your project via Browse… in the Run a single test section
    • insert com.inet.doqua.DokuTool as Test class
  • Switch to the Arguments tab
    • add the following line into the VM arguments textbox

      -Dtest.globalfile=${workspace_loc:%PROJECT%}/.doqua/global.xml
      -Dtest.projectfile=${workspace_loc:%PROJECT%}/.doqua/project.xml

      and change the paramter %PROJECT% to your project name

  • Click Apply and Run to start the test.

Here at i-net software, we use Hudson to continously build and test our software throughout each development phase, making it easy to react quickly to any problems which may arise. Together with i-net Doqua, we use Hudson to continously test our documentation and to plan review cycles.

Hudson is an automated building and testing system. It monitors the execution of repeated jobs, showing their success and error states.

You can easily integrate i-net Doqua with Hudson by creating a new Hudson job calling a special build script. See an example build script.

In addition to the prequisites above you will need to:

• download a version of JUnit (junit.jar): http://junit.org
• add a script such as this one to your documentation project
  • modify the library path in the sample script to your needs