Upgrading Coded UI Tests from Visual Studio 2010
Test Projects containing coded UI tests that were created in Visual Studio 2010 SP1 are silently repaired when opened in Visual Studio 2012. If the Test projects are checked into source control, the project files are checked out for this repair. Once repaired, these test projects containing coded UI tests can then be used in both Visual Studio 2010 SP1 and Visual Studio 2012.
Requirements
- Visual Studio Ultimate, Visual Studio Premium
Note
Visual Studio 2012 includes more than one test project type. If you create a new coded UI test, it will be created in a coded UI test project type. For more information, see Upgrading Tests from Earlier Versions of Visual Studio.
Warning
Visual Studio 2010 test projects that contain coded UI tests must be rebuilt when you open the test project in Visual Studio 2012 or Visual Studio 2010 side-by-side with Visual Studio 2012.
Warning
When a test project that was created in Visual Studio 2010 and contains only unit tests is opened in Visual Studio 2012, coded UI tests cannot be added to it. Similarly, you cannot add a coded UI test to a unit test project that was created in Visual Studio 2012.
Compatibility Issues between Visual Studio 2010 and Visual Studio 2012
The following table lists issues to be aware of when migrating coded UI tests between Visual Studio 2010 and Visual Studio 2012.
Warning
There is a known issue regarding references in coded UI test projects not appearing in Solution Explorer. For more information, see the ReadMe file included on the Visual Studio 2012 installation media.
Coded UI functionality |
Issue |
Solution |
|---|---|---|
Silverlight UI Testing is not supported in Visual Studio 2012 |
Build will fail If you have Visual Studio 2010 Feature Pack 2 and have created Coded UI Test Projects for Silverlight applications, these projects cannot be opened in Visual Studio 2012. |
We recommend that you manage these projects in Visual Studio 2010 Feature Pack 2 only. Warning |
Firefox UI Testing is not supported in Visual Studio 2012 |
Build will succeed, test run will fail If you have Visual Studio 2010 Feature Pack 2 and have created Coded UI Test Projects for web applications in Firefox, these projects cannot be opened in Visual Studio 2012. |
We recommend that you manage these projects in Visual Studio 2010 Feature Pack 2 only. Warning |
New UI code testing APIs have been added in Visual Studio 2012 |
Build will fail If you create Coded UI Tests using the new UI Testing API in Visual Studio 2012, these projects cannot be opened in Visual Studio 2010. |
Projects using new API should be managed in Visual Studio 2012 only. |
In Visual Studio 2010, references were added inside a ‘Choose’ statement in the csproj file. In Visual Studio 2012, we are using a Feedback targets file to include Coded UI Test Assembly references. |
In Visual Studio 2012, a Coded UI Test cannot be added to a Test Project created in Visual Studio 2010 (or SP1) that did not contain a Coded UI Test. The repair process adds the targets file and the Choose statement. If a Coded UI Test is not in the Test Project, then the project is marked as repaired and the appropriate references will not be added when adding Coded UI Test in Visual Studio 2012. |
You will have to create a new Test Project in the same solution using Visual Studio 2012 and add your new Coded UI Test in it. Alternately, you can add Coded UI Tests into the Test Project in Visual Studio 2010 SP1 and open that project in Visual Studio 2012. |
Visual Studio 2010 SP1 Update
An update to Visual Studio 2010 SP1 with compatibility support for Visual Studio 2012 and Windows 8 is available for download at the Microsoft Download Center and also as a Visual Studio update.
After you apply the update, the following Visual Studio 2010 SP1 coded UI test tool features are improved for Windows 8:
You can run a Coded UI Test for the Microsoft .NET Framework 4.5-based Windows Presentation Foundation (WPF) controls on a computer that is running Windows 8.
You can run a Coded UI test for 64-bit (x64) Internet Explorer 10 on a computer that is running Windows 8.
The update also contains fixes for the following issues:
Code coverage: Inability to open a code coverage file (.coverage) that is created by Visual Studio 2012 in Visual Studio 2010 SP1.
Stranded test artifacts: Your team has a test artifact that is assigned to an invalid user in Team Foundation Server (TFS) 2010. For example, a user has left the company, but still has a test case that is assigned to him. You upgrade TFS 2010 to TFS 2012. You use Microsoft Test Manager 2010 to connect to the upgraded TFS server. You are not able to assign the test artifact to any TFS users by using Microsoft Test Manager 2010.
Load testing: When you run a load test together with a network type other than the local area network (LAN) profile on a computer this is running Windows 8, the network emulator driver causes the operating system to crash. For more details, see KB Article 2736182.
See Also
Concepts
Visual Studio 2012 Compatibility
Upgrading Tests from Earlier Versions of Visual Studio
Verifying Code by Using Coded User Interface Tests
Supported Configurations and Platforms for Coded UI Tests and Action Recordings
Other Resources
Generating a Coded UI Test from an Existing Action Recording