Forum Discussion

KRR's avatar
KRR
New Contributor
8 years ago

Assert not equals a specific value

I have a web service that I am creating a test suite for in Soap UI Pro (Ready API 2.0). I need to add an assertion that a particular field does NOT return the value 1.0 but I can't figure out how to...
  • groovyguy's avatar
    groovyguy
    8 years ago

    So if you use an XPATH assertion, you'd end up with an xpath statement that ends up like:

     

    //ns1:myWebServce/return/factor

     

    in the top part of the assertion and 

     

    1.00000605897785

     

    in the bottom pane, saying that this is the expected value.

     

    You can change your XPATH statement to  

     

    //ns1:myWebServce/return/factor = 1.0

    and have your expected value be

     

    false
groovyguy's avatar
groovyguy
Community Hero

So if you use an XPATH assertion, you'd end up with an xpath statement that ends up like:

 

//ns1:myWebServce/return/factor

 

in the top part of the assertion and 

 

1.00000605897785

 

in the bottom pane, saying that this is the expected value.

 

You can change your XPATH statement to  

 

//ns1:myWebServce/return/factor = 1.0

and have your expected value be

 

false
KRR's avatar
KRR
New Contributor
8 years ago

That worked perfectly, thanks. I didn't know an XPATH match could be used that way.

  • KRR's avatar
    KRR
    New Contributor
    8 years ago

    I'l look into that to understand Groovy better in the future!

    • groovyguy's avatar
      groovyguy
      Community Hero
      8 years ago

      XPATH can be very powerful. But groovy tends to be easier for more complex situations. If it gets outside of equals or does not equal, I tend to use groovy. Especially if there are multiple objects to be checked in a response.