Whoops.  Forgot to send this back to the list.

--- Ovid <[EMAIL PROTECTED]> wrote:

> Date: Thu, 4 Jan 2007 02:52:38 -0800 (PST)
> From: Ovid <[EMAIL PROTECTED]>
> Subject: Re: "Really" Test Anything
> To: Adrian Howard <[EMAIL PROTECTED]>
> 
> --- Adrian Howard <[EMAIL PROTECTED]> wrote:
> 
> > I have nothing useful to contribute - but I just feel the need to
> say
> > huzzah and thank you for TAPx::Parser. Looks jolly fun for the next
>  
> > time I need to fiddle with TAP!
> 
> Thank you.  You can also read http://use.perl.org/~Ovid/journal/32063
> for more details of my thoughts of working with the --exec switch.
> 
> Also, I've already been contacted by someone working on a project
> with
> tests written in multiple languages and they need my code to already
> be
> written, so I'm going to try to get it out the door as soon as I can.
>  
> > Oh - actually - I have thought of something :-)
> > 
> > Something that I've wanted in the past is a way to merge TAP
> streams 
> > together. So I could take these:
> > 
> > 1..2
> > ok 1 - foo the first
> > ok 2 - foo the second
> > 
> > 1..2
> > ok 1 - bar the first
> > ok 2 - bar the second
> > 
> > and produce something like
> > 
> > 1..4
> > ok 1 - foo the first
> > ok 2 - bar the first
> > ok 3 - bar the second
> > ok 4 - foo the second
> > 
> > The reason I wanted it was so that I could merge the results of
> tests
>  
> > I was running on a distributed set of machines (for purposes of  
> > speed) together and present the results as soon as they were ready.
>  
> > In the end I ended up hacking something together that merged whole 
> 
> > test runs, rather than individual tests because that was easy(ier)
> 
> One feature of 'runtests' which is already implemented is to be able
> to
> specify a different test harness, so you could do:
> 
>   runtests --harness TAPx::Harness::MergeStreams \
>            --exec 'run_distributed_tests' < list_of_servers.txt
> 
> And with something like that, you could then have a text file with
> the
> servers you want to run tests on, a program called
> 'run_distributed_tests' which would know how to run the tests on each
> server and TAPx::Harness::MergeStreams would just have to know how to
> merge the test streams.  It's a bit of work, but I don't think it
> would
> be too hard.  I just need to finish the --exec functionality and get
> my
> current harness to mimic the output of Test::Harness as much as is
> feasible.
> 
> Cheers,
> Ovid
> 
> --
> 
> Buy the book -- http://www.oreilly.com/catalog/perlhks/
> Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/
> 


--

Buy the book -- http://www.oreilly.com/catalog/perlhks/
Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Reply via email to