fabiobrz / eap-microprofile-test-suite Goto Github PK

See https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/quarkus-dev/QZgqrblsYEc/sgDcnHYlBAAJ

Maybe the bootable container adapter can be added just to the belonging profile?

Paul Ferraro showed me he is not reproducing the issue, so it needs to be investigated why it pops up in our TS.

Need to verify what at https://download.eclipse.org/microprofile/microprofile-open-api-1.1.2/microprofile-openapi-spec.html#_microprofile_rest_client

• Check diffs in release notes
• Check diffs in PR
• Check diffs AD (including previous ones)

TD - Sketch MP OpenAPI test application to demonstrate tests as per TP:

• look at forks
• MP OpenAPI specs (again)
• other MP specs
• experiments with Quarkus, Thorntail, OpenLiberty etc.
• look at Google Group + Zulip for new ideas (e.g.: see JWT + OpenAPI example at https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/quarkus-dev/QZgqrblsYEc/sgDcnHYlBAAJ)
• identify concrete test opportunity points for tests as per TP and summarize making relation with TP sections clear.

See https://javaee.github.io/tutorial/jaxrs-advanced004.html

• Use basic project used to manually test the feature and incorporate it into TS.
• Send PR

The endpoint should be exposed via HTTP per specs but Wildfly will allow access via HTTPS transport in case such a listener is configured.

Tests to verify that the /openapi endpoint will be available in such case and to evaluate WARNs.

• Check TCK and MP Samples

Pre-checks must be done ASAP to comply with TP

Current TD status with respect to requirements in TP is missing some tests that have yet to be developed, here's a list of the missing cases:

Integration testing

1. MP specs

• MP Config: MP OpenAPI annotations sources and MP OpenAPI extended properties effect on multiple deployment environment (e.g. WARNs)

2. Customer/advanced/negative scenarios

• one test on JWT related Security annotations, see https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/quarkus-dev/QZgqrblsYEc/sgDcnHYlBAAJ (should this one be added to TP - Integration testing?)

• mixed approach to OpenAPI document model generation (e.g.: static file + programming model + annotations)

• Negative scenario about headers, see #1 (comment)

• multiple and subsequent deployments/undeployments

• WARN for missing HTTP listener

Security testing

• The endpoint should be exposed via HTTP per specs but Wildfly will allow access via HTTPS transport in case such a listener is configured.

• Tests to verify that the /openapi endpoint will be available in such case and to evaluate WARNs.

Also misc tests

• Performance: time to boot/deploy, memory/disk pressure with hundreds of annotated endpoints

OBSOLETE (see new checklist #11 (comment)): Plan

• define how to perform manual checks on missing items (MP config first)
• start with manual checks on missing items
• OBSOLETE (see new checklist #11 (comment)): check WARNINGs not logged by SmallRye? File a JIRA for not logging unwanted/misplaced properties like in JWT sample?
• OBSOLETE (see new checklist #11 (comment)): execute the TS for the MP OpenAPI spec
• execute Wildfly TS MP OpenAPI integration tests
• execute manual experiments (try generate and use clients too, i.e. swagger editor)
• provide current status to DEV - i.e.

• TP/TD ratio
• enlist missing scenarios and that those are covered manually
• status/outcome of tests (both manual and automated)

• update document at https://docs.google.com/document/d/1DRo5RIT-E7g-GuRztB_7r5hTDc89e0-sEdTh8kW28UU/edit
• update JIRA

Roadmap/ETA

• This is top priority so all automated and manual pre-checks must be executed today/tomorrow morning
• Report must be given within tomorrow EOB

There's an error without any code in server.log

Evaluate architecture/implementation strategy for final solution with two potential approaches:

• 1 app, to serve as a back-end to simulate customer scenarios and to let the tests for all sections of TP to be run against

• n mini apps to serve things as integration tests but 1 app for complex scenarios

OpenAPI doc seems to be there, no good. Verify and issue.

• mixed approach to OpenAPI document model generation (e.g.: static file + programming model + annotations)

• Negative scenario about headers, see #1 (comment)

• multiple and subsequent deployments/undeployments

• WARN for missing HTTP listener

• one test on JWT related Security annotations, see https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/quarkus-dev/QZgqrblsYEc/sgDcnHYlBAAJ

Once architecture/implementation strategy is defined, then re-check with updated TP (integrations do "move" a bit - e..g: JWT + OpenAPI? Tests failed by management TS?)

• Code refactoring/cleaning and uniforming with current MP OpenAPI tets codebase style
• Java doc
• Extract test opportunities to satisfy TP requirements: RHOAR QE migration + customer scenario APP
• Design application first stub
• Review test classes/methods
• Map test criteria with TPG tags
• Send PR

This test can be used for memory evaluation after multiple subsequent deployments/undeployments.
Possibly document criteria and the file the PR for the proposal using already implemented local branch.