in reply to Test output: Interpret or pass/fail

In general, you should only test code that's worth something to you. If you don't care whether some code breaks, don't test it. Similarly, if you don't care about the results, don't automate them.

I personally don't understand why you'd go to the trouble of writing tests if you're not going to look at the results, but some people are funny that way.

(As a side note, if you wrote your tests with Test::More, you could automate them through Test::Harness like the CPAN module does. (Appealing to authority, I wrote some of those tests.)

  • Comment on Re: Test output: Interpret or pass/fail

Replies are listed 'Best First'.
Re^2: Test output: Interpret or pass/fail
by adrianh (Chancellor) on Aug 07, 2003 at 06:50 UTC
    Similarly, if you don't care about the results, don't automate them.

    I wouldn't go quite that far myself. There can be times when writing one-off tests can be very useful - e.g. Exploratory Testing (pdf).

    However, in the context of unit and customer tests I agree completely.