Hi! On Thu, Apr 09, 2009 at 03:22:16PM -0700, Michael G Schwern wrote: > For that reason I believe the idea is fundamentally flawed and a pain > in the ass.
I agree - at least that it's a pain in the ass, but sometime you just have to deal with something that's a pain in the ass and I was looking for advice on the least painfull way :-) > Instead, I put the MakeMaker test module creation code into little test > modules in t/lib. Now each test can just load the appropriate setup module to > create the necessary test files, and throw it out at the end. > > So I'd suggest an approach like that. Keep each test file as a stand alone > unit. Shove common setup/teardown code into a module. I had some setup/teardown stuff in place, and in the end I extended that instead of trying to mess around with some sort of state between testing. It's not complete pain-free, but well.. -- #!/usr/bin/perl http://domm.plix.at for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}
