I'm new to Maven, but can't find an resolution to this problem: unit
tests don't run with enough verbosity to be useful. When I run unit
tests that fail, there is nothing reported other than that the tests
failed. For example:
[junit] Running com.foo.FooTest
[junit] Tests run: 4, Failures: 0, Errors: 4, Time elapsed: 1.875 sec
[junit] [ERROR] TEST com.foo.FooTest FAILED
If I want to see the reason the test failed I have to generate the
site and then look at the HTML output, which takes a lot longer, but
does provide the full reason for failure:
Error creating bean with name 'com.foo.FooTest' defined in null:
Unsatisfied dependency expressed through bean property 'fooManager':
There are 2 beans of type [class com.foo.FooTest] for autowire by
type. There should have been 1 to be able to autowire property
'productManager' of bean 'com.foo.FooTest'.
Is there a way to get the failure reason on the command line?
In a separate problem, when I run test:ui it appears to have a
different classpath than when running test. Is there a way to make
sure these are the same? When running the Swing test runner from Maven
I get classpath-related errors in my unit tests that don't appear when
I run the console tests.
Thanks
Dan Bradley
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
