Message Content Assertion: Assertion is looking for null fields even though it worked previously
When I run my call I get the following JSON object: { "data": { "id": 159, "zoneName": "NameofZone", "createdAt": "2019-09-11 19:25:31", "updatedAt": "2019-09-11 19:25:31", "groupsId": null }, "status": "success", "code": "200", "message": "Operation success", "version": "2" } I setup a Content Assertion on the response to validate that the fields exist: I can run this call any number of times back to back and the message content assertion will always pass. However, when I run the entire Test Suite and the same step is run the message content assertion will always fail. It will give an error as if it were trying to find null nodes in the response (shown below) Any idea or insight into why this is happening? Is there any way to prevent this? Currently I am removing the contract assertion from the test case but that kind of defeats the purpose of the test.
