Ta 
Ah it’s just a matter of how it was coded - the ClientUnitTest class itself contains the ‘minimal/headless client’ state/setup, so I’d just need to refactor it to move that into a different class, and a single unit test should be able to do multiple headless clients.
Just hasn’t been needed/useful up until now - but it’s marked down as something to do now.