Dheepha
12 years agoContributor
MavenSOAPUIPro plugin not support wildcard * in Xquerymatch
Hi,
I'm using maven soapui pro plugin 4.5.1 to run the soapui automation test.
Upon executing , the maven soapui pro plugin gives error when the Xquerymatch assertion contains wildcard as '*'.
It treats '*' as a value and compare the actual result against this.
For Eg:
<ServerDate>2013-09-12 00:00:00</ServerDate> is a tag in the response xml and it will change on each run.
So we use xquery match assertion to save the response xml and check the allow wild card option and porvide * in the ServerDate tag in the expected response. i,e <ServerDate>*</ServerDate> and save it.
On next run, it should verify whether the tag is present in response and not the value as we have put it as wildcard.
This works fine in soapui 4.0.0/soapui 4.0.1 version and also in maven soapui plugin 4.0.0/4.0.1
But this feature is not working in maven soapui pro plugin 4.5.1 / maven soapui plugin 4.5.1
Hope this is an open issue in the maven soapui pro plugin.
Anyone from the soapui team can you please look into this and fix this , as this will solve many of our issues.
Thanks in advance.
I'm using maven soapui pro plugin 4.5.1 to run the soapui automation test.
Upon executing , the maven soapui pro plugin gives error when the Xquerymatch assertion contains wildcard as '*'.
It treats '*' as a value and compare the actual result against this.
For Eg:
<ServerDate>2013-09-12 00:00:00</ServerDate> is a tag in the response xml and it will change on each run.
So we use xquery match assertion to save the response xml and check the allow wild card option and porvide * in the ServerDate tag in the expected response. i,e <ServerDate>*</ServerDate> and save it.
On next run, it should verify whether the tag is present in response and not the value as we have put it as wildcard.
This works fine in soapui 4.0.0/soapui 4.0.1 version and also in maven soapui plugin 4.0.0/4.0.1
But this feature is not working in maven soapui pro plugin 4.5.1 / maven soapui plugin 4.5.1
Hope this is an open issue in the maven soapui pro plugin.
Anyone from the soapui team can you please look into this and fix this , as this will solve many of our issues.
Thanks in advance.