The Fastest Way To Discover APIs Documented Using The OpenAPI Specification
While organizations around the world are setting their roadmaps for the new year, our ReadyAPI engineering and product team has been hard at work on ReadyAPI 2.6 to bring you new capabilities and improvements that will help start 2019 off right.
For the new year, we have a few initiatives of our own on the ReadyAPI team, and one of them is to continue to seamlessly insert ourselves into the DevOps toolchain. In ReadyAPI 2.6, you’ll see improvements made to our Git integration, Postman Integration, and a new integration with SwaggerHub On-Prem - making sure that ReadyAPI is apart of your entire API Lifecycle. Another initiative is to simplify and augment, so we continue to invest in our API Discovery recorder. Teams can now discover, filter, and create tests against their OAS endpoints to help increase test coverage without bogging down their CI/CD process.
OAS API Discovery
One of the hidden gems of ReadyAPI for non-technical testers is the API Discovery Recorder. As teams move to DevOps and replace manual API testing or UI testing for API testing, there is perhaps no better bridge than the API Discovery Recorder, and we’ve made it even easier to use and smarter.
The API Discovery Recorder records HTTP/S traffic and API transactions from a live workflow using our built-in browser or a proxy. After the workflow is completed, users can filter and create test cases based on real data captured from these transactions.
With the new update in ReadyAPI 2.6, a user can upload a specific OpenAPI Specification before they start their workflow, and any API traffic matching the OAS file will be automatically filtered out, simplifying the discovery of APIs that are actually used and allowing testers to validate them even faster.
If you are looking to increase your API test coverage and get a general sense of what APIs are actually being used, this is exactly what you've been loking for.
As organizations shift-left and dabble with moving testing responsibilities towards engineering, they have the advantage of leveraging technology traditionally used only by engineers. One of those is Git, the version control system that has taken over the world of software and sprouted a distributed-development revolution. In ReadyAPI 2.6, we’ve added Git-native versioning, so you can push, pull, and commit just like you would in Git and a Git console that you can call right from the ReadyAPI interface.
Also in ReadyAPI 2.6 is new support for Postman version 2.0 and 2.1 and improvements to the overall integration, like importing Postman Collections via local file as well as a URL.
You can now easily import API definitions located on SwaggerHub On-Premise servers and publish APIs from ReadyAPI to SwaggerHub On-Premise instances.
Now you can run multiple virtual services on the same port. The only requirement is that they use different paths in URLs.Introducing ReadyAPI 2.6