test executor is not aware that test is supposed to be executed only on the client side (currently that's only working when test method or class is marked with @RunAsClient)
therefore it wipes out data provider for parameterized test, assuming this needs to be executed in the container (so it prevents from n^2 test execution described in #17)
If Spock specification has parameterized feature and is supposed to be executed only on the client-side through marking
@Deployment
as non-testable, the test will fail with exception mentioned in https://github.com/arquillian/arquillian-testrunner-spock/issues/26#issuecomment-536157490.Why is that happening
@RunAsClient
)