Contributions
Re: POST request - unable to control encoding
Yes, content type is"application/xml" I have found the solution, it's trivial yet it can give you headaches. Global Preferences >> HTTP Settings >> set "Request compression" to "None". Somehow it was set to "gzip" by default installation, hence the unwanted encoding in my requests.1.5KViews3likes0CommentsPOST request - unable to control encoding
Hi, I have a very basic POST request looking like this: The problem is that I can't seem to controlencoding this data ("12345"). My request will look like this, regardless of any used "Content-Type" header or "Encoding" property. I have compared all settings with another colleague, everything is identical. Yet he gets a clean POST request, while I end up with the above. Tested on SoapUI 5.2.1, 5.1.2 and ReadyAPI 1.9.0 with the same results. Any help is appreciated. Thank you, /AdrianSolved1.6KViews0likes2CommentsForce "Receive MQTT message" test step as always PASSED
Hi, Assume thefollowing basic setup in order to test some MQTT application: I have one publisher (tcp://localhost:8883) and two receivers, respectivelytcp://localhost:1883 andtcp://localhost:1884 When some message is published on a given topic, one of the receivers will get the message. But this is decided by some balancing mechanism, so you never know which one gets it. I have created three test cases which are ran in parallel, i.e. TC1 and TC2 for receivers, TC3 for publisher. Since either one of TC1 or TC2 will fail because it won't retrieve any message, the whole suite will be failed. Is there any way to force these "receive mqtt" to pass, regardless if any message was received or not? Thanks and regards, /Adrian591Views0likes0Comments