[wsf-c-dev] Adding a script to tools to build wsf/c and run the samples

[Rajika Kumarasiri]

hello everybody,
Some time back there was some discussions on the same list, adding a
tester script- a perl script, to do the followings. 
1. Update the working copy of wsf/c (or checkout a new revision)
2. Then build and runs the samples.

This suppose to be a detail description of the task of the script.

In general script can use for two things.
1. In one side it will automate the above process, that is first it will
check out(or update the working copy) and then runs the samples. 
2. On the other hand when a developer adds a new feature to the code
base it will re-build the required parts and re-run the samples to check
weather the added codes make no harm to the code base. 

The script builds axis2/c first and then runs its samples and then goes
to the other modules etc..,
At the end followings will be given to the developer.
# of samples
# of samples pass
# of samples fail - fail samples should contains the more information
about the failure, so that the developer can easily locate the bug and
fix it. 
The script process can run in back ground(with nice) without giving any
burden to the running machine when just building and running samples,
and if we use it as in (2) we need to just to run the script.

Do we need this? Still can we manage with what we have ?

Any comments/thoughts/suggestions ?

-Rajika