Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Error creating Coded UI Test in Visual Studio 2010 Ultimate

I am attempting to create a Coded UI Test in a Visual Studio 2010 test project.
I right click on the project, Select Add Select Coded UI Test

I then get the error warning:

The following package failed to load: C:\Users[File Path Goes Here]\Microsoft.VisualStudio.TestTools.UITest.Extension.IE.dll. Coded UI Test is now in an inconsistent state. Remove this package and restart Visual Studio to work with Coded UI Test.

Once I click OK, I can create the Coded UI Test (CUIT) but when the test is over, the test file is empty.

Does anyone know how to fix this problem? I've already deleted my settings, AND reinstalled VS 2010, all to no avail.

Thanks everyone.

like image 408
Steve French Avatar asked Jul 08 '11 20:07

Steve French


People also ask

Is coded UI open source?

Coded UI from Microsoft and open source White from TestStack are two popular choices for developers starting with automating UI tests for WPF applications. Coded UI is shipped with Visual Studio starting from version 2010. White is an open source project, you can find it here. It's also available as a NuGet package.

What is coded UI Automation Tool?

Coded UI (also called CUIT) is an automation testing tool provided by Microsoft technologies which helps in creating automated tests. The Coded UI tests help us verify the whole application such as User Interface and their functioning properties.

How do I record a UI web test?

To do so, navigate to Window > Preferences > Test > Recording > Web UI Recording and select Record all actions on the page. Do not change any browser preferences, including JavaScript settings. Recording and playing back Web UI scripts in a browser requires that JavaScript be enabled.


1 Answers

No idea about the source of the problem, but if you go to C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\ and copy the Microsoft.VisualStudio.TestTools.UITest.Extension.IE.dll file into the bin/debug directory everything works fine.

I don't know why VS assumes that the .dll is there when it's not, but that is the fix.

like image 141
Steve French Avatar answered Sep 30 '22 03:09

Steve French