coded-ui-tests

What is the difference between using System.Windows.Automation (commonly known as UIA) API and Microsoft.VisualStudio.TestTools.UITesting (one that is used in Coded UI Test behind the scene) for implementing UI Test automation of a WPF application programatically? Is there any specific scenarios, restrictions or advantages/disadvantages? In fact, the answer is in your question. UIA is used for automation, while UITesting is used for... testing. An excerpt from MSDN: UI Automation provides programmatic access to most user interface (UI) elements on the desktop, enabling assistive technology

My Coded UI Test is configured so that the output of the test automatically produces an HTML log file, the instructions for doing this can be seen here . Is there any way to customize this HTML log or make my own HTML logger so that mine is used to produce the log instead? For instance the default HTML log only shows Assert events if they fail. I would like Assert events to be shown even if they don't fail. I would like to use the default HTML logger as a base as it already does almost exactly what I need, I'm not looking for a solution such as create my own output messages during the test

Closed. This question is off-topic. It is not currently accepting answers. Learn more . Want to improve this question? Update the question so it's on-topic for Stack Overflow. Hi I am looking at using Coded UI Tests (CUIT) to test an application. I have tried the recording option and this is not flexible enough for me. If you use it on a different size screen it breaks. I know you can hand code the tests but I cannot find any good examples of how to write a basic test. There are examples on here that use CUITe but these posts are from 2011 and I'm not sure how relevant they are anymore with

Question Can anyone please explain (preferrably with a code example) how the AutomationProperties.Name property is used programmatically and declaratively with XAML? Explanation I understand that the Coded UI Builder in Visual Studio 2010, for instance, takes a Window's name as SearchProperty. Since my Window's name changes, I would like to have a constant SearchProperty that my Coded UI Tests can rely on. In the code example below, I don't want the window title to be hard-coded as "Properties of Pipe 1" since that changes. Code example [GeneratedCode("Coded UITest Builder", "10.0.30319.1")]

I'm writing some codedUI tests in VS2010 to test a web application. I'd like to be able to open the browser once for the entire set of tests in the solution and then close it again when the tests finish. I've tried AssemblyInitialize attribute on a method, with my BrowserWindow.Launch in there, but it gives me the following exception when I run it: Assembly Initialization method OrdersGridTesting.SuiteSetup.Login threw exception. Microsoft.VisualStudio.TestTools.UITest.Extension.TechnologyNotSupportedException: Microsoft.VisualStudio.TestTools.UITest.Extension.TechnologyNotSupportedException:

Each test case saves results to a separate UITestActionLog.html file. But in the end of each test case I'd like to move that .html to a different folder and rename it. Is it possible to do so in, say, [TestCleanup()]? If yes, then how can I programmatically get .html report location? The TestContext class contains several fields with "directory" in their names. These can be used to access the various directories associated with running the tests. As well as managing the files as asked by your question the TestContext class has an AddResultFile method. The Microsoft documentation on this mehod