Test Run Failures

If you receive a failed test run, you can do one of the following:

• Check the response message after a failed test run. The response message is available under the test case node in the Projects window. The response message is time stamped.

  You can verify that the response does not match the expected response (that is, Output.xml) and this might help you understand the problem.

• Check the Server log file after a failed test run.

  To do so, go to the IDE's Runtime tab. Select the View Server Log action on the GlassFish V2 Application Server node.

  This shows the contents of the server log and might contain information about why a test run failed.

One particular case of test run failures is related to tests that use content-based correlation embedded in Input.xml (for example, the Input.xml files in the Travel Reservation Service test cases have <UniqueID>...</UniqueID> as the basis for correlation). In this situation, if you run the test case when there is already a running process instance initiated by the same test case, the second process instance will not be initiated and the test will fail. The following message will appear in the GlassFish V2 Application Server log:

Exception occurred while executing a business process instance.
com.sun.jbi.engine.bpel.core.bpel.exception.CorrelationAlreadyExists: An instance is associated with the correlation
<...>