Both WildFly Arquillian and WildFly Core have ServerSetupTask interfaces. (Core does not use ARQ so it has its own interface for use with WildFly Core Test Runner.) They differ in the type of the 'management client' passed into setup/tearDown.

In testsuite/shared create an adapter class to allow core task impls to be easily used in full WF. The adapter class takes the core ServerSetupTask as a c'tor param. It includes logic to translate from an WFARQ ManagementClient to a core ManagementClient. In setup/tearDown in translates and invokes the core ServerSetupTask.