BMUnit integration identifies TestNG test classes which require Byteman rules to be loaded either because they

1) inherit from BMNGRunner

2) have an @Listeners annotation mentioning BMNGListener

For any given test class only one option is appropriate. The problem arises when test classes using different options are mixed in one test suite.

BMUnit will happily execute a suite of test classes which employ only one of these two mechanisms. However, a test suite which includes classes which, between them, employ both options cannot be handled.

A workaround when using maven is to split the tests into separate executions each of which contains only tests using one of the two mechanisms. Similarly, when using ant the tests can be run using two separate tests each of which selects the subset of the tests employing one or other mechanism.