Chapter 2. Modules

Chapter 2. Modules
Prev	Part I. FitNesse Integration	Next

Table of Contents

2.1. Directory Structure
2.2. Main Modules
2.3. Support Modules
2.4. TestApp Module

Abstract

This chapter describes the modules that make up Tested Objects' FitNesse integration.

The modules that make up Tested Objects' FitNesse integration follow the general conventions of sister projects, with a main module, a support module and a testapp module. You can read more about this in the Star Objects developer guide. However, the directory structure this does not quite follow the standard layout for sister projects: the main and support modules are nested under trunk/fitnesse/ (as opposed to directly under trunk/). That's because Tested Objects may be extended to support other testing frameworks (eg Concordion) in the future.

2.1. Directory Structure

The source code directory structure for Tested Objects is as follows:

trunk/
  fitnesse/           # FitNesse support
    main/               # main release for FitNesse, including Maven site
      fixtures/           # the FIT fixtures that integrate NO with FitNesse
      documentation/      # this documentation
    support/            # support - built after main release
      release/            # defines dependencies for projects using the 'fixtures' module
      archetype/          # archetype
    testapp/            # application for testing - not released
tags/
  fitnesse/main       # tags for trunk/fitnesse/main
  fitnesse/support    # tags for trunk/fitnesse/support

Note that this directory structure is nested under trunk/fitnesse/ (as opposed to directly under trunk/). As is usual, though, to ensure that tags go into the correct location when releasing, the mvn-release-plugin plugin has been configured (using <tagBase>) to override its default location.

You can checkout the entire trunk using Subversion:

svn co https://testedobjects.svn.sourceforge.net/svnroot/testedobjects/trunk ~/testedobjects/trunk