vervuwi
New Contributor
Joined 9 years ago
User Profile
User Widgets
Contributions
Re: Assertion fail for valid HTTP code 204
At least it would be nice if the end-user would have control over this behaviour. Can this option be turned of somewhere so that not all our tests that assert on a 204 fail due to this? In the mean time the dev team can start implementing the fix for no longer sending the 'content-length' header ... I could be mistaken, but it seems that this change is also not included in the release notes for version 1.9 ...5.5KViews0likes2CommentssoapUI JSON Path selector on raw request not working in version 1.8
Hi, While upgrading to from version 1.6 to version 1.8 of ReadyAPI we noticed that there is a bug in the software which causes json path selectors to extract items from the raw request no longer works. An example of this can be found below: ${TestStepName#Request#$.jsonPathSelector} We have also skipped version 1.7 of ReadyAPI due to bugs with the json path selectors, but we would like to have the benefits related to the composite projects in version 1.8. Any idea on when this can be fixed. Please keep in mind that on our build servers we don't like to install nightly builds of the software. Thanks in advance. Kind regards, Wim760Views0likes1CommentDefect: JSON Path Expressions can no longer handle inline data fetches
We have a response from a REST service with the following json structure: {"users": [ { "email": "user1@test.com", "userId": "..." }, { "email": "user2@test.com", "userId": "..." } ]} We also have a test step called 'GenerateData' that has a property that actually contains the email of the user we are currently using in this test. When we try to extract his userId with the following JSON Path Expression we always recieve an empty result. We are 100% positive that the '${GenerateData#userEmail}' contains 'user1@test.com' while our test is executing. $.users[?@.email='${GenerateData#userEmail}'].userId In readyAPI 1.6.0 this feature was still working. However we recently upgraded to release 1.7.0 and we now notice that test cases that make use of this sort of JSONPath Expressions actually fail. Is this a wanted change in version 1.7.0 or a newly introduced bug? In case there are any reasonable work arounds available, feel free to share them. Thanks in advance.1.4KViews0likes4Comments