Re: Continuous testing tools

2006-06-12 Thread David Romano
On 6/9/06, Adam Kennedy <[EMAIL PROTECTED]> wrote: http://ali.as/pita.html The above gave a 404, but http://ali.as/pita/ worked.

Re: Continuous testing tools

2006-06-11 Thread Adam Kennedy
Michael G Schwern wrote: On 6/9/06, A. Pagaltzis <[EMAIL PROTECTED]> wrote: * Adam Kennedy <[EMAIL PROTECTED]> [2006-06-09 18:35]: > Sorry for the lack of information, but PITA's design is fairly > ambitious, Hmm, I just saw this: http://googleresearch.blogspot.com/2006/04/our-conference-on-

Re: Continuous testing tools

2006-06-10 Thread Michael G Schwern
On 6/9/06, A. Pagaltzis <[EMAIL PROTECTED]> wrote: * Adam Kennedy <[EMAIL PROTECTED]> [2006-06-09 18:35]: > Sorry for the lack of information, but PITA's design is fairly > ambitious, Hmm, I just saw this: http://googleresearch.blogspot.com/2006/04/our-conference-on-automated-testing.html Th

Re: Continuous testing tools

2006-06-09 Thread A. Pagaltzis
* Adam Kennedy <[EMAIL PROTECTED]> [2006-06-09 18:35]: > Sorry for the lack of information, but PITA's design is fairly > ambitious, Hmm, I just saw this: http://googleresearch.blogspot.com/2006/04/our-conference-on-automated-testing.html The submission deadline has already passed, but I figure

Re: Continuous testing tools

2006-06-09 Thread Andrew Savige
--- Adam Kennedy wrote: > I know it's somewhat vapour at the moment, and I'm keeping somewhat > quiet, but the new post-Audrey'fied PITA design is aiming at exactly > what you have described. Thanks for the reminder about PITA. I'd (unforgivably) forgotten about that project when I first enquire

Re: Continuous testing tools

2006-06-09 Thread Adam Kennedy
Hi Andrew I know it's somewhat vapour at the moment, and I'm keeping somewhat quiet, but the new post-Audrey'fied PITA design is aiming at exactly what you have described. Initial deployment targets include a pugs smoker, parrot smoker, and CPAN Testers 2. Of course, I have no idea how you

Re: Continuous testing tools

2006-06-09 Thread Adam Kennedy
Sorry for the lack of information, but PITA's design is fairly ambitious, and until the core testing loop is completed, absolutely every other part of it would block waiting for me to finish. So I've kept things mostly under wraps. With the core almost done (we've had to scrap a major componen

Re: Continuous testing tools

2006-06-09 Thread Geoffrey Young
Nik Clayton wrote: > Geoffrey Young wrote: > >>> Since you're using C++, you can probably use libtap >>> (http://www.onlamp.com/pub/a/onlamp/2006/01/19/libtap.html and >>> http://jc.ngo.org.uk/trac-bin/trac.cgi/wiki/LibTap) for writing the >>> tests and >>> then you could use a Perl harnes to coll

Re: Continuous testing tools

2006-06-09 Thread Nik Clayton
Geoffrey Young wrote: Since you're using C++, you can probably use libtap (http://www.onlamp.com/pub/a/onlamp/2006/01/19/libtap.html and http://jc.ngo.org.uk/trac-bin/trac.cgi/wiki/LibTap) for writing the tests and then you could use a Perl harnes to collect those results. just out of curiosity

Re: Continuous testing tools

2006-06-08 Thread Tels
Moin, On Thursday 08 June 2006 18:10, Chris Dolan wrote: > On Jun 8, 2006, at 10:39 AM, Tels wrote: > > On my todo (well, wish list) is still a project that works rouhgly > > like a > > server/client model. > > > > You upload a snapshot to the server, it notifies the clients, they > > download the

Re: Continuous testing tools

2006-06-08 Thread Chris Dolan
On Jun 8, 2006, at 10:39 AM, Tels wrote: On my todo (well, wish list) is still a project that works rouhgly like a server/client model. You upload a snapshot to the server, it notifies the clients, they download the package, run the tests and report the result back. Reports are viewed on t

Re: Continuous testing tools

2006-06-08 Thread Tels
Moin, On Thursday 08 June 2006 15:11, Michael Peters wrote: > Andrew Savige wrote: > > We are looking at introducing continuous builds/smoke tests at > > work across a number of platforms (mainly Windows and Unix), > > building a number of different languages (mainly C++). > > > > I quick google u

Re: Continuous testing tools

2006-06-08 Thread Geoffrey Young
> Since you're using C++, you can probably use libtap > (http://www.onlamp.com/pub/a/onlamp/2006/01/19/libtap.html and > http://jc.ngo.org.uk/trac-bin/trac.cgi/wiki/LibTap) for writing the tests and > then you could use a Perl harnes to collect those results. just out of curiosity, has anyone got

Re: Continuous testing tools

2006-06-08 Thread Michael Peters
Andrew Savige wrote: > We are looking at introducing continuous builds/smoke tests at > work across a number of platforms (mainly Windows and Unix), > building a number of different languages (mainly C++). > > I quick google uncovered the list below. > > Anyone got any advice? I would advise k

Continuous testing tools

2006-06-07 Thread Andrew Savige
We are looking at introducing continuous builds/smoke tests at work across a number of platforms (mainly Windows and Unix), building a number of different languages (mainly C++). I quick google uncovered the list below. Anyone got any advice? Thanks, /-\ Perl * AutoBuild: http://www.auto