You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is an area of the the system under test where it creates a new browser window. I need to be able to switch to this and perform the necessary automation task on that, as well as switch back again afterwards. However I'm having trouble getting the browser instance to see more than the current window. So if I run this code before and after the step that creates the new window:
current window title: IBM InfoSphere Master Data Management Collaboration Server v11.3.0
current window handles: [01847c55-529c-4837-a3f6-3417819e61fa]
(navigation logic now creates window)
current window title: IBM InfoSphere Master Data Management Collaboration Server v11.3.0
current window handles: [01847c55-529c-4837-a3f6-3417819e61fa]
How do I convince the driver that there is a new window please? I'm at 1.2.5-SNAPSHOT currently and browser is IE11.
The text was updated successfully, but these errors were encountered:
btw, this problem was not due to a timing issue - I could put a breakpoint on the code and leave it there for any amount of time (e.g. after I saw the new browser window appear) and the number of handles still stayed at 1. Is this something that we have no control over or is there some Serenity code that manages this please @wakaleo?
There is an area of the the system under test where it creates a new browser window. I need to be able to switch to this and perform the necessary automation task on that, as well as switch back again afterwards. However I'm having trouble getting the browser instance to see more than the current window. So if I run this code before and after the step that creates the new window:
I get this:
(navigation logic now creates window)
How do I convince the driver that there is a new window please? I'm at
1.2.5-SNAPSHOT
currently and browser is IE11.The text was updated successfully, but these errors were encountered: