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
Please look at the following proposal for adding support for iFrames to SeLion. We are running into the issue where some pages contain an iframe that we need to interact with. We usually create a separate page object and switch to the frame before interacting with it.
This works but our test cases start to look a little more messy, as we can't rely on all the features of SeLion anymore.
Proposal:
Create an element similar to Container which represents an iframe with subelements.
If we interact with an element in a iframe it should automatically switch to the iframe.
Add the ability to automatically switch back to main window when taking screenshot.
For 2 and 3 the behavior should be configurable so that people can change the behavior to their needs. And this should be supported on a global level and on per iframe object level through Yaml.
The text was updated successfully, but these errors were encountered:
@renelux Other than the Config need, I think you could accomplish this with a custom element. That said, I can see the value of having support for something like this in the SeLion code. My only suggestions are to;
Consider putting a solution that more generically solves the problem for anything where a call to driver.switchTo().window(handle) is needed.
Let's think of it more generically as a "view".
Let's include support for mobile, in the case of hybrid apps that need to driver.switchTo() web and app views.
Thanks for the suggestion! I look forward to seeing what you come up with!
Please look at the following proposal for adding support for iFrames to SeLion. We are running into the issue where some pages contain an iframe that we need to interact with. We usually create a separate page object and switch to the frame before interacting with it.
This works but our test cases start to look a little more messy, as we can't rely on all the features of SeLion anymore.
Proposal:
For 2 and 3 the behavior should be configurable so that people can change the behavior to their needs. And this should be supported on a global level and on per iframe object level through Yaml.
The text was updated successfully, but these errors were encountered: