Forum Discussion

Occasional Contributor

9 years ago

Message Content Assertion - Node Missing

I am using a Message Content Assertion to verify data returned in a response against a data source. Some of the elements that are returned aren't compulsory and are not always populated, e.g. <tn...

SmartBearAmber

Alumni

9 years ago

Unfortunately, if you assert on an element in the request, that element is mandatory. I would suggest using an Assertion Test Step instead of asserting at the request level. For more information, see this document.

hadmatsingh

Occasional Visitor

9 years ago

I came across similar problem of Node missing under message content assertion. I didn't find a solution in documentation which tells about asserting null value,

Forum Discussion

Message Content Assertion - Node Missing

Recent Discussions

Importing project from old ready api version to new 5.7.1

Getting error “this.wss container is null “when started using new ready api 5.7

Problem with ${#Project#Token} and Environments

Related Content

Transform "Message Content Assertions" to "Smart Assertions"

Message Content Assertion: Assertion is looking for null fields even though it worked previously

Ready API-Soup UI Pro-Message Content Assertion failed