While moving the cli tests (those that can be) from the wildfly testsuite to the core, I stumbled upon a couple of puzzling issue which I don't see running the tests locally but the PR doesn't get a green light. One of them is maven-based module loading. Some of the tests start the CLI as a process providing all the command line arguments. These tests fail with Failed to resolve artifact 'org.wildfly.core:wildfly-cli:1.0.0.Alpha6-SNAPSHOT' Looks like it's not installed before the testsuite run. As a workaround, I, temporarily, pointed jboss.dist to core-dist/target/... The second problem is establishing a connection to the controller. Trying to connect, as in wildfly, using - http-remoting - TestSuiteEnvironment.getServerAddress() - TestSuiteEnvironment.getServerPort() fails with 'The controller is not available at [::1]:9990'. Any ideas how to fix this? Thanks, Alexey