-
Notifications
You must be signed in to change notification settings - Fork 81
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
TCK tests for openapi endpoint #69
Comments
|
We'll want to write assertions which cover each of the annotations. I've copied the checklist below. Annotation list:
|
Going to start with the Info, Contact and License annotations. |
I am covering Component, Tag, Tags and Header. |
Starting with Schema |
doing
|
I'm covering the following annotations:
|
I'll do SecurityScheme and SecurityRequirement |
thanks everyone. I updated the checkboxes based on the comments. |
I'm now working on Operation, APIResponse and APIResponses. |
I'm working on Link, Encoding |
updated checkboxes |
I'll handle Extension, Extensions, Example Object |
updated |
Also doing OAuthFlow, OAuthFlows, OAuthScope, as these relate to SecurityScheme (confirmed this with Jana @janamanoharan). Note: SecurityRequirements is covered in petStore app, so I will write test for it there. |
I am working on Content |
I am working on DiscriminatorMapping |
All done - thanks everyone! |
* Added a unit test for simple jax-rs processing. Specifically added a test for eclipse#28 * Upgraded to MP+OAI 1.1. Fixed some deprecation warnings. * Updates to smallrye due to change in MP+OAI v1.1 * Upgraded to version 1.1.1 of the MP+OAI spec. Signed-off-by: Eric Wittmann <eric.wittmann@gmail.com> * Replaced tabs with spaces
We will be using the
/openapi
endpoint for most of our TCK tests already, but this issue will track the inclusion of specific endpoint tests that will use differentAccept
headers for json and yaml.The text was updated successfully, but these errors were encountered: