setting INTERACTIVE_TESTS=1 when running the test suite 'fixes' this by creating a rabbit within the testapp environment. its trace shows:
slave appserver rabbit - initially 59260
reconfigured to port 53162
and oopses raised in the appserver won't be seen by the parent test runner, so not a good solution, but makes me think I'm in the right area.
setting INTERACTIVE_TESTS=1 when running the test suite 'fixes' this by creating a rabbit within the testapp environment. its trace shows:
slave appserver rabbit - initially 59260
reconfigured to port 53162
and oopses raised in the appserver won't be seen by the parent test runner, so not a good solution, but makes me think I'm in the right area.