Re: How to test less with Test::More?

This is an archived low-energy page for bots and other anonmyous visitors. Please sign up if you are a human and want to interact.

You can do the following:

Just define a goto label just before the test you want to run

Add option handling to your test script, e.g.

use Getopt::Long;
GetOptions("fast" => \$do_fast_test) or die;
[download]

After test initialization code, add

goto FAST_TEST_LABEL if $do_fast_test
[download]

And call the test with perl -Mblib t/testfile.t -fast

If you have planned the number of tests, then you will get an error that too less tests were run (of course), but you can just ignore this or use no_plan.

Comment on Re: How to test less with Test::More? Select or Download Code

Replies are listed 'Best First'.
Re^2: How to test less with Test::More? by Mr. Muskrat (Canon) on Aug 19, 2004 at 11:50 UTC
I think that it would make more sense to use a lookup table. Then the test script could execute all tests in a predefined order by default but allow the use of a command line option to run a specific test or set of tests. (And it wouldn't have to use a BASIC-style `goto`.)	[reply]
Re^3: How to test less with Test::More? by eserte (Deacon) on Aug 19, 2004 at 13:05 UTC
Too complicated. I need this feature only for quick'n'dirty debugging.	[reply]
Re^4: How to test less with Test::More? by Mr. Muskrat (Canon) on Aug 19, 2004 at 13:54 UTC
Too complicated? Then you have too many tests in one file and it's time to split them up into separate test scripts.	[reply]
Re^5: How to test less with Test::More? by eserte (Deacon) on Aug 24, 2004 at 13:04 UTC

• hippo

‥ epoptai's answer Re: how do I set a cookie and redirect was blessed by hippo!

• erzuuli

‥ Anonymous Monks are no longer allowed to use Super Search, due to an excessive use of this resource by robots.


We don't bite newbies here... much
	PerlMonks