Make it possible to create different URI's in 1 environment
For each environment (TEST and UAT) we have different URI's for particular API's. This is not convenient as is, to create so much environments for each API. e.g.: environment TEST has an api that is used for - customs https://hbatna80.ad-my.domain/Headbird.Ferry.App.Customs.1.0.1.00.13 webbook https://hbatna80.ad-my.domain/Headbird.Ferry.App.Webbook.2.0.01.06 WebTop https://hbatna80.ad-my.domain/Headbird.Ferry.App.Webtop.1.1.01.15 etc... this means that for each webservice that contains 15 API's it can be that I need different endpoints. At this point (ReadyAPI v3.66.0) you need to declare them all seperately and select them all seperately. That makes a very long Environment list to select from....and this give more chance on mistakes and info losses. Make it possible that each Environment can contain different URI's to select from in the testcase itself please.
Refer to JSON payload in multipart/form-data
I need to test an endpoint accepting multipart/form-data. The endpoint expects a required part with content id "messageToSend" and optional parts with content id's "document[1-x]". The documents are to be file attachments and I want to send the "messageToSend" as a JSON payload. The attachments are working without issue, but using the query parameter value to input my JSON is not great UX. Ideally I would be able to refer to the body below from the query param so the content id is set correctly. You can imagine if the JSON content were much larger it would be painful to use the query parameter as the text box. As you can see in the screenshots above, the JSON payload has the correct Content-Type but no Content-Disposition. Functionally the two parts need to be merged. I either need to be able to: Refer to the JSON from the query parameter where placeholder "REFER_TO_JSON_BODY" (similar to file:fileName). Set the "content id" in the large text box with the rest of the JSON. Kind regards
How do I add a REST query string without the 'name='
Hi, I'm trying to build a REST query, but my issue is that the service I'm calling only requires a value following the '?' and I'm struggling on how to define this. If I blank out the name in the settings, it still generates the '=', so my query string ends up as'?=value', which the service rejects. So, how do I add a query without the 'name=' or '='. Thanks
How to change the API of a REST test step
Hi guys, If you test REST APIs in SoapUI, you may encounter an issue where you cannot change the API attached to the REST test step. I am not aware of any standard way to do it, so I prepared a simple Groovy script to change the test step's API programmatically: testRunner.testCase.getTestStepList().each(){ step = it service = step.getService() log.info("TestStep: ${step.getName()}") config = step.getRequestStepConfig() log.info "Before: ${step.getService()}" config.setService("BankGround_v1.12") log.info "After: ${step.getService()}" } I thought this may help those of you who work with REST APIs, which get changed over time (new versions). For a longer story, you can visit the following article: https://www.linkedin.com/pulse/soapui-what-rest-api-changes-karel-husa-7vb2eSet Authorization Method defaults in Auth Manager which can be inherited by environments
Each of my Ready API projects have dozens of tests and 10+ environments each. The authorization methods for each API request/test is the same across all environments, but any time I need to make changes, or add new requests/tests, I have to open up the environment configuration window. and then for each environment I have to: select the api > Edit > Authorization > Configure > Auth Manager > expand out all of the requests/test steps > make any changes (which is like 3 mouse clicks each plus some scrolling) > close > save And then repeat the exact same steps 10+ more times. Even using inheritance within an environment as much as I can, it's incredibly tedious, and often leads to developers making quick one-off changes in the request/test itself which gets applied inconsistently across environments and then wonder why our automated tests start failing I propose being able to use Auth Manager in the "No Environment" to set the authorization methods in one place, which can then be applied to all environments (unless overridden). Basically, in addition to Inherit From Parent, there could be an Inherit From Default Environment. That way, if an environment will be using all the defaults I only need to touch the environment level auth manager once, set Inherit From Default Environment at the project level for each environment, and then apply that to all dependencies. Any time changes need to be made, I could open up the No Environment Auth Manager, make my changes there, and know it will apply to all all environments inheriting from the default.
