I assume it's splitting
a test suite into "Batches"
targeted for separate machines,
so they just run faster?
Is continuous testing feasible for
what you want...meaning you update
some code and half a second
or less later
all the tests have been applied?
Personally for continuous testing
I need the the continuous tester
to be smart enough to figure
out which tests are relevant, otherwise
I'm going to need a lot of machines :-)
Alex Karasulu wrote:
Hey that would be way cool. If you want to approach them on it to get
this pie in the sky dream o mine
than man please go for it.
Regards,
Alex
On 5/29/07, * Ole Ersoy* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
BTW - Cédric Beust (TestNG), David Saff (MIT guy that that's working on
the continuous stuff, Agitar like stuff, etc), etc. and so on
all hang out on the JUnit list and they are very friendly.
Could be that they might be interested in helping tackle continuous
distributed testing with ApacheDS as a "Study".
I need to get more into it myself. As soon as I get the DAS
done, I'm reinstalling Fedora again. I'm running FC6_64 now
with the Sun 1.6.0 JDK and Eclipse crashes every hour,
so I think if I try to run continuous testing in the background
it would probably be every minute. A continuous testing grid
would be sweet though. Put the kid's computer to use...maybe the
neighbor's...
Alex Karasulu wrote:
> This is cool. What I want is one that can use more machines on my
> network to run these heavy tests.
>
> Alex
>
> On 5/29/07, *Ole Ersoy* < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
> <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> wrote:
>
> This looks interesting:
>
> http://pag.csail.mit.edu/continuoustesting/
>
> I think I'm going to try
> it on the DAS since I'm refactoring every 30 seconds now.
>
> Cheers,
> - Ole
>
>
