mirror of
https://github.com/AdaCore/PolyORB.git
synced 2026-02-12 13:01:15 -08:00
729b5be5f4
The purpose of this allow us to keep the Python-2.x version of this testsuite while we work on the next version of the testsuite framework, to be implemented using Python 3.x. no-precommit-check: The script has style violations that are not worth fixing, since we'll eventually abandon it. TN: U922-064 Change-Id: I8cdee8309ecfec770ddaa99e74dc5f720b609795
README for the PolyORB testsuite
--------------------------------
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
$ make examples
3/ Build the test suite
$ make testsuite
Note: some tests are not built by default: they require the
installation of third-party middleware, and adaptation of the
makefiles. See corba/interop/cpp/README and corba/interop/java/README
for more details.
* Run the test suite
Note: GNATPython is required to run the testsuite. To install it, run:
svn checkout svn://scm.forge.open-do.org/scmrepos/svn/gnatpython/trunk gnatpython
export PYTHONPATH=/path/to/gnatpython
$ make run_tests
or
$ ./testsuite -j N --diff
All results are stored in the 'out' directory by default and log in the 'log'
directory.
To run only the corba tests:
./testsuite.py -j N --diff corba
To run the all_exceptions corba tests
./testsuite.py -j N --diff corba/all_exceptions/
And to run a specific test CORBA_ALL_EXCEPTIONS_0
./testsuite.py -j N --diff corba/all_exceptions/CORBA_ALL_EXCEPTIONS_0
A report is created in out/report.
See ./testsuite.py -h for more help
4/ Discriminants
The following discriminants are available:
1- for each app perso there is corresponding app_<name>
2- for each protocol perso there is a corresponding proto_<name>
3- for each services available there is a corresponding serv_<name>
4- if SSL is supported, the discriminant 'ssl_support' is set