ReadyApi JSONPath match assertion with Wildcard
Hi I am using ReadyAPI 3.6.0 and a bit new on it 🙂 In some test steps, i like to use wild card in Jsonpath Match Assertion for content , but i don't know How to define wildcard ? Let me share a simple example: I have some REST endpoints with Json format to test, so in Teststep , I expect some response error messages start with "BAD_REQUEST::VALUE_FORMAT" followed by the name of the key in this case i think i have two option : 1- Use wild card like this "BAD_REQUEST::VALUE_FORMAT * " and it means that all similar messages end with * (key name) would be PASS/accepted 2- Define OR with various messages that i expect to see like BAD_REQUEST::VALUE_FORMAT-Key1 ORBAD_REQUEST::VALUE_FORMAT-Key2 ...... Actually i cant manage to define none of them ... in this case would you please help me on it ?Solved1.9KViews0likes3CommentsReadyAPI/functional test assertion don't works after awhile!
Hi I am using ReadyAPI 3.5.1 I have already defined some test suite and test cases to meet my requirements for test and controlling my API functionality , and it worked fine so i save it and in every new version of my production i try to use already save test cases. But funny thing happen! I have some simple Assertions in my test cases to control the error messages i expect. For example i am going to control error message "KEY_UNRECOGNIZED" , so i had defined an Assertion for response match content and it used to works! but when i try to run the test and control it again after a week , i see that these assertion do not correctly recognize the response error message ! (attached screen capture of it ) So as you can see i supposed to look for "KEY_UNRECOGNIZED" and in response it has "KEY_UNRECOGNIZED" and in my case it matched so it supposed to PASS , but i show FAIL ?! please note that this test step used to works fine while ago and i have done no change to it ...but it don't works correct now ?Solved1.6KViews0likes3Comments