RE: Discussion Topic #3 Distributed Testing

I'm interested in the Junit component. Depending on the deadlines I can take one feature, eg starting with making reports human readable. Though if you need it very shortly it's better that someone else does it instead.

Doing research on distributed testing is my goal but I dedicate the coming months to hands-on work to know what I'm talking about.

They are coordinating a project at CERN that will provide grid developpers with infrastructure and software to run builds and tests on whatever machine they want (they have many available OS and compilers) and using any version of grid middleware your job depends on. You'll give  your configuration descriptions in your favorite language and the job will be sent to a target chosen by the system in that it is idle and corresponds to your specs.
The project is called ETICS and uses notably "NMI build and test framework" based on Condor.
Here is the problem: you send your job to a single machine and you don't easily have a handle to the machine nor can control the lifecycle. Basically you just pin a build so that it stays otherwise you loose it once done. So it's not made for distributed testing. However they are interested in it and I'm working on how SmartFrog could help. For testing, the Junit component may be the key but they're not focusing only on Java. For the builds, the sfOpenlabTools will certainly be useful.
Here is the ETICS homepage, still very light: http://etics.web.cern.ch/etics/

Xavier


-----Original Message-----
From: Xavier Grehant [mailto:[email protected]]
Sent: Tue 1/24/2006 11:00 AM
To: Xavier Grehant
Subject: [Smartfrog-developer] Discussion Topic #3 Distributed Testing
 
On 1/19/06, Steve Loughran <[email protected]> wrote:
>
> And the final discussion topic is distributed testing: Where are we at,
> what do we need?
>
> 1. We have the non-distributed sf junit suite,
>
> 2. we have the arithmetic testharness to test that sf and those
> components distribute possibly.
>
> 3. There is a junit component that can deploy junit tests to remote
> nodes and then collect the results on a designated reporting node. There
> is nothing yet to make collected XML reports human readable, and there
> is no collection of events from multiple machines into a single test run.
>
> SmartFrog itself needs better distributed testing, so that we can deploy
> on different machines, collect the results, etc.
>
> We also think that distributed testing is itself an interesting research
> project, especially across grids of systems. The mygrid people run
> gridunit on many nodes because running (local) junit tests across a
> variety of machines is a great way of finding problems.
>
> I'm interested in distributed junit testing of the cddlm soap API, so
> that I can deploy a server on one node and run tests from another. I
> think the base components to do that are there, its just the reporting
> and IDE/ant integration to deal with, and the time needed to sit down
> and do it.
>
> What other needs do people have, and who else is interested in getting
> involved in this interesting research problem?
>
> -steve
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Smartfrog-developer mailing list
> Smartfrog-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/smartfrog-developer
>










-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642