Yes, right, concurrency embeds the entire testsuite in a deployment. There is an org.jboss.arquillian.container.test.spi.client.deployment.ApplicationArchiveProcessor interface that one could implement to trim the test archive.
One of the potential problems with just excluding is that entire test archives need to be excluded, as the archive fails deployment. In Concurrency a single test archive contains many tests. This is I guess one disadvantage of not having a separate module/archive per test.
Maybe though with a org.jboss.arquillian.core.spi.LoadableExtension we can first remove the offending EJB bean so that the archive deploys, and then exclude less tests.
We could create a junit5 suite class to exclude the tests that don't apply. I did this for the RESTful tck in the core profile as there were xml binding and security tests that the core profile does not support. Here is the suite class for that:
There were also a few tests for xml binding mixed in with other tests that I did not want to exclude, so I had to add an InvocationInterceptor to filter those out. The class for that is:
I think we need to create a Concurrency TCK challenge for
excluding the tests that require EAR deployment to be solved for
Web Profile. IMO, the challenge could be accepted with the advice
that users can manually exclude (via tck runner configuration) the
tests identified by
https://github.com/eclipse-ee4j/jakartaee-tck/issues/1053 when
running on a EE 10 Web Profile implementation. If that is
acceptable, we could try excluding those tests.
Scott
On 6/27/22 4:58 PM, arjan tijms wrote:
Hi,
Concurrency was recently added to the Web Profile, but it
looks like its TCK is not suitable for the web profile at the
moment.
For instance, a large number of test archives (each
containing a dozen or so of tests) contain remote EJBs. On the
GF web profile distribution this will cause errors such as:
"Caused by: java.lang.RuntimeException: Invalid
application. EJB CounterSingleton exposes a Remote client
view. This feature is not part of the EJB 3.1 Lite API"
Until this is addressed, I think we cannot release the web
profile for EE 10.