Hi Alex,
Thanks for your response.
Unfortunately, this is not the solution to the problem :-(
Meanwhile i tried different things upto a complete reinstall of TC and Chrome on my machine (including a reboot after deletion). It won't help.
Luckily, I have TC11 still on my PC. I can continue to work, as TC11 does my scripts without hesitation (also the Chrome browser parts).
I logged an incident with the helpdesk. I'm intrigued why this is not working for TC12.... and wondered whether there are no fellow testers having the same problem....
I did not have the problem you mention with Chrome, but I didn't try TestComplete 12 with Chrome. I did run into a problem with TestComplete 12 and IE though, and like you I logged a support issue and have stayed with TestComplete 11 for now. I mention this since you were asking for other user experiences and I am on the forum looking for other people's experience with TestComplete 12. I'm interested in moving to TestComplete 12 but so far i'm getting the feeling I should expect to wait for the next minor update to fix some problems.
-Adam
Hi Adam,
Meanwhile, I was helped correctly with the SmartBear Servicedesk.
It seemed that i (unwantingly) deleted a counter, which should have made me jump to my next browser (chrome) but instead, he relaunched my first browser (ie).
As we all know, the process of IE takes a time to close down, so when starting up the next (cross-browser) tests, it detected 'browser already running' (as that was IE closing down) and did not want to continue.
I mistakenly thought Chrome was not recognised.
Meanwhile all problems have been solved and TC 12 is working as steadily as before. So no need to be afraid of switching to TC12.
Hope it helps!
Good luck.
Dominic
PS. to help everyone. The last three lines (in the above code) should have read:
browserindex = browserindex + 1
Call Aliases.browser.BrowserWindow.Close(5000)
Wend
