Think about Loose Coupling | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
I usually put all my cleanup code into an END block within the appropriate test file. That way, even if the test is interrupted/aborted for some reason, the cleanup code usually runs and I leave a clean environment. This becomes a hassle if you set up stuff in one .t file that you depend on in another, but I avoid that (and since you're saying you randomize the execution order of your tests, it seems so do you). If you really want to clean up before your tests run and not after (in which case I'd be interested to know why) you could put it into a BEGIN block of the relevant test. All dogma is stupid. In reply to Re: Executing something before all tests using 'prove -s'
by tirwhan
|
|