Cory Horner ha scritto:
> Martin Desruisseaux wrote:
>> Just realized that Maven documentation said "just print the test cases that has
>> errors", but in practice Maven doesn't prints any test at all, even in case in
>> Will wait in the hope that this is a Maven bug to be fixed in the future, unless
>> peoples wish to roll back this change. In the main time, it is always possible
>> to check in the target/surefire-test directory in the usual way.
> Hi Martin,
> I like the change, but would like to easily be able to set a flag to
> have full output (-Dtests.verbose=true). Right now the build boxes tell
> us that the build is broken, but not which test failed. I also cannot
> figure out which test failed from the command line (but i agree this is
> a great improvement, if only this bug were fixed).
But it's not, and if a module has lots of tests (like the Metadata
module that is failing now) it's hard to spot what's happening
by inspection of each single surefire report.
Re-enabling summary I get:
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.015
sec <<< FAILURE!