I am currently looking into UI testing with alternatives for Selenium, recently i made the switch to VS2013 from VS2012 and the first thing i notice is that, the Coded UI Test project template is missing.
Anyone has a clue why this is missing and / or i need to install something in addition or if some workaround exists to make it available again?
Visual Studio 2013 Ultimate and Premium Editions have CodedUI test. See here for all the supported configuration details:
http://msdn.microsoft.com/en-us/library/dd380742.aspx
I am not sure if you can add it to Professional(I see no downloads listed for CUIT)
As Aniket mentioned, Coded UI is only available for the Ultimate and Premuim editions. There is also a Test pro edition that has a limited number of Testing tools. Some of them can be used to initially describe your tests and the later automate them with Coded UI.
The following links provides a feature comparison between the editions. Go to the Testing tools section, which specifies the availability of Coded UI in the specific editions:
http://www.visualstudio.com/en-US/products/compare-visual-studio-products-vs
Related
I would like to automate my winforms testing using CodedUI but it seems that it is only available on Visual Studio Enterprise. Is it possible to create a CodedUI test project if you don't have Visual Studio Enterprise? If not, what are the alternatives to CodedUI?
The answer as far I know is no. You need Enterprise license to use that feature. This post seems to have some more information enter link description here
The answer is yes if you are on VS 2012-2013. There you need just Premium. Enterprise version is only relevant to VS 2015.
Here is the list of all requirements.
We are using VS2012 Premium edition, it misses "Web Performance and Load Test project" type, so I am wondering can someone suggest good alternative to do performance and load testing in VS premium edition? Is it possible to use Coded UI generated code to run it in parallel to simulate user interactions?
Coded UI tests can be used within a Visual Studio Load Test. As Coded UI takes over the mouse, keyboard and screen of a computer you will need the same number of computers as the number of tests t be run at the same time. The computers may be real or virtual and the overhead of Coded UI is not great. So a computer that is powerful enough to comfortable run your application should be adequate.
The computers that run the Coded UI tests do not need Visual Studio installed. They need the Visual Studio "test agent" software that is easily downloaded from Microsoft. However you would need Visual Studio Ultimate or Team Foundation Server (TFS) to control the tests.
As far as I know, the only way to run load tests in Visual Studio is to use the Ultimate editions.
Here is a summary of Visual Studio versions.
I have built a test with UI automation using Visual Studio 2010 Ultimate. I would like to run the test on computers that have other editions of Visual Studio 2010 installed, not Ultimate. However when I try to use mstest\testcontainer:tests.dll (the dll file of the test with the debug library) there was error that it was missing one of the test files.
Is there a way to run a UI test on a computer without the Ultimate edition? Thanks.
Coded UI Tests only run with VS Ultimate and VS Premium.
Here is an overview showing which VS edition supports which testing features: http://www.microsoft.com/visualstudio/en-us/products.
Here is the screenshot of the link above, just in case the URL shouldn't work anymore one day:
If you're referring to the Coded UI tests, it's only available on the Ultimate or Premium versions of VS2010. If a user is using the Express or Professional, they just won't be able to do it.
If upgrading those users to Ultimate/Premium isn't an option, you might want to look at a different UI testing tool.
I am doing on a project to built automatic GUI testing for graphical application in .NET. I will use C# but i am trying to reading to get some ideas. But I don't have any idea on how to record and replay back. So can you give me your ideas.
Here's a blog from the visual studio team that goes over this exact topic. It's about how they tested pre-wpf and post-wpf.
This post covers an overview of techniques that we used to create and maintain automated user interface regression tests for Visual Studio. Regression tests are a type of software test that, collectively, aim to be an oracle of expected functionality for the target application, run often against new builds of product – they aim to uncover regressions in behavior introduced in a new build.
Visual Studio Blog
Selenium RC!
There is also the TFS Test that has web tests, which tie into load test. Nice platform, but if you are not already using TFS then it is not worth it.
Frankly, I don't think there is a good answer out there for this. There are two options, however, that work okay:
Visual Studio Test Edition (as durilai suggested)
Telerik's Web Testing (both a free version and a version with a cost but depending on your UI, this may or may not work)
A good (commercial) C#-based product is Ranorex, it may do what you need.
Have you updated your Visual Studio to 2010 version? It has a build-in coded-ui automated testing feature, which could be used to record and replay back the test for win form.
Selenium
Watin
are some options that come to mind
To test C# apps there are a few things we have had success with:
PowerShell
TestPlant
and possibly would be the new VSTS 2010 features, though we haven't tried them
I'm developing an application using Visual C# Express Edition - what is the downside to using the express editions? Are there any limitations on what I can build and release? Will my users be able to tell I'm using the Express Edition?
It won't impact your users, other than by making you less productive by prohibiting add-ons such as ReSharper, TestDriven.NET, etc. and not having some of the built-in features of the commercial editions.
To put it another way: if a word processor didn't have a spell checker, you could still make sure that your documents were spelled correctly, so readers wouldn't know - but it's a lot quicker (usually!) if the tool has it built in...
Here is a huge comparison chart of all versions of Visual Studio, from Express until Team System.
Visual Studio 2008 Product Comparison Guide
No AddIns whatsoever - no ReSharper, no TestDriven.net, no VisualSVN, no nothing
Server Explorer does not support remote databases
No support for solution folders
Express targets only a single Framework - Express 2008 targets .net 3.5 only. (Edit: I was wrong, Express 2008 indeed supports multi-targeting)
Reinstalling Express may require re-registration which is free, but can be shut down any time from Microsoft
Apart from that, it's fine. It uses the same compiler to generate the same code, you just don't get all the Time-Saving tools that VS Professional offers.
The Express debugger does not allow Attach to Process:
The ability to attach the debugger to
an already-running process has also
been removed, hindering scenarios such
as writing Windows services and
re-attaching a debugger under ASP.NET
when errors under the original
debugging session cause breakpoints to
be ignored.
I can live with everything else but that.
Only one language is supported. You can't have an application in C# and a library in C++ in the same solution, for instance.
Also, third party ADO.NET providers are not supported in the designers
See features and tools available with Express editions, Visual Studio Standard and Professional editions, and Visual Studio Tools for Office.
It has no mobile device support - one of the most important features, for me :o)
No MFC visual gui builder for C++.
EDIT
Oops - just read the C# tag. I'll leave this up though in case it comes up in a search for anyone else who might also be using c++
Visual Studio Express can do "most" of what the higher editions can do until you start getting into more advanced things such as trying to install third-party components and get full integration, adding database projects, integration into third-party systems, etc. On that note even Visual Studio Standard lacks several of these features so you'd be looking at Professional (at a minimum) to get a fully robust and feature-rich edition.
The current version of VS Express (I'm writing in 2014) has no diagnostics. No assert method and things like stat monitoring. For me this means I'll use a different version to finish a site because it limits testing and validation. No point in making a sub-par .NET site to be actually used.