develooper Front page | perl.qa | Postings from January 2005

Re: Test::Unit, ::Class, or ::Inline?

Thread Previous | Thread Next
From:
Tels
Date:
January 27, 2005 08:53
Subject:
Re: Test::Unit, ::Class, or ::Inline?
Message ID:
200501271748.25818@bloodgate.com
-----BEGIN PGP SIGNED MESSAGE-----

Moin,

On Thursday 27 January 2005 00:50, Michael G Schwern wrote:
> On Wed, Jan 26, 2005 at 06:28:20PM -0500, David Golden wrote:
> > But is there any reason they can't be run in the same process?
>
> In general I think its a bad idea for the test and the thing which
> generates its output to be in the same process.  Why?  Because then how
> do you, the user, change the output format?  You have to trust that the
> test author used something that you can pass in arguments or
> environment variables or whatever to be able to spit out the format you
> want.  This is, of course, the problem with any all-in-one system.  The
> various implementations of XUnit, for example, have this problem.  And
> then what happens if Module::Foo is using Foo::Runner that takes its
> arguments in one way and Module::Bar is using Bar::Runner that takes
> its arguments in another way?
>
> The nice part of the "test | parser" model is because there's a common
> format you can stick any parser on the end and generate any output you
> like.  The current trouble is we have only one parser and its not
> terribly flexible.

If I understand the current test model correctly, the seperation also has 
the advantage that if the test dies, the parser is largely unaffected. It 
even tells you *where* it died (e.g. "after test #7"). If you have 
test/parser in one process, a die() might tear it down completely, and 
you get only "test process died" out of it.

Best wishes,

Tels

- -- 
 Signed on Thu Jan 27 17:45:34 2005 with key 0x93B84C15.
 Visit my photo gallery at http://bloodgate.com/photos/
 PGP key on http://bloodgate.com/tels.asc or per email.

 "I am soo clumsy today." *crash*

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iQEVAwUBQfkbWHcLPEOTuEwVAQGraAf8C0Q7fgnpoNQJcIsPAHULf02Pb+NordIL
Io4FDnjIz/ryuecXj067Gz6aTZv3gFMeTWZuqWMqE/FffNSZxHoJ8935yaJCBlv/
+QUA9Q7/3b7Anj7BodlJCvVVotfR1lGD+DlEQLjqrv8C5wd0hMQFnkxws7AFv3tB
mKGGAUyO9ZodscvBj+1l5gBPSWEAMlVYS48cRC/2MAl2xTmv6xfqFHFvaqA9HKTP
qz3OSAdCw2wKOWm/vzs5p/t2vUcaInH1xC5nXfecBqwERTcHROLeMcwc3rDntQgJ
NxgR3/4zCd2y6LN9CHr2vEg/4cImoBXjTU8Fi50SKi2BsP3/rw8nGw==
=I6+J
-----END PGP SIGNATURE-----

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About