detvetdu
Occasional Contributor
Joined 9 years ago
User Profile
User Widgets
Contributions
Re: Assertion fail for valid HTTP code 204
If you add extra check in the assertion for http codes you add assertions for standard as well. Shouldn't that be an assertion for the header is following the http standard? I agree that http 204 should not contain content length header. But the assertions for valid http codes do to much check with this new feature.5.5KViews0likes0CommentsAssertion fail for valid HTTP code 204
In earlier versions than 1.9 of ReadyApi the assertion for HTTP 204 worked fine. In this version I get failed assertion for HTTP code 204 when i response header returns "Content-Length: 0" with error message: "Wrong server response: responses with the 204 status code must not contain the "Content-Length" header." I can't find anything on https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html that supports that Content-lenghth header is not allowed. Is there any reason why this assertions behavior have changed? I tested in version 1.8.5 and there it works fineSolved5.7KViews0likes7CommentsCan not open teststep when using environments
When i use default envionment i can run the testcase and open all teststeps. When i set a environment first teststep fails and it is not possible to open the teststep for editing. If i open the teststep while in default environment and then switch to a different environment nothing happens when I press run testcase. This do only apply for one testsuite/testcase in the project. What is the problem? I run readyApi 1.6827Views0likes1Comment