In Ready API Tool - Not able to Add sections in Request -> Form (Tab)
I have added a new field in the API request but not able to add the new feild details in the Request -> Form (Tab) all the sections are disabled as per the screen shot. Can someone help me on how to add the new section to add the new fields in the Request -> Form (Tab)? Also, in the API request View Type -> All is selected from dropdown but still the data is viewed as clutter sections and feild details not able to see section and fields in the proper form (as per attached screen print) . How to resolve this issue?
SOAP Tests aren't running after updating ReadyAPI
Hey guys, After updating from ReadyAPI 3.43 to 3.49 my SOAP tests no longer work. I was able to narrow down the problem to the outgoing WSS. It looks as if the Basic(Bultin) authentication method requires an outgoing WSS, otherwise ws-security policies do not work. After adding outgoing WSS the tests are working. Attached is the error message: HTTP/1.1 500 500 Date: Thu, 30 Nov 2023 14:05:02 GMT Server: Apache Strict-Transport-Security: max-age=31536000 Content-Type: text/xml;charset=UTF-8 X-Content-Type-Options: nosniff X-Frame-Options: sameorigin Connection: close Transfer-Encoding: chunked <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>These policy alternatives can not be satisfied: {http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}SupportingTokens {http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}UsernameToken {http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}HashPassword</faultstring></soap:Fault></soap:Body></soap:Envelope> Why is it required to add an WSS in this version, when it wasn't necessary in version 3.43? Is there a way to circumvent this WSS requirement?
How to disable "autocorrect/autofill" on SOAP requests
Using ReadyAPI to do a data driven test against a SOAP API. On each iteration, putting XML in the values for a properties test step. This is so that we can have some tests with missing elements, or other structural options. Using a placeholder in the SOAP request to grab those property values (see image). Whenever I save the project, ReadyAPI goes into my request, sees missing elements (because the placeholder puts them there during runtime) and "helps" me by shoving empty element tags in there for schema compliance. Next time I run the test, it fails because of extra tags... I have to remember to go into the request and delete the extra tags. One day I may forget and raise an embarrassing defect. Main Question: Is there a way to disable this "help" that keeps making things more complicated? (please support negative test cases - they're critical for robust testing) Thanks
Invalid User Name and/or Password
Hello After upgrading to 3.47 I was receiving an authorization error message, so I uninstalled 3.47 and went back to 3.44. Now 3.44 is receiving the same error message. So I upgraded to 3.49 and am still seeing the same error. I am just wondering if anyone knows of or has a configuration solution that I can use. I am a functional person running the SOAP UI request to test the response values received. I am logging into Smart Bear as myself and use test users to access the test environment. This was working fine until 3.47 and now it seems 3.44 is now broken and even 3.49. I have no idea of what to look for to figure out what the issue is. Other workmates can access the test environment using the SOAP UI tools they have installed on their laptops and the same test users I am attempting to use. <faultcode>SOAP-ENV:Client.authenticationError</faultcode> <faultstring>invalid username or password</faultstring>
