[News.eclipse.test-and-performance] Re: Will this project be geared to s

[Bryan Hunt <bhunt@xxxxxxx>]

Great, here is some more info:

My current preceived problem with Hyades is in the execution model.  It 
appears to me that the current execution model relies on the ability to 
choose the machine(s) on which the test(s) executs, and the requirement 
of running a daemon on the test machine.  This model does not work when 
you have thousands of machines that execute tests 24/7 and must be 
shared with other jobs.

Our existing environment uses a queueing system to dispatch jobs to a 
machine for execution.  The job may be a test, or any other type of task.  
Our system submits tests to this queue for execution 24/7 and results 
are stored in a database.  Our tests are designed to produce stiumuls 
real-time in response to a SUT based on a set of configuration 
parameters.  This allows us to test different functions of a SUT simply 
by running a test multiple times.  Various configuration parameters 
control how tests are submitted to the queue.

Here is a sample use case:

Bring up eclipse.
Query the status of the tests ran / failed in the last 24 hours.
Re-run a failing test with additional parameters to generate additional 
debug information.
Debug test.
Submit all tests with same fail symptom for re-run on new SUT or fixed 
configuration parameters.
Shut down eclipse and go home while tests run.

There's obviously a lot more to our system than I've described above, 
but this will hopefully get a good dialog started.

Bryan

In <cdfo95$78j$1@xxxxxxxxxxx> Tyler Thessin wrote:
> Large-scale testing of software and/or hardware systems is a target of 
> the Test & Performance Project (and the Hyades platform developed 
> therein).  Let us know the specific constraints you have perceived and 
> we can provide more specific insights for applicability to your 
> environment.
>
> --tyler