Heya! Glad to see your interest. Currently there aren't many pure implementation details around this effort, but the general goal is to flip the common Arquillian execution flow on it's head. So to speak. The way Arquillian work today is by hooking into the lifecycles of the Test Frameworks and let the Test control the execution flow. e.g. * when BeforeSuite -> start a container * when BeforeClass -> do a deployment etc.. What we want to do here is remove our selves from the test framework lifecycle and create a simple scripting front end over the Arquillian backend that allow you more flexibility and control over what to do and when to do it. You can see the prototype/sketch I created a while back to get a somewhat feel for it; https://gist.github.com/aslakknutsen/5563547 To describe the prototype in short: * You should be able to configure up multiple environments (containers, deployments) * Then create scenarios that you can play out based on those environment settings Start server x, do some deployment, Start server Y, so some deployment, Kill server X, Run some tests, etc etc.. Hope that helps a little... -aslak- ----- Original Message -----