> 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.
Mauro, Sorry for the delay in responding. As to why closing the application closes JBehave with it: There is a step to close the application that will ultimately call a "system.exit(0)". What I understand is that, since I start the application with a step that calls the its main method, it runs in the same JVM as JBehave. So, when "system.exit(0)" is called, the JVM closes with both applications. The application being tested is fairly large, it's exit points are always "system.exit(0)". My current problem is in implementing my "@AfterScenario" step. I want to be able to run a snapshot of my database in order to keep the database always in a valid state between scenarios. I've been trying to see how easy it is to close the connections myself. But since the application is quite old and there is a lot of legacy code, some complex refactoring would be needed. > 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 example, this is a very simple scenario that I first wrote in order to test Jemmy with JBehave. Please don't mind if it's too simple. I didn't know exactly where to put it, so I sent it to Sendspace http://www.sendspace.com/file/1bm1fy -- Victor Moura Cortez --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
