I have seen this behavior (what Kim described), most of the time it hangs and sometimes it will fail. If we can move all the integration type of tests outside the code base then we want have this problem.
This sort of inconsistent behavior has forced me to skip the tests using - Dmaven.test.skip most of the time which is not a good practice. Can we have only unit tests as part of the main build, and perhapse a different goal (or phase if thats the right terminology) to run the integration tests. For unit tests it's illegal by definition to make connections (in VM or otherwise), to have threads blocking for messages/requests/reponses or chain tests together etc. If we need to test connections or request/response scenario as part of the main build then lets use mock objects (EasyMock or whatever) and lets move the other stuff to systests. Also, Steve can we use a code coverage tool with maven ? I suspect that we have very little unit test coverage and more integration type of tests. Regards, Rajith On 12/8/06, Steve Vinoski <[EMAIL PROTECTED]> wrote:
On Dec 8, 2006, at 7:49 AM, Kim van der Riet wrote: > On Fri, 2006-12-08 at 00:45 -0500, Steve Vinoski wrote: >>> When it works, I get the normal test passed message. When it hangs >>> I get (always the same message): >>> >>> <snip> >>> Running org.apache.qpid.test.unit.client.forwardall.CombinedTest >>> Starting 2 services... >>> Starting client... >>> Received 1 of 2 responses. >>> <hang> >> >> I personally have never seen this problem. Why not try jacking up the >> verbosity of the test output to see if you can narrow down where it's >> hanging? > How is this done? I looked at the command line options with mvn -- > help; > there is no verbose option. Neither is there a man page. A quick scan > through the on-line docs did not reveal anything about verbosity... > (although it was a very quick scan!) Is this done through editing the > settings.xml file, perhaps? Hi Kim, Unfortunately the log4j logging level was hard-coded in the client pom.xml. If you svn update that pom, you can now run mvn -Dtest=CombinedTest -Damqj.logging.level=debug test to get full debug output. --steve
