Re: Descriptive strings?
On Wed, Jun 20, 2001 at 02:38:14PM -0400, Kirrily Robert wrote: > On Tue, Jun 19, 2001 at 08:42:29PM -0400, Michael G Schwern wrote: > | > | I assume you're talking about "make test"? Test::Harness in > | non-verbose mode (ie. "make test") won't display any of that info. If > | you set $verbose = 1 you'll see all the test output. For failed tests > | it will just report their numbers. > > Where do I set $verbose? make test TEST_VERBOSE=1 -- Paul Johnson - [EMAIL PROTECTED] http://www.pjcj.net
Re: Descriptive strings?
On Tue, Jun 19, 2001 at 08:42:29PM -0400, Michael G Schwern wrote: | | I assume you're talking about "make test"? Test::Harness in | non-verbose mode (ie. "make test") won't display any of that info. If | you set $verbose = 1 you'll see all the test output. For failed tests | it will just report their numbers. Where do I set $verbose? | Currently, Test::Harness is not aware of test names at all. It just | ignores the extra info. I'm not sure what I'm going to do about that. | As sort of a simple, half-ass solution I'm going to have Test::Harness | dump its verbose output to a file (test.out?) by default. Hrm. What I want is to achieve this: # This produces "ok 1 - Hell not yet frozen over" (or not ok) ok( get_temperature($hell) > 0, 'Hell not yet frozen over' ); (from the Test::Simple perldoc) when I run "make test". K.
Re: Descriptive strings?
On Mon, Jun 18, 2001 at 04:54:05PM -0400, Kirrily Robert wrote: > The above is generated using Pod::Tests and pod2test (yay schwern!). > When I run these tests, I never see the descriptions of the tests (eg > "Strings aren't blank"). > > I thought those strings were meant to output during the testing, to show > you what it's testing for. Am I confused? I assume you're talking about "make test"? Test::Harness in non-verbose mode (ie. "make test") won't display any of that info. If you set $verbose = 1 you'll see all the test output. For failed tests it will just report their numbers. Currently, Test::Harness is not aware of test names at all. It just ignores the extra info. I'm not sure what I'm going to do about that. As sort of a simple, half-ass solution I'm going to have Test::Harness dump its verbose output to a file (test.out?) by default. -- Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/ Perl6 Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One My breasts are arousing weapons.