Beefy Boxes and Bandwidth Generously Provided by pair Networks
Just another Perl shrine

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

by Mr. Muskrat (Canon)
on Aug 19, 2004 at 15:50 UTC ( [id://384338]=note: print w/replies, xml ) Need Help??

in reply to Re: How to test less with Test::More?
in thread How to test less with Test::More?

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.)
  • Comment on Re^2: How to test less with Test::More?

Replies are listed 'Best First'.
Re^3: How to test less with Test::More?
by eserte (Deacon) on Aug 19, 2004 at 17:05 UTC
    Too complicated. I need this feature only for quick'n'dirty debugging.
      Too complicated? Then you have too many tests in one file and it's time to split them up into separate test scripts.
        The main problem (in my particular case) is that single test cases are slow (taking up to one or two seconds on my slow machine). Splitting the test file into smaller chunks (How many tests per file? 30? 20? 10?) would still leave me the problem that it could take 10 seconds or more to actually run the faulty test --- to long for development.

        And for the "too complicated" argument: the failure of a test is a unusual thing, and normally only I will see the failure and very probably it's also just me who will debug and handle the error. A solution which works for me is absolutely OK. I don't need a "nice" solution, just a working solution.

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://384338]
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others browsing the Monastery: (5)
As of 2024-04-24 20:00 GMT
Find Nodes?
    Voting Booth?

    No recent polls found