Wrong isInstance check prevents usage of new/custom container -------------------------------------------------------------- Key: ARQ-1658 URL: https://issues.jboss.org/browse/ARQ-1658 Project: Arquillian Issue Type: Bug Components: Extension - Droidium Affects Versions: droidium_1.0.0.Alpha4 Reporter: Thorben Janssen Fix For: droidium_1.0.0.Alpha6 If the container configuration contains an unknown qualifier, MultipleContainerRegistryCreator tries to the adapterImplClass class and checks if it implements DeploableContainer. The current check with isInstance() returns always. The isAssignableFrom() method has to be used instead.