Compare the actual and expected service result without any filter.

Ignore the namespace prefix from the service results.

For example, for a field value demotest:employee in the actual result, where demotest is the namespace prefix, Unit Test Framework ignores the namespace and uses employee for comparison.

Specify which fields in the service result should be compared.

You have to provide a field alias for the field in the actual result that you want to Unit Test Framework to compare against in the expected output.

For example, for a field value demotest:employee in the actual result, you can assign a 1002 as the field alias. Then, Unit Test Framework uses 1002 instead of demotest:employee for comparison.

Specify a custom comparator for expected output other than provided with the plug-in.

Overrides the default comparator in webMethods Test Suite with an Integration Server service that has a custom assertion logic.

Select an Integration Server service that implements the custom assertion logic for an output comparison. The service signature must conform to the wm.spec:result_comparator specification in the WmServiceMock package. You can import the specification directly into the service or replicate it manually in the Integration Server service. For more information on the specification, see WmServiceMock specification.

Implement the custom service to suit your testing requirements. If you select a custom service as the comparator, the outcome of the comparison between the actual and expected test results is determined by the assertion logic in the custom service chosen.

The custom service supports only the "file" type selected in the Expected Output section for comparison. However, providing a file is optional. If no file is selected, the comparator service receives "null" data for comparison.