CodedUITest fails to locate current document in IE-Tabs - by sko

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 761401 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 9/6/2012 3:46:11 AM
Access Restriction Public


I created a simple HTML page that opens a second tab with another page. A CUIT fails to assert or use any controls on this second tab. I added an assertion for the title of the second document and it fails because it uses the title of the first one.
When I configure IE to always open popups in new windows, everything works fine.
see attached solution
Sign in to post a comment.
Posted by sko on 9/10/2012 at 11:29 PM
When this is by design, I am asking who made the design?
With this bug CodedUITest is almost useless for us. Do you know any kind of workaround for this behavior?
Posted by Microsoft on 9/10/2012 at 6:13 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by sko on 9/10/2012 at 12:59 AM
I attached video recording of the failing test. The steps to reproduce the issue are very easy. Open the attaced Solution, build and run the CodedUITestMethod1 with IE in default configuration
Posted by Microsoft on 9/6/2012 at 10:47 PM
Thanks for your feedback.

In order to fix the issue, we must first reproduce the issue in our labs. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please give us a video recording your steps so that we can conduct further research?

Please submit this information to us within 3 business days. We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 9/6/2012 at 3:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(