On 2010.04.16 03:36, Philip Potter wrote: > On 16 April 2010 02:05, Steve Bertrand <st...@ibctech.ca> wrote: >> On 2010.04.15 18:50, Steve Bertrand wrote:
>> What I've done to 'rectify' the issue so that it is clear that the >> config files differ, is rename the test to the highest test number >> (999-upgrade.t) so it will run last, and we will run "make test" with >> the TEST_VERBOSE=1 flag. >> >> So instead of this: >> >> acct-dev: ISP % sudo make test > > no need for sudo here. You only need it for "make install" (and not > even then if you're using local::lib). The installed config file is readable only by root at this point, so sudo is how I'm getting around that for now. >> .... I'm still reading through the docs, but if someone has any quick >> advice on how to make this more granular so I don't have to be extremely >> verbose on all tests, that'd be great. > > I'm not entirely sure what you're asking, but if you *only* want to > run your new test and you want to get verbose output from it, try: > > perl Makefile.PL > make > prove -bv t/22-upgrade.t I use prove often, usually when I want to quickly and non-verbosely (-Q) work with a single test file that I'm currently adding new tests to, or to ensure existing tests still pass if making changes to a function. What I want to be able to do, essentially, is allow Perl code to run within small sections of tests while under "make test". In essence, some pseudo code that I'd put into 999-update.t: #test55 perl on print result to STDOUT perl off # back to no printing Another way I'm going to try today, is put the code from the test file into the Makefile.PL directly, so that when 'perl Makefile.PL' is called, the checks will be done then, and I should get my desired output. Steve -- To unsubscribe, e-mail: beginners-unsubscr...@perl.org For additional commands, e-mail: beginners-h...@perl.org http://learn.perl.org/
