Clever Geek Handbook

SoapUI Testrunner gives error in TestAssertionRegistry

I can successfully run my test case with valid assertions, but when run through testrunner, it starts with these errors -

ERROR [TestAssertionRegistry] Missing assertion for type [JsonPath Match]
ERROR [TestAssertionRegistry] Missing assertion for type [JsonPath Match]
ERROR [TestAssertionRegistry] Missing assertion for type [JsonPath Match]
ERROR [TestAssertionRegistry] Missing assertion for type [JsonPath Match]

Where do these errors come from? I turned off all my test steps to no avail. It looks like it exits the project level by looking at the xml. I am trying to figure out where it was generated from.

Any help would be appreciated.

+3


source to share


2 answers


JsonPath Match is a feature in version 5.2.x of SoapUI. You are trying to open a 4.x project and the project files are not compatible.

I faced the same problem as you: how to remove all of them. This is how I faked them:



  • Open *-soapui-project.xml

    in a text editor.
  • Replace all occurrences type="JsonPath Match"

    for type="XPath Match" disabled="true"

    . Spaces and double quotes are relevant!

Not really, but it works. Also, if you want to go back, just undo the replacement.

+2


source


As a follow up, if someone is using the pro api and has a pro client that has a project configured and still gets this error, you can do this to get your assertion to work through the java api:

//register the json path content assertion before the project loads
TestAssertionRegistry.getInstance().addAssertion(new JsonPathContentAssertion.Factory());

//loads the project, test suites, etc.
WsdlProjectPro project = new WsdlProjectPro(projectPath);


I'm not sure if this is a bug, or if I am using the API incorrectly, but it does not appear that the pro claims are loaded into this registry along with the free version claims.

+1


source






More articles:


All Articles