Implement advanced scenarios tests

[fabiobrz]

• 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

[fabiobrz]

• WARN for missing HTTP listener

Done, see security testing

Next Steps

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

• multiple and subsequent deployments/undeployments

• WARN for missing HTTP listener

[fabiobrz]

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

TBD PR to be sent once rebased after the last one (https://github.com/jboss-eap-qe/eap-microprofile-test-suite/pull/124) is merged. And there seems to be issues with single elements inside the SecuritySchema

UPDATE 20200102 11:30 There are actually no issue with security annotations with respect to experiments with Swagger Editor: OAS 3 spec define that some elements are REQUIRED only depending to the schema used, so the warnings were apropriate. Question now is: is SmallRye implementation emitting validation WARNINGS? Probably NOT as MP OpenAPI spec does not require vendors to implement model validation, see https://download.eclipse.org/microprofile/microprofile-open-api-1.1/microprofile-openapi-spec.html#_validation

[fabiobrz]

Done, PR sent, see https://github.com/jboss-eap-qe/eap-microprofile-test-suite/pull/127

[fabiobrz]

multiple and subsequent deployments/undeployments - left this aside and will file a proposal for memory pressure test, see https://github.com/fabiobrz/eap-microprofile-test-suite/issues/18