thanks for the link.
I'll look how to start the tcServer before running test and stopping it after these.
I have different kind of tests.
I have some tests where I will use directly the full functionality of terracotta and use a tc server. (I guess the connection to the TC Server will solve the classpath problem).
For some other tests, I would mock the terracotta API (using Mockito) in order to only test my code.
By this way I can check the parameters used to call Terracotta API (Mockito) and other methods which are not using terracotta, speed up the tests by avoiding deployment and connection to a TC server).
But it is in this second case where I don't know how to define correctly the class path.
I added in my maven project dependencies to :
Thanks for answers.