Contributions
Re: Re: User-Agent issue with SoapUI NG (trial)
Found a possible reason. On my case, the remote server is responding a 302 redirection to https. On logs, I see the headers sent on the first request to http but not on the https. Seems SoapUI is forgotting the headers after a 302.1.4KViews0likes0CommentsRe: clone teststep with Valid HTTP Status Codes assertions
Yes I can still reproduce the same. You can also by commenting file reading and defining theslaScript andgzipScript to "" As I tried SoapUI NG, I checked if it has the same behavior. It is not, seems a bug corrected in the commercial part...1.7KViews0likes0CommentsRe: clone teststep with Valid HTTP Status Codes assertions
Seems linked to my creation script: I have a swagger which is still mooving :( As I can't update the swagger in SoapUI, I chose create a groovy script which will create the tests from any swagger. In my script, I clone a teststep which has theValid HTTP Status Codes assertion. In the resulting teststep, the assertion has empty codes. Il after the creation, I try to clone the same step manually, I have the same results. Then I tried to do some other tries on this clonig bug. After that (don't know yet what changed), the bug is not there anymore! Tried restart SoapUI, no change. To reproduce the bug, I deleted the testsuite and recreated it from my script. Then the bug is there. I join the script I use (not finished yet;) ) To run the script, I simply create a testsuite, testcase and copy it in a script teststep1.7KViews0likes2Commentsclone teststep with Valid HTTP Status Codes assertions
Hello, when I clone a teststep with assertions, I have the assertions cloned as well (as expected). But when I look at the"Valid HTTP Status Codes" assertion, the value were not cloned. It is empty! Same behavior when using groovy script or direct UI. I use the latests stable version : SoapUI 5.2.1 Is this a bug? Thanks -- Pascal Greliche1.7KViews0likes4Comments