Currently the WaitForFrame method only takes FrameInfo object as parameter. It will be helpful to use WaitForFrame method with frame name only.
Posted on:25 Mar 2022 10:20
Thank you, Marc-Antoine, for sharing details about your use case.
As you pointed out, after the improvements to the element merging and creation of duplicated frame nodes, now you need to provide FrameInfo with "name", "id" and "src". Having the ability to call the frame only by "name" will cause issues with the above mentioned improvements and will be a step back for the stability and usability of the product. That is why we have decided that we will not provide the option to wait for frames by their "name" only.
Please do not hesitate to contact us, if you have any concerns or questions.
Does UI testing really fit into CI/CD?
If you want to find out how to take advantage of continuous delivery pipelines, join our Test Studio webinar on Wednesday, April 6 at 11 am EST | 5 pm CET.
Posted on:29 Jul 2021 13:28
In v. 2021.1.616, the Browser's find expression was changed such that:
"FrameInfo" objects are considered equal when their id, name and src match. This improves element merging and creation of duplicated frame nodes is being avoided
(Before, it was either the id, or the name, or the src. Now, it is the id AND the name AND the src)
The find expression is also used by the WaitForFrame method (as it takes a FrameInfo for a parameter). Thus, if in the past, you were using a FrameInfo containing only the name, you now need to provide the id and the src.
An easy way to replicate the past behavior is to create the FrameInfo like this: new FrameInfo("~", frameName, "~"), as ~ is essentially a wildchar expression for this situation.