Hosted on SourceForge



About
Overview
Features
Install
CVS
Mailing Lists


Manual
Files organisation
Compiling
Testing
Documenting
Going on inline


Documentation
Java classes
Stylesheets


  Testing
> Testing


Unit tests

You can run the unit testing with

./build.sh test

You should put your testing code source in the test/src directory. Functional testing master class is AllJUnitTests.java

Refer to JUnit documentation at http://junit.org/ for more information about how to write testing code.


Functional tests

First off all you have to compile and launch the Tomcat server

Then you can run the functional testing with:

./build.sh ftest

You should put your testing code source in the test/src directory. Functional testing master class is AllHTTPUnitTests.java

Refer to HTTPUnit documentation at http://httpunit.sourceforge.net/ for more information about how to write testing code.


Continuous integration

a continuous integration process is a fully automated and reproducible build, including testing, that runs many times a day. This allows each developer to integrate daily thus reducing integration problems.

For setting up a continuous build process with Cruise Control, follow this steps

Dedicate a machine for this task

Check-out your project files from CVS

Edit the cruisecontrol.properties and set the properties to match your project's needs

Install the web interface

./build.sh installcc

run Tomcat

Edit web.xml file under tomcat/webapps/chellobuild/WEB-INF/ and change logDir and xslFile properties according your configuration.

The first time you launch the process do:

./build.sh ccfirst

Then you will have to launch

./build.sh cc

You can access the web interface using http://localhost:8080/chellobuild/chello




Chello Documentation