[Tsp-devel] TSP auto-tests

[Eric Noulard]

Hi All,

Some of may have catch (and may be read) some message
about a TSP sub-project call DTest.

The initial idea which motivate DTest was to be able
to write "portable" GoNoGo test for TSP.

DTest is already able to do such task.
I did check-in the first example on how to use DTest
in order to design (and run) TSP autotest

Please have a look to:
http://cvs.savannah.nongnu.org/viewvc/tsp/tests/auto/tsp_stub_and_stdout_test.py?root=tsp&view=markup

If you want to take the fast path in order "test" DTest usage for TSP

1) checkout dtest somewhere
    cd /where/you/want
    cvs -z3 -d:pserver:address@hidden:/sources/tsp
co dtest

2) checkout tsp somewhere
    cd /where/you/want
    cvs -z3 -d:pserver:address@hidden:/sources/tsp co dtest

3) imagine you have compiled version
    tsp_stub_server and tsp_stdout

4) update PYTHONPATH for dtest
    export PYTHONPATH=/where/you/want/dtest

4) launch the TSP dtest script like this
    /where/you/want/tsp/tests/auto/tsp_stub_and_stdout_test.py
--provider=<user>@<host>:/path/to/tsp_stub_server
address@hidden:/path/to/tsp_stdout

You should obtain something like:
## Test Sequence <TSP Stub Server/Stdout Test> ...
## Number of DTesters = 2
##   Description:
##   This TSP test sequence launch  a stubbed server and an stdout client
1..7
ok 1 - TSP Stub and Stdout Starts
ok 2 - Barrier <provider started> crossed by all <2> registered DTester(s)
ok 3 - First stdout run (no args)
ok 4 - Second stdout run (-n 150)
ok 5 - Barrier <consumer ended> crossed by all <2> registered DTester(s)
ok 6 - TSP Stub and Stdout Ends
ok 7 - No Tester did timeout.
## Test Sequence <TSP Stub Server/Stdout Test>: PASSED.

Volunteer wanted for writing a bunch of dtest TSP autotest.


-- 
Erk