Obviously there is a problem here the sessionid will be different each time around which will fail the assertion, let's use the wildcard feature to work around this Ībove we have selected the 'Allow Wildcards' option and replaced the sessionid value with a '*' which will result in SoapUI ignoring the sessionid value when asserting the result. If the value doesn't match, the assertion fails. Next step is to specify the XPath expression that selects the loginResponse element Įntering this expression into the top edit field and the pressing 'Select from current' in the toolbar below gives us the following:Īs you can see, the 'Select from current' action applied the XPath expression to the underlying response message and shows the result in the 'Expected Result' field this is now the value that SoapUI will compare against each time a new response is received and the assertion is executed. The dialog is divided into two areas: the top specifies the XPath expression to apply and the bottom the Expected Result. Start by selecting the 'Add Assertion' button in the Assertion Toolbar and selecting the 'XPath Match' assertion in the prompting dialog:Īfter pressing OK, the following (empty) configuration dialog is opened: Let's jump right in, here is a login response message that we want to validate īasically we want to check for the loginResponse and sessionid elements in the SOAP Body, but ignore the actual value of the sessionid since it will change between each request. If the values match the assertion passes, otherwise it fails. The XPath assertion applies a specified XPath expression to the received message and validates the resulting nodes against an expected value. Check out their website to get details on supported standards, reference documentation, etc. Quick Tip: Both the XPath and XQuery Match assertions make use of the Saxon XPath / XQuery processor which supports most of the latest standards in this area. Let's have a look at each together with some examples!

This also makes way for two of the most powerful assertions, XPath Match and XQuery Match, which both utilize the named technologies to provide fine-grained message validation possibilities. All messages received by sampler TestSteps are internally converted to an XML counterpart, which provides a common ground for assertions and other post-processing.

Check xml tool