Posted 19 Jun 2013
Link to this post
Apologies for re-posting here, but realized this is probably actually the right forum.
I'm trying to create web tests in Test Studio for a page which subsequently opens a new popup and opens a silverlight application inside an IFrame within that popup.
When I am recording tests in Test Studio I seem to end up with lots of duplicate root level elements, with say one individual element underneath each. This seems to cause particular problems with the IFrame holding the silverlight application and I found if I set UseQuery to false and cleared out the BaseURL and Query fields in the properties they generally combine back into one root element, which is fine. Although I seem to have to do this for every single new step I record, which is slightly annoying!
As soon as I run the tests on a different machine, additional steps are creating different root elements again and as the URL and title bar were different for that machine it seemed impossible to combine them all back into a common base at this point.
I just want it to always ignore things like the title bar, URL and query strings as these will obviously be different for each test run and each machine that the tests are worked on or run on. But all I seem to end up with is a mess of elements in this tree.
Could somebody point me in the right direction as to how to manage this element tree correctly? Because of all the duplicates it's very hard to tell what element belongs to which version of the base page or IFrame and so tests steps consistently fail and I'm not sure why. To me it seems strange that there are all these properties mapped to the machine the tests are being recorded/run on, I have bound data for things like the IP address to browse to etc. so I would expect to be able to continue writing tests or running them on any machine and it would act the same way.
Any help would be appreciated!