-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added testing to the generated OpenAPI. #286
Conversation
API specs implemented for 266/649 (40%) APIs. |
f9f7ce0
to
4ce3af7
Compare
API specs implemented for 266/649 (40%) APIs. |
2 similar comments
API specs implemented for 266/649 (40%) APIs. |
API specs implemented for 266/649 (40%) APIs. |
API specs implemented for 266/649 (40%) APIs. |
API specs implemented for 266/649 (40%) APIs. |
API specs implemented for 266/649 (40%) APIs. |
API specs implemented for 266/649 (40%) APIs. |
1 similar comment
API specs implemented for 266/649 (40%) APIs. |
API specs implemented for 299/649 (46%) APIs. |
API specs implemented for 299/649 (46%) APIs. |
1 similar comment
API specs implemented for 299/649 (46%) APIs. |
API specs implemented for 299/649 (46%) APIs. |
2 similar comments
API specs implemented for 299/649 (46%) APIs. |
API specs implemented for 299/649 (46%) APIs. |
API specs implemented for 299/649 (46%) APIs. |
Signed-off-by: dblock <dblock@amazon.com>
Signed-off-by: dblock <dblock@amazon.com>
Signed-off-by: dblock <dblock@amazon.com>
See apiaryio/dredd#1430 Signed-off-by: dblock <dblock@amazon.com>
Signed-off-by: dblock <dblock@amazon.com>
Signed-off-by: dblock <dblock@amazon.com>
Signed-off-by: dblock <dblock@amazon.com>
Signed-off-by: dblock <dblock@amazon.com>
Signed-off-by: dblock <dblock@amazon.com>
Signed-off-by: dblock <dblock@amazon.com>
Signed-off-by: dblock <dblock@amazon.com>
Signed-off-by: dblock <dblock@amazon.com>
Signed-off-by: dblock <dblock@amazon.com>
Signed-off-by: dblock <dblock@amazon.com>
ee0fcd3
to
c4546f3
Compare
Signed-off-by: dblock <dblock@amazon.com>
Signed-off-by: dblock <dblock@amazon.com>
Signed-off-by: dblock <dblock@amazon.com>
Signed-off-by: dblock <dblock@amazon.com>
@nhtruong I added POST and DELETE specs, which required correcting the response code from POST to be 201, but now the linter complains that the responses for all
Help me correct this the right way? |
We'll need to update the linter to accept a list of exceptions OR update this lint rule to consider 200 and 201 to be exchangeable. We can't get rid of this lint because the client generators expect operations of the same group to share certain properties, and |
You can use |
Closing in favor of #299 |
Description
This adds tests using dredd.
x-tested
. This is a new feature of the merger than can be extended in the future to exclude deprecated APIs, or ones for a specified hosted target (AOS, AOSS, etc.), or version of OpenSearch.Passing spec.
Failing spec:
In order to get
GET /
to pass we needed to supply an example of a response, otherwise dredd thinks thatbuild_flavor
is a required parameter (see apiaryio/dredd#1430).Issues Resolved
Resolves #277
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.