We have editor support for creating a new Service Test class, but this tests a service directly. If I want to test an application from the outside using a MixIn, then I don't need to specify a service being tested in the new unit test dialog and I'm not going to use an Invoker instance.

I see two options to address this:

1) Modify the existing new unit test class wizard to make the service testing optional. If the user selects a service to test, then add an Invoker injection in the unit test to call that service. If no service is selected, then just stub about a basic unit test.

2) Add a new unit test create option which does not require a service in the wizard.