Enhance Coded UI Test to include the many common features found in commercial-off-the-shelf software test automation packages like SmartBear's Test Complete. These packages typically feature very rich functionality in mapping and managing UI control objects, whereas Coded UI does not. Packages like Test Complete also boast an impressive list of technologies with which it is compatible. Coded UI is limited in this respect as well.
We have a backlog item to add more features to manage UI Maps & maintain Coded UI Test in the Coded UI Test Editor.
Hi Have been using Coded Ui from last two years i am felling comfortable working with this tool,
we have automated two big applications,
even when i started working with Coded Ui i don't know any thing about C # when when you get used to then it is really easy and maintainable i am not talking about record and play back.
I need the easy of use of QTP for test automation!!!
+1 on getting QTP functionality + Key word based UI testing.
Diwan Bisht commented
1- Does VSTS-Codded UI has any Object Spy feature.
2- Does it has any Descriptive Programming technique like QTP (there are some object which Codded UI is not able to record) so that can we use Descritipve programming like QTP?
Thanks in Advance....
Richard Morison commented
Shubhra, you guys are a dollar short and a day late. Codedui is very limited and not surprisingly even teams at Microsoft haven't adopted Codedui but have instead stayed on Quality Center. Seriously try to work with the object graph in codedui for multi-screen applications is far too difficult. Have to be a senior level C# programmer to work with test automation means that codedui costs dramatically more than the equivalent QA/BA staff we can hire and have QTP test automation created. And don't point me to your action recording technology. Action Recordings are so limited the technology is nearly useless..
Shubhra Maji MSFT commented
In Visual Studio 2012 we made an effort to simplify the user interface to give people more room for their own work and to make the IDE more productive. Part of this simplification was to not show many toolbar options. In case you are wondering how to get the test Toolbar back, please refer to Chuck's post on ALM blog:
We have added backlog items to add a similar data wizard in Coded UI Test in upcoming updates. Please let us know through comments if the missing data wizard is a blocker for you so we can prioritize accordingly.
Shubhra Maji MSFT commented
@Samuel: You may want to look at the latest integration of Logigear's TestArchitect with VS ALM
TestArchitect for Visual Studio uses module-based keyword test authoring to automate coded UI tests in Visual Studio 2012. By eliminating coding, keyword based testing allows more team members to be involved in test design and execution.
Feel free to post your comments and further asks on the blog comment thread
Mathew Aniyan(MSFT) commented · October 21, 2011 5:53 a.m. · Flag as inappropriate · Delete
The product team is considering a proposal to address this request. I am looking for users to validate this proposal."
So after nearly a year of looking at these feature requests you guys come out with this nasty looking metro version that not only has nothing requested in your own forums and you've removed functionality that was in 2010. I'm referring to the removal of the data wizard and the test toolbar.
When are you guys going to get serious about this tool!!!! I can't think of one single reason to move to 2012.
You guys should either get serious about this tool or sell it off to someone else like you did Visual Test. I would have hoped lessons would have been learned from that failed experiment but I guess NOT!
Sam Rodney commented
I want to be able to do keyword based UI testing and to be able to have the UI automation run against Java (for android) and IOS (for Iphone).
We've looked at LogiGear's TestArchitect but it doesn't integrate cleanly with Team Build and Lab Management.
We've looked at Squish from Frog Logic but it's SUPER expensive and doesn't integrate into MTM's manual tester runner action recordings.
Samuel Drumond commented
Yes I want QTP type functionality with CodedUI. Working with UI Maps shouldn't be the job of developers...it should be something that manual testers are able to do. I'd like to have keyword based testing that's better than what logigear makes. Test Architect (http://www.testarchitect.com/)sort of works but has a limited feature set and doesn't tie in easily with Team Build.
Alon Kobets commented
To sum everybody here, we want a QTP that works with C# and integrates with TFS.
Here, I've said it :)
I just found this site and I came straight to this issue. It is now 11/05/2012 and this issue of Object maintenance in Coded UI Automation is **** in Visual Studio. I honestly don't understand how you can go to market with this solution as an automated test tool. It is like the job was half done.
I have installed the UIMap Toolbox and at best it is a patch on a bad solution.
You "Microsoft" should be able to come up with a good solution to Object maintenance. Have a look at the Object Repository Manager in QTP if you want some idea of where you should be going with this functionality.
John Bennett commented
Really need to be able to drag and drop Objects (as you can in QTP) else the UI Control Map soon becomes a mess and difficult to read with UIFrame1, UIFrame2, UIFrame 3 and so on - I need to be able to rename UIFrame1 to UIFrame and then move the contents of UIFrame2 and UIFrame3 into it. (as UIFrame1, 2 and 3 are all the same frame just recorded at a different time).
Brian Paisley commented
The biggest running issue for me around coded ui is the 'OMG I have no idea what window the control is in' issue that pops up constantly when replaying coded ui tests. We could do with a utility that locates the active window and resets the controls to that window. It just shouldn't be this difficult to make a coded ui test play reliably, and it shouldn't be difficult for MS to release a utilty that does this for us.
This causes constant pain in creating ui tests, and I'm going to struggle to roll out coded ui to the QA team, because the skills required to code around this are probably beyond most testers. This isn't a minor annoyance, but rather a real obstacle to the use of coded ui as a quality management tool.
Mathew Aniyan(MSFT) commented
The product team is considering a proposal to address this request. I am looking for users to validate this proposal. If you can spare 30mins to review the proposal and give feedback, please mail me - mathewan at microsoft dot com.
I would just like to add to this i would consider myself as having good coding skills as development has always been an interest of mine. Because of this i am able to pick up CUIT fairly easily. But since working in a development team I've been through 5 other QA Member and none of them had much coding knowledge. Other product do tend to bridge that gap with things like keyword driven tests. In saying that their is a huge benefit of having it in .net as it makes it extremely flexible. An example of this is integrating CUIT with Specflow to allow automated Acceptance Tests and living documentation
Other products also help you to visualise the test by taking screenshot's of the control or form and building a visual timeline of the test. This would also be added bonus and would help the average QA into a more specialist type role.
I Agree, Coded UI Tests at the moment require a fair amount of codeing knowledge and unless you want to get into development it can be hard to find QA's with that knowledge. When you look at competitors there is a lot more the average QA can do without coding.
The biggest improvement need for me is UIMap Managing, being able to transfer methods and related controls to a new UIMap, Selecting what UIMap an existing action recording will be placed in to and still being able to see methods once they are transferred to code for editing. Oh and of course a spy tool you can use without starting the CUIT Builder and Adding all controls on a selected window / webpage to the UIMap
Anu MSFT commented
Hi Michael - it would be really nice if you could prioritize your top concerns here.
1. What sort of advanced functionality in managing UI controls would you like? Have you tried UITesteditor in Feature Pack 2? Does that meet your needs?
2. What specific technologies would you want us to support in CUIT? Which of these are most important to you?