ReadyAPI just got a brand-new update for 2019, and it is BIG. We've added a ton of enhancements to the ReadyAPI tools in 2.7 and even added support for one of the most popular technologies in software today: GraphQL. So, let's get started and talk about the big things you'll get with an upgrade to ReadyAPI 2.7:
- Intelligent Assertion Creation
- OpenAPI Spec Test Coverage
- Support for GraphQL
- Zephyr Integration
Intelligent Assertion Creation
With the addition of ReadyAPI's Smart Assertion feature, users can automatically create test assertions and validations based on the response given from an API. Developers and QA Engineers today spend precious amounts of time creating basic assertions against their APIs to validate foundational functionality - if responses exist, if they contain static response like Status OK, etc.
Using Machine Learning, if you "hit" an endpoint 3 times and it returns the same data all three times, we'll create assertions against the entire response, cutting down hours of test creation time. If that response is dynamic each time the API is "hit", then we'll create an assertion that is flexible and won't fail each time the value changes.
OpenAPI Spec Test Coverage
Test coverage has been a hot topic in the world of Continous Testing and DevOps. Teams want to measure there testing effectiveness and measure over time if their test coverage is generally increasing or not. For RESTful APIs, test coverage has been difficult to assess. But the OpenAPI Spec has changed that.
When a user imports their OpenAPI/Swagger definition, we can now measure how much of it is covered with a test suit or a ReadyAPI project. So if there are 10 different endpoints with 5 parameters each (50 total "objects"), we can tell the user how many have a test case built for it. This should really help QA teams pinpoint poorly tested functionality.
GraphQL is a new paradigm in API development. It is a Querying Language that allows developers to efficiently query data from multiple different sources and APIs. Like REST, SOAP, and JMS - it has its own response format, which we now support for exploring and testing the GraphQL responses. We wrote a whole post about GraphQL and our continuing plans, so check it out.