Files
PolyORB/testsuite
Jérôme Hugues 045c91b60b Use helper functions to raise user defined exception,
instead of PolyORB internal functions.

[Imported from Perforce change 9155 at 2006-12-01 21:16:00]

Subversion-branch: /trunk/polyorb
Subversion-revision: 36677
2005-02-25 22:37:09 +00:00
..
2003-11-04 21:48:50 +00:00
2004-05-11 15:38:37 +00:00

README for the PolyORB testsuite
--------------------------------

$Id: //droopi/main/testsuite/README#1 $

This file details the organization of PolyORB's test suite.

* Directory structure

acats/ : source for the Distributed System Annex test suite, from the
        ACATS suite,

corba/ : source for the CORBA test suite,

core/ : source for the PolyORB's core test suite,

scenarios/ : scenarios to be executed when running the test suite,

utils/ : tools used to run the test suite.

* Preparing PolyORB to run the test suite

1/ Build PolyORB

Refer to PolyORB User's Guide for more information.

We suppose you build PolyORB in $build_dir.

2/ Build PolyORB's examples

Go in $build_dir/examples
Run make

3/ Build the test suite

Go in $build_dir/testsuite
Run Make

* Run the test suite

In $buld_dir/testsuite, type 'make run_tests'.

This will launch the test suite. Output is in $build_dir/output.

$build_dir/output/error provides information on any internal error,
$build_dir/output/failed lists failed tests,
$build_dir/output/log provides various information,
$build_dir/output/<scenario_name>/<test> is a trace of the test.