In customer's application it generates a number of dynamic frames. The Name and ID will changes based on if it's the first or second or third tab of the application. This means you cannot use these properties to reliably find the correct frame because when you run the test you don't know which tab it will generate. The baseurl of the src attribute is always the same no matter what type of tab is being created, so you can't rely on that either. There is a long complicated query string which can be used to identify the correct frame however the client needs this to be parameterized for reusable subtests. One test will require one value and another test will require a different value (e.g. the name of a "Property" as created and used in their application). Ideally they would like to be able to data drive the Frame Info just like you can data drive finding elements. Barring that they need some mechanism of being able to parameterize which frame to look in when looking for elements. Different tests will create different frames with different src values but the rest of the content in the frame will be the same e.g. the tab for Property AAA will have the same elements as the tab for Property BBB. But since they src property is different they are currently being forward to write two different tests that effectively do exaclty the same thing but in different frames.