infinispan-embedded cluster, jpa, jdbc, leveldb tests

A few 'self-standing' tests for infinispan-embedded UberJar.
Your tests seem to rely on specific test execution ordering because one tests initialises cache/cachemanager instances and the others use it. I'm not sure you can always make such guarantees and I don't think it's good practice for test method encapsulation. Either create cache managers in BeforeClass, and close them in AfterClass, keeping it symmetric, or make each test create its own cache manager.