|AUT persist in memory after testsuite ? [message #1066180]
||Mon, 01 July 2013 12:34
| Paraita Wohler
Registered: June 2013
I have a problem where my AUT Agent does not "release" my AUT once the test is over. Here's my test bench:
- the AUT agent is already launched, listening on port 60000.
- I use testexec to execute my tests.
- I use the -data and -autconfig flags to set my AUT.
- testsuites should be run separately. (testexec -testsuite myts1, testexec -testsuite myts2, etc...)
I understand that using the -autconfig, the AUT Agent launch the given AUT itself. So when I call testexec, everything runs fine, and when the test is finished, the AUT is closed (at least visually) but after say 4 calls to testexec, I get 4 instances of the same AUT in memory. Since I'm running on a slow machine running xp 32 bits, I can really feel my system getting slower and slower.
Before using the -autconfig flag, I was using the -autid flag, but that imply the AUT is already running, so I also use autrun before pulling up testexec. Well I get another problem with that, because I can't close the AUT without making my testsuite fail. Because the AUT doesn't have any File->Exit menu, I use the ALT+F4 shortcut. AUT Agent wasn't complaining about it until the recent version of Jubula (7.1) with the message in the file attachment.
Putting all my testsuite in a sole testsuite or job won't be possible, as Jubula is going to be integrated in our continuous integration workflow, and I need to be able to select from another tool which tests I'll run.
Powered by FUDForum
. Page generated in 0.10459 seconds