Wait For Not Exists & Validate (NotExists) failure
Posted: Wed Jan 15, 2014 2:15 pm
Hi,
New day, new issue
OK, my new problem is like this. I have a recording, which closes the application then starts the Wait For Not Exists action with 5000ms timeout. And after this action, there is started Validate "NotExists" action.
The application is closed and Wait For Not Exists is almost immediatelly finished (in less than 2 sec.), so the application must really be terminated/not existing, right? The thing is, that Validate "NotExists" action sometimes fails with "Element for item 'Repository.AppName.Self' does exist." error. Why the Wait For Not Exists is terminated before the timeout is reached and the application probably still exists? How this could happen?
I tried to turn the Turbo playback OFF, but this did not help. The only thing that helped was adding a forced Delay before the Validate step, but I would like to avoid that.
This recording worked fine but all of suddenly, it started to act like this. Could it be something wrong in 4.1.4? Does the Wait For Not Exists action use a different kind of element existence detection than Validate "NotExists" action?
Unfortunately, I don't have a demo to share. I'm only able to reproduce it after loading and unloading number of proprietary files, which takes about 15 minutes to complete the test. Our nightly test loads even greater number of these files and the test takes about 2 hours to complete. And as I said, exactly the same test worked fine before.
New day, new issue
OK, my new problem is like this. I have a recording, which closes the application then starts the Wait For Not Exists action with 5000ms timeout. And after this action, there is started Validate "NotExists" action. The application is closed and Wait For Not Exists is almost immediatelly finished (in less than 2 sec.), so the application must really be terminated/not existing, right? The thing is, that Validate "NotExists" action sometimes fails with "Element for item 'Repository.AppName.Self' does exist." error. Why the Wait For Not Exists is terminated before the timeout is reached and the application probably still exists? How this could happen?
I tried to turn the Turbo playback OFF, but this did not help. The only thing that helped was adding a forced Delay before the Validate step, but I would like to avoid that.
This recording worked fine but all of suddenly, it started to act like this. Could it be something wrong in 4.1.4? Does the Wait For Not Exists action use a different kind of element existence detection than Validate "NotExists" action?
Unfortunately, I don't have a demo to share. I'm only able to reproduce it after loading and unloading number of proprietary files, which takes about 15 minutes to complete the test. Our nightly test loads even greater number of these files and the test takes about 2 hours to complete. And as I said, exactly the same test worked fine before.