Ready! API Plugin for importing Swagger definitions as REST Services
Java Groovy
Clone or download
antone-sb Merge pull request #62 from SmartBear/RIA-4304_Support_OAS_3.0_in_a_p…

RIA-4304 support OAS 3.0 in a plug in
Latest commit 324a135 May 23, 2018

ReadyAPI Swagger Plugin

Provider the following swagger-related features in ReadyAPI:

  • Possibility to create projects, Virts and REST APIs from an existing swagger definition
  • Possibility to export a swagger definition for any REST API defined in ReadyAPI
  • Automatically generates a swagger 2.0 definition for REST Virts - available at <Virt endpoint>/api-docs.json
  • Supports both Swagger 1.X and 2.0 for imports and exports

Download and install via the Plugin Manager / Repository Browser from inside ReadyAPI. Older versions are available for SoapUI open-source as well (see below)

Build with

mvn clean install assembly:single

Release History

  • Mar 2017 - Version 2.5.3 - Updated swagger-parser dependency, included required snakeyaml and fixed asserting of XML responses
  • Feb 2017 - Version 2.5.2 - Updated core Swagger dependencies, sample response creation and host handling
  • Sept 2016 - Version 2.5.1 - Fixed autodetection of Swagger 1.X files and added Testcase generation from Swagger
  • July 2016 - Version 2.4.0 - Bug fixes for R!A 1.8.0 release bundling
  • June 2016 - Version 2.3.1 - Dependency updates for improved message creation
  • Feb 2016 - Version 2.3.0 - Creates sample messages for POST/PUT requests / responses, dependency updates, bugfixes
  • March 2015 - Version 2.1 - Bug-fix release which ties into the updated plugin system in Ready! API and adds dynamic swagger generation for REST Virts
  • September 2014 - Version 2.0 - Initial release for Ready! API with Swagger 2.0 support

The latest above version is available from inside the ReadyAPI Plugin Manager.

Previous releases were on sourceforge (and are still available there)

Download old versions from sourceforge:

Please post issues here at GitHub - you can find me on twitter at @olensmar

Thanks for any feedback!