|
|
Re: Cann´t test after a Software update(my AUT) [message #1386116 is a reply to message #1282365] |
Fri, 13 June 2014 13:03 |
Marie-Christin Kloss Messages: 10 Registered: September 2013 |
Junior Member |
|
|
Hy Alex, sorry for the late reply, but because of some exams and other tasks at work, I haven´t time for my jubula project.
- the logs are empty
- it is not possible to start the execution. How you could see into the picture, the Button is chose able, but nothing happens.
If you press to the OM, Observing it worked a moment, the button become gray and after 0,5-2 Minutes it´s the same like the beginning.(Without doing what should)
- I´m not using a remote desktop
- My oldest program version works without any problems. If I´m updating this version, there is no problem, but if I want to install one of the newer one, there are the problems. After a update from eclipse Juno to Kepler it´s not possible to update my ATU, so I must install it new.
Maybe I have a mistake in my mind, but the only thing I have to do is:
- place the "org.eclipse.jubula.rc.rcp_2.2.0.201310100933" into my plugin folder
- add into the confi.ini ",org.eclipse.jubula.rc.rcp@start"
- connect the AUT in jubula
Best regards
Marie
|
|
|
|
|
|
|
|
|
Re: Cann´t test after a Software update(my AUT) [message #1401340 is a reply to message #1400632] |
Tue, 15 July 2014 13:10 |
|
The scenarios you mentioned are (at least as a simple test case) part of our nightly regression test, i.e. we start a bunch of Eclipse versions to see if the RCP accessor is working.
One thing that would explain the difficulties you experience is the installation/configuration area of RCP applications. If you start your AUT on the same machine/account without cleaning all files you may have an older version of the RCP accessor in the cache. Try starting your AUT with the -clean parameter of remove all artifacts by hand to get a clean run.
Let us know if something changes.
- Achim
|
|
|
|
Powered by
FUDForum. Page generated in 0.02696 seconds