I have a web-based framework that I had for a good while been executing my test scripts against Chrome 76 using TC14.1 into TC14.2. Then Chrome updated to 77.
The issue that I get conssistently now is when my script at the end will logout of my web app, and then closes the Chrome browser.
i.e. code example:
Delay(30000); --- 3000 used to work for me, then I went to 6000 , still see issue at 30 sec wait
// Close Chrome browser
Warning from TC14.2
Process "chrome" stayed in the system after the close command was used.
Chrome is working in the background and cannot be closed.
I have in Chrome 77 @ chrome://settings/system
Turned Off: Continue running background apps when Google Chrome is closed
I have to logout and close browser like a user as to clear out tokenid that the web app
tracks some on the next script when Chrome is started to login, the web app is still not
considered that user still logged in.
Need some help here
Do you close all other instances of Chrome before you test? Perhaps there's a lingering one from email use or something.
All instanaces of Chrome are closed prior to the test scripts running.
This all worked great in TC 14.1 and Chrome 76.
Trying to narrow down what's changed.
Adding just another tidbit here:
There is 1 or 2 test scripts here and there that will PASS.
All the test scripts start up the same with chrome and logout, close Chrome the same way.
Not sure if there is an easy way to downgrade Chrome 77 back to 76 to try that approach to debug.
Was the issue resolved? Please share the solution with us.
This has not been resolved yet.
Now that Chrome 78 is out, I'm doing some more testing to see if this is Browser side related.
Will keep all posted.