Forum Discussion

Dheepha's avatar
Dheepha
Contributor
12 years ago

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.

8 Replies

  • nmrao's avatar
    nmrao
    Community Hero
    Have you tried in soapui 4.5.1 version? what is the result?
  • Do you want me to use maven soapui pro plugin version 4.5.0?
  • redfish4ktc2's avatar
    redfish4ktc2
    Super Contributor
    yes, give it a try to be sure on which version the problem has been introduced
    if this version is bugged, you will have to use the previous version of the plugin (4.0.x) if possible
  • I used soapui pro 4.0.1 , and i was getting some digital signed signer error.
    Later i found a solution that is copy paste the following dependency in the pom.xml. And place the soapui 4.0.1.0 jar and its pom in the
    .m2\repository\eviware\soapui location also in the \.m2\repository\eviware\soapui\4.0.1.0 location.

    <dependency>
    <groupId>eviware</groupId>
    <artifactId>soapui</artifactId>
    <version>4.0.1.0</version>
    </dependency>

    Its working.

    I have not tried in the 4.5.0 version. Any idea that even 4.5.0 version also digitally signed?
  • Yes the reference from your post only Thanks.

    OK, I'll give a try in 4.5.0 also and I'll update the forum.
  • I had executed in 4.5.0 version and seems to be working fine.
    Thanks.

    But still just a doubt, whether any build fix has come for the 4.5.1 or higher version to use the Xquery match with wild characters?

    Regards,
    Dheepha B