Community
Participate
Working Groups
Use Jubula to start AUT and try the following steps. 1) Use Eclipse as your AUT 2) Create simple Java project (You do not need to develop your test for project creation, you can do it manually) 3) Delete created project 4) Develop simple test using ub_app_restart to restart AUT 5) Observe Project Explorer of Eclipse after restarting I am using app restart in my tests and I am seeing this issue.
Since restart terminates the AUT very fast the normal shutdown code may not be executed. Since Eclipse uses an in memory representation of the file system this would explain this behavior.
Closed as invalid
Update (better late than never!) - we've just implemented two new actions to allow "correct" restarting of an AUT which should resolve the issue described here. The actions will be available in Kepler.
*** Bug 382323 has been marked as a duplicate of this bug. ***