MobicentsQA < Communications < TWiki

TWiki . Communications . MobicentsQA

Mobicents Quality Assurance

The Mobicents project has coninuously running build and test systems to ensure its robustness and standards compliance.

Continuous Builds

After each CVS check-in, the build system automatically rebuilds the full source tree to ensure source code integrity. The latest reports can be found on the designated mailing list: https://mobicents.dev.java.net/servlets/SummarizeList?listName=cruisecontrol&by=date

Nightly runs of SLEE TCK (Technology Compatibility Kit)

To ensure full compliance with JSLEE on continuous basis, each day the latest source tree (CVS HEAD) is automatically checked out and tested against the TCK. This procedure is executed on multiple platforms:

If you would like to add another platform to the list and have the resources to maintain it, send a message to the Mobicents Contributors Forum

How To Setup Continuous Builds?

The continuous build and test run are based on a Cruise Control script. It can be found in the Mobicents CVS repository under /scripts/.

The CC file is named

config.xml
. It uses the ant script build-mobicents24.xml and the modified server startup script run-cc.sh.

Nightly run of JUnit Test Suite

This is a pending task. Post on the forums if you are interested to help with it.

Build Result Archives

Results from each continuous build are sent to a designated mailing list, which is regularly archived.

How To Run the TCK

See the instructions here: MobicentsQuickStartGuide#Run_the_TCK

Performance Testing and Benchmarking

How to Write Custom Tests

To add new tests that cover features not covered by the TCK follow this tutorial: Writing Custom Tests

-- Main.ivelin - 08 May 2005

----- Revision r16 - 20 Jun 2006 - 22:46:37 - Main.ivelin