I use a custom components.xml when running my integration tests that avoid any jbpm stuff.
That speeding things up for me.
Try the new SeamTest structure in Seam 2.1 - it's considerably faster to start.
Well, that's not really an option, since we WANT to test the JBPM process and the related issues :-)
I just thought there may be a trick to deploy the process definition just once for all tests.
BTW: We are using Maven/Surefire to start the tests
We are currently bound to Seam 2.0.1. Can I use the new test framework anyway? That is isolated from the rest?
You can, the underlying structure is the same. Compare the changes in trunk to Seam 2.0.1 to SeamTest.