Using the BPEL Designer and Service Engine

Looking at Test Case Results

The first time you run your test, the results correctly report that it has failed. This happens because the output produced does not match the (empty) Output.xml file, and the file?s null content is replaced with the output of the first run. If you run the test again without changing the input, the second and subsequent runs report success, since the output matches the contents of Output.xml.

Test results are displayed in the Output window. Detailed results are also displayed in the JUnit Test Results window, which opens automatically when you run a test case. If you change the value in the Input.xml and re-run the test:

If you right-click the test case node and click Diff in the pop-up menu, the window displays the difference between the latest output and the contents of Output.xml.