KarelHusa
Super Contributor
Joined 9 years ago
User Profile
User Widgets
Contributions
Re: OpenAPI/Swagger 3.0 Support
Importing OpenAPI definitions with refs works fine, at least for many API definitions I have imported. You must ensure all the referenced objects are in your file. I have prepared a brief article on how to import the OpenAPI definitions: https://www.linkedin.com/pulse/soapui-hack-openapi-3-karel-husa-9dsxf/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-7vb2eRe: Import from SoapUI (Open Source) to ReadyAPI
ColinM, it's probably a ReadyAPI bug. ReadyAPI should import a SoapUI project seamlessly unless you have a specific plugin installed which would introduce a new Test Step, unknown to ReadyAPI. If you haven't used specific tests steps from 3rd party plugins for your SoapUI project, you need to raise a support ticket for ReadyAPI.Re: How do you reuse your ReadyAPI Groovy scripts if you want to run tests in a pipeline?
Cleo-Juniper, if your external Groovy/Java code needs to be shared amongst all tests, you can place it in a separate Git repo. At your local computer, checkout the repo and configure your ReadyAPI to point into that directory. In the pipeline, you need to setup ReadyAPI. Checkout of the shared code repo would be part of this ReadyAPI setup (probably as a ready-made container). So in each test pipeline you won't need to do extra work.Re: OpenAPI v3.0.1 support in SoapUI open source?
plsnrk, loucast0159, an update to SoapUI support for OpenAPI 3. Recently, I tried to import an OpenAPI 3 definition as YAML in SoapUI 5.7.1 and suprisingly, the API has been created in SoapUI project. Though the dialogue offers JSON media type, you can use it to import the YAML file, see screenshot bellow. When I tried to import the same definition as JSON, it failed. In the past I did multiple tests to import OpenAPI 3 definitions into SoapUI with negative results and assume that still may be cases where the import will fail. However, at least for simpler OpenAPI 3 definitions, this works. I have summarized this in a brief article.
