Hi Victor, it's not entirely clear as to why closing the application under test control should close JBehave with it. For example, look at the noughtsandcrosses example:
https://svn.codehaus.org/jbehave/trunk/core/examples/noughtsandcrosses/ It happily uses a library for GUI app control from JBehave. Perhaps you could send us a simple example of your app and how you are trying to use JBehave to run Jemmy. We can then provide more insightful advice. As for the running in a different JVM, at the moment neither the Ant nor Maven entry points have the fork option. But you could run the scenarios as normal JUnit tests using either the Ant junit task or the Maven surefire plugin, both of which support the fork option. Cheers On 21/05/2010 16:25, Victor Moura wrote: > Hi, > > I'm trying to write acceptance tests using JBehave with Jemmy to control > and verify the state of Swing components. > > The problem I'm having is simple. After a scenario is finished I need to > close the application in order to clear everything that remains in the > background, like Singletons. This is done so that when the next scenario > runs, he gets a clean environment with no previous objects in memory. > > The thing is, I can't just simply close the application, because when I > do that, I'm closing the JVM (and JBehave) with it. > > So, is there something I can do like running two separate JVMs or some > mechanism that enables me to close my application and still keep JBehave > running? > > Thanks > > -- > Victor Moura Cortez --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
