<quote who='Fergal Daly' when='Fri, Mar 13, 2009 at 02:13:49PM +0000'> > If I have this straight, the problem is that T::NW's END executes > after the test script's END. This happens because T:NW's END is > compiled before the test script's END. > > You could get around this by having Test:::Most require T::NW in a > CHECK or INIT. This will cause T::NW's END to be compiled after > everything else and so will run before all other END blocks.
Yep, you have it right (and more concise, too :). Thanks for that, Fergal, I'll play around with CHECK and INIT and see how that looks. <quote who='Michael G Schwern' when='Fri, Mar 13, 2009 at 11:06:47PM -0700'> > A stupid work around is to put "use Test::NoWarnings" after your END block. > > Another is to use no_plan in the END block because it doesn't output until > inside Test::Builder's own END block. [snip] > That will work fine, and since Test::Most already loads a bunch of Test > modules one more wouldn't seem to hurt much. > > Need to come up with a better way to deal with end-of-test-process tests. I take it that there isn't a recommended way at this point. I'll see if I can find something that isn't offensive to the sensibilites; maybe I can come up with a better way. Thanks, Schwern. J
