|Re: Aut Agent loses connection to Aut during test execution [message #1505898 is a reply to message #1505746]
|Wed, 10 December 2014 11:58
| Alexandra Schladebeck
Registered: July 2009
The database doesn't have any bearing whatsoever on the communication between the client and the server as far as I'm aware. It looks like your problem is related to the command line parameters you are using. You are using the -timeout parameter with 700, which means that the test exec itself will stop after this time. This is documented here.
It's true that Jubula disconnects and reconnects to an AUT between test jobs - that's because they're designed to deal with addressing multiple AUTs in a test, so the new connection has to be made. If you're only working with one AUT, then the preferred way to structure your tests is to use single test suites (e.g. one for your productive test cases, one for your incubation / smoke test / .. test cases). Within a test suite, you add each "use case" you want to test. Each use case is contained within a Jubula Test Case, and should be independent of any other use cases (i.e. it should assume or create its starting setup and leave the application in this state at the end - either via correct execution or via an event handler). An article on this is on the portal:
There are also other articles about structure and conventions there that might be helpful. This is the kind of thing our consultants offer reviews and training on too, if you're interested.
Hope this information helps,
Powered by FUDForum
. Page generated in 0.02808 seconds