How to start the Ivy Server in plain Java?

You can pass a new org.eclipse.core.runtime.NullProgressMonitor() to the mentioned method.

But anyway I also think that Tamas is right. Normally its better to start a real server with e.g. with Maven. The maven script could then be used to test locally or remote on the ci-server. So you really know if the test will run on ci or not as you execute the same logic:

1. on phase pre-integration-test: start a server, deploy projects (e.g. by calling ant as tamas suggested)
2. on phase integration-test: execute your junit test e.g. with maven-surefire
3. on phase post-integration-test: stop the server

i'm wondering about reasons why to test anything in Designer. Likely you want to make sure that the solution works for the customer (on a server Engine).

I suppose you already use some Continuous Integration to make sure your tests executed automatically. https://guidelines.axonivy.com/projects/guides/wiki/Continuous_integration

With Ant or Maven scripts you can control when an Engine is started and stopped. In between you may execute any number of (JUnit) Tests.

In case you really want to test the Designer itself, e.g. you write Eclipse plugin to Ivy, then see my private mail with attached Eclipse based Test cases.