I came across an issue when trying to run the TCK using the new arquillian REST 3.0 protocol (which uses a jax-rs resource instead of a servlet to communicate between the client and server).
This extra rest resource is put into every test deployment which means it's in the application and gets scanned and added to the /openapi endpoint, which breaks some of the tests because there are unexpected entries in the openapi document.
The fix is to mark the deployment as not "testable" (which means there aren't any tests which will run within the deployment) so that arquillian doesn't include the extra REST resource in the application.
This should be changed for all of our deployments apart from ModelConstructionTest and OASFactoryErrorTest
I came across an issue when trying to run the TCK using the new arquillian REST 3.0 protocol (which uses a jax-rs resource instead of a servlet to communicate between the client and server).
This extra rest resource is put into every test deployment which means it's in the application and gets scanned and added to the
/openapiendpoint, which breaks some of the tests because there are unexpected entries in the openapi document.The fix is to mark the deployment as not "testable" (which means there aren't any tests which will run within the deployment) so that arquillian doesn't include the extra REST resource in the application.
This should be changed for all of our deployments apart from
ModelConstructionTestandOASFactoryErrorTest