Unit test output verbosity

[Krzysieq]

[Note: parts of this message were removed to make it a legal post.]

Hey,

I have a question. I wrote some unit tests for my simple app. Since it's a
part of a larger whole, it's managed inside a continuous integration
framework. For that purpose I would like to report the unit tests that are
executed not only by their overall failure or success, but in more detail.
Is there any way in which I can increase the verbosity of messages sent to
standard output, so that I can see the names of all test case subclasses,
and all test methods, with a distinction whether or not they succeeded? The
best would be to get a junit format of xml report, but I have tools to do
that for me from plain text, so this isn't a big deal. I will appreciate any
insight.

Cheers,
Chris

 

[Kouhei Sutou]

Hi,

In <[email protected]>
"Unit test output verbosity" on Sat, 13 Dec 2008 01:30:39 +0900,

I have a question. I wrote some unit tests for my simple app. Since it's a
part of a larger whole, it's managed inside a continuous integration
framework. For that purpose I would like to report the unit tests that are
executed not only by their overall failure or success, but in more detail.
Is there any way in which I can increase the verbosity of messages sent to
standard output, so that I can see the names of all test case subclasses,
and all test methods, with a distinction whether or not they succeeded? The
best would be to get a junit format of xml report, but I have tools to do
that for me from plain text, so this isn't a big deal. I will appreciate any
insight.

Are you using test-unit? If so, you can use -vv option.

Thanks,

 

[Krzysieq]

[Note: parts of this message were removed to make it a legal post.]

Hi again,

Yes, I'm using Test::Unit, but the -w parameter You mentioned doesn't seem
to have done anything. Any other ideas? Thanks for help anyways.

Cheers,
Chris

 

[Kouhei Sutou]

Hi,

In <[email protected]>
"Re: Unit test output verbosity" on Mon, 15 Dec 2008 18:58:18 +0900,

Yes, I'm using Test::Unit, but the -w parameter You mentioned doesn't seem
to have done anything. Any other ideas? Thanks for help anyways.

No, no, no. Two "v"s ("-vv") not one "w" ("-w").
See --help.


Thanks,