At last the feature that many testers wanted and waited for is NOW available.
Today with the launch of Visual Studio and Team Foundation Server 2012 Update 1, you will find some new test features in Microsoft Test Manager in Visual Studio 2012 Update 1. And the among these features is the one that we waited long for it “ Cross Browser Testing with Coded UI ” ![]()
Now users will be able to perform functional testing of web applications across IE/Firefox/Chrome.
System Requirements:
- Operating System: Windows 8 X86 Client/Windows 8 X64/Win7 X64/Win7 X86/Win2k8 R2 SP1
- IE version – IE9/ classic IE10
- Firefox version – 15+
- Chrome version – 21+
- Visual Studio Ultimate/Premium – VS 2012 RTM + VS 2012 Update 1 CTP
- Selenium NET Bindings and the Selenium ChromeDriver made available to you through an installer on Visual Studio Gallery. Refer to the file attachment “CUIT Cross Browser Testing Acquisition” for more details
Features:
The following features are available across the various web browsers:
- Recording support for actions and validation on supported IE browsers
- Hand-coding scenarios support for such things as control properties, search, and playback waiters.
- Support for popups and dialog
- Ability to execute basic JavaScript with no return type
- Search resilience (via smart match) and performance improvements
Scenario Videos:
Record on IE and Playback everywhere
Author cross browser tests with Coded UI Test Builder
Author cross browser tests using plain hand coding without UI Map
Run cross browser tests sequentially on multiple browsers
Troubleshoot cross browser test failures
Known Limitations
- No support for Safari browser
- Browser launch needs to be part of the UITest. In case you have a browser already open and you want to run steps on the opened browser, playback will fail for non-IE browser windows. Hence, it is advisable to have launch too as part of the test case.
- Automating browser based actions such as Maximize/minimize/restore is not supported
for more info click here
Happy Testing ![]()
Thanks for the info. I will try that out soon. But I think for web applications selenium is a better choice but may be I am wrong. Correct me if I am.
Hi
i didn’t try selenium before
but what i like about TFS (Microsoft Test Manager) & (coded UI) is how it is very easy to use, and also how to make code coverage for the test cases you run (even if its not automated) this gives you great advatage to see how code coverage by test cases and also how to link your requirement/tasks to test cases to bugs and code coverage (whether manual test cases or automated). you can see all of that in ready made report matrix
I will second that. You are right. Microsoft has provided tight integration with TFS due to which it is easy to integrate all your components.
But that all comes with a cost. On the other hand Selenium is free.
One more thing I am surprised about that Coded UI does not come under the list of best commercial automation tools either. You can visit this link
http://www.automatedtestinginstitute.com/home/index.php?option=com_content&view=article&id=1379:ati-automation-honors&catid=128:past-winners&Itemid=184#CommercialTools
to see what I am talking about. Here it is beaten by Ranorex in the .Net category. Microsoft is providing a commercial tool but it is not able to compete with existing commercial tools. On the other hand selenium is free and it is the best in its category.
Maybe because Coded UI Test was supporting cross browser testing but for very old versions, and as i can see all the testing tools support latest versins and as i mentioned in my post here, this is an update to Coded UI that just came out 2 days
Hope with this new update, it will compete well with the other products. but not sure if not supporting safari will impact that