I hope you guys can help me here. I’m not sure if I’m missing something or it’s a Postman bug:
As you can see in the screenshot, JSON response shows a validation error because some of the required fields are missing from the body. However, my test is still passing, even tho there are no “name”, “logline” or “userdId” properties in the json response. It should have failed at the very first step because jsonData.name would be “undefined”.
Notes:
So far, it seems like Postman is skipping pm.test() and marking it as Passed if the response is some kind of validation error. So it doesn’t matter what the assertion is, it will always pass.
Hi @danny-dainton, Thank for the reply.
I’ve added Pre-request script as well as the Postman version.
The pre-request script works fine and I can see those variables in my Environment variables.
I’ve changed the test to check “jsonData.nnnnn” property, which is non-existing and it’s still passing.
I did add a status check and that’s the only test that is failing now (as it should).
What ridiculous is that even “pm.expect(44444).to.eql(55555);” is passing.
I have tried to duplicate and recreate it. it’s actually reproducible with other PUT requests as well. Considering that I have just found a typo in one of my other assertions, and it was still passing, I assume that this issue has been happening for a while
Postman fails to update to 7.8.0: “Something went wrong while trying to update your app. Check the DevTools for more details.”. When I’m trying to download it manually, it only gives me 7.3.4 build. (I’m on Mac)
I’ll try to do some more testing around to get more data and try to narrow it down.