Forum Discussion

yakari's avatar
yakari
New Contributor
9 years ago

XPATH assertion fails with SoapUI NG

Hi together,   I want to migrate our projects from SoapUI Pro 5.1.2 to SoapUI NG. Within SoapUI NG the following XPATH assertion fails, which passes within 5.1.2.   As result of a REST request I ...
  • PJat's avatar
    PJat
    9 years ago

    It's because of a bug fix in Ready! API to be able to match mutliple values returned by an XPath. As you can see your XPath expression returns multiple values but expected value is only one. Please change the XPath expression to : //codeCategories[1]//codeCategory[2] or change the expected value to [A,B,C].

  • PJat's avatar
    PJat
    9 years ago

    Yes, you can use wildcards - so expected value in your case can be '*B*'.

     

    nmrao We should definitely include it in SoapUI OS - I will bring this up with MattiH (SoapUI OS Product Owner).

yakari's avatar
yakari
New Contributor

Hi,

 

thanks for the answer. But that does not really solve the problem. The results differ each time and could be [C,A,B] and the next time [B,C,A]. So how should the assertion then be? Is there a possibility to sort the results before the assertion or use wildcards?

 

Thanks

yakari

PJat's avatar
PJat
Contributor
9 years ago

Yes, you can use wildcards - so expected value in your case can be '*B*'.

 

nmrao We should definitely include it in SoapUI OS - I will bring this up with MattiH (SoapUI OS Product Owner).