With 0.2 release, we have introduced a concept called test api wrapper, which helps to pass specific set of parameters to test apis and avoid duplicating tests api definitions.
This would typically be helpful when the same API definition is expecting a different response/response code based on the context.
When the same API returns a different set of status code, usage of test api wrapper would be apparent.
During generation of the spread sheet, create a test api wrapper instance for each status code that the api supports. For the equivalent entry in the test api definition,
- Parameterize the response status.
- Parameterize the expected response body.
- Pass both from the respective test_api wrapper entry with the values from the OAS (Open API Spec)
With 0.2 release, we have introduced a concept called test api wrapper, which helps to pass specific set of parameters to test apis and avoid duplicating tests api definitions.
This would typically be helpful when the same API definition is expecting a different response/response code based on the context.
When the same API returns a different set of status code, usage of test api wrapper would be apparent.
During generation of the spread sheet, create a test api wrapper instance for each status code that the api supports. For the equivalent entry in the test api definition,