I have a new problem with my automation of my Jubula's test...
I have automated some test suite since a few month and they work pretty well (except some errors). But since some days, sometimes my job on Hudson fail with the error "Can't connect to AUT".
I've checked if the AUT is running and it is. No other things are running on the machine during the execution of my job.
So, a lot of days I have to launch a new time my test so it's time consuming and let me think I can't trust myself to Jubula.
Have you any idea to solve my problem and having a test automation safest ?
For information :
My Hudson server and Jubula run on different virtual machine on the same server.
Jubula version is the 7.1.
on which platform are you working on? How do you start the AUT (via configuration in testexec, autrun, from the ITE)? Have you changed something in your test Environment? Have you tried using Jubula 8.0?
My AUT is launched on a virtual machine with Windows XP 32 bits. It's started with the autrun.
My Hudson job is configure to execute the next steps :
- Take the last compiled AUT (from another job)
- Add the plugin to my AUT
- Start the AUT Agent
- Start the AUT
- Run the Test Job with 5 Test suites
- Close the AUT Agent
- Create a index of access to reports
My environment has not been modified since the creation of the Hudson job two month ago.
At the moment, I've not tried Jubula 8.0 but in the near future we would like to upgrade Jubula to the version 8.0. But one of my concerns is whether automation with Jubula 8 is more maintainable ?
Jubula automated tests have been failed too many times for obscure reasons, if you have any advice to ameliorate our automation I would be happy to hear.