axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davanum Srinivas" <>
Subject Dealing with failure in an junit testcase under modules/integration
Date Wed, 02 May 2007 01:41:58 GMT

Here's the write up i promised.

Scenario: you made changes in kernel and running the m1 build and see
a failure in ServiceGroupContextTest. Here's what you do next.

Step #1: Edit under modules/integration and add
remote debug options to the maven.junit.jvmargs. Here's what i
typically use

-Xdebug -Xnoagent -Djava.compiler=NONE

Step #2: Rename maven.xml to say maven.bak. So that the boat load of
setup stuff don't run. This may not work under some circumstances.
Under those, try commenting our all the wsdl2java related ant snippets
to save time. I've occasionaly changed the name attribute of the
preGoal/postGoal elements to something non-sensical so that they don't
kick in. Basically we trying to reduce the time taken to run a test by
removing stuff that does not need to be run each time.

Step #3: Run a single maven test. See example below. You really don't
need to be on-line, so throw in the offline switch as well.

maven -o -Dtestcase=org.apache.axis2.engineServiceGroupContextTest test

If you see Step #1, we are asking the jvm to wait till the IDE
connects on port 5006. So maven now should stop at the point where you
need to connect to it from an IDE.

Step #4: Connect from your favorite IDE to the port you specified in Step #1.

That's it..


Davanum Srinivas ::

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message