Vishnu's Blog https://docs.microsoft.com/archive/blogs/vishnus_blog/feed.xml Wed, 17 Apr 2019 03:54:08 GMT en-US hourly 1 Coded UI Test not able to interact with the desktop https://docs.microsoft.com/archive/blogs/vishnus_blog/coded-ui-test-not-able-to-interact-with-the-desktop Sun, 05 May 2013 10:08:00 GMT https://blogs.msdn.microsoft.com/vishnus_blog/2013/05/05/coded-ui-test-not-able-to-interact-with-the-desktop/ If you are running into the following error, Please read the options to enable Coded UI Tests on a remote machine.

Error calling Initialization method for test class NewTitlesPush.NewTitlesPush: Microsoft.VisualStudio.TestTools.UITest.Extension.UITestException: Automation engine is unable to playback the test because it is not able to interact with the desktop.  This could happen if the computer running the test is locked or it’s remote session window is minimized.

 

For the UI tests, the active desktop session has to be opened. We have faced this issue and we have couple of solutions

1. Open a Hyper-V session onto the machine where the UI Tests are running. You can minimize the hyper-V window and the tests will still run fine.

2. If you are running tests in a Lab Environment created from Microsoft Test Manager, Run the tests and open LEViewer[Lab Environment Viewer] to keep the desktop session active.

3. Enable AutoLogon on the machine where the tests are running and restart the machine. Then you don't need to do remote desktop - https://support.microsoft.com/kb/310584

 

Thanks,

Vishnu

 

]]> Running VS 2010 SP1 Coded UI Tests on VS 2012 Test Agents https://docs.microsoft.com/archive/blogs/vishnus_blog/running-vs-2010-sp1-coded-ui-tests-on-vs-2012-test-agents Tue, 09 Apr 2013 11:23:00 GMT https://blogs.msdn.microsoft.com/vishnus_blog/2013/04/09/running-vs-2010-sp1-coded-ui-tests-on-vs-2012-test-agents/ To run VS 2010 SP1 Coded UI Tests using VS 2012 Test Agents, these are the requirements

1. Coded UI test projects should be opened in VS 2012. This auto-upgrades the test project to VS 2012. The upgrade test project is compatible with VS 2010 SP1 as well. If the test project is not upgraded, then you might hit the below error

Unit Test Adapter threw exception: Could not load file or
assembly 'Microsoft.VisualStudio.QualityTools.CodedUITestFramework,
Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of
its dependencies. The system cannot find the file specified..

2. Build Agent should be of version TFS 2012 with VS 2012 installed

3. VS 2012 Test Controller and VS 2012 Test Agents should be registered with TFS 2012.

]]> Silverlight 5.0 Support https://docs.microsoft.com/archive/blogs/vishnus_blog/silverlight-5-0-support Thu, 18 Oct 2012 04:29:42 GMT https://blogs.msdn.microsoft.com/vishnus_blog/2012/10/18/silverlight-5-0-support/ Few months back, We had added support for Silverlight 5.0 applications.

Please check out the plugin at https://visualstudiogallery.msdn.microsoft.com/28312a61-9451-451a-990c-c9929b751eb4

]]> How to access Test Case Manager Test Case ID https://docs.microsoft.com/archive/blogs/vishnus_blog/how-to-access-test-case-manager-test-case-id Tue, 29 Mar 2011 13:12:00 GMT https://blogs.msdn.microsoft.com/vishnus_blog/2011/03/29/how-to-access-test-case-manager-test-case-id/ In Visual Studio 2010, we can create test cases using Microsoft Test Manager and can associate automation to these test cases. During the test method execution, we might need the test case Id of the test case for various reasons.

Unfortunately, the TESTCONTEXT doesn’t expose the Test Case Management context that you could use from the Test Method itself. 

1.       Write a custom data collector. This article will help in writing a simple custom data collector - https://blogs.microsoft.co.il/blogs/shair/archive/2010/04/19/how-to-create-custom-datacollector-in-visual-studio-2010-part-1.aspx

2.       From the custom data collector's event handler, you could access the Test Case Management Context like below.

private void OnTestCaseStart(object sender, TestCaseStartEventArgs e)

{

      try

      {           

           File.WriteAllText(@"C:\MTM_TC_Association\TestCaseID.txt", e.TcmInformation.TestCaseId.ToString());

      }

}

 

]]> Assigning Unique AutomationId for Silverlight XAML Controls https://docs.microsoft.com/archive/blogs/vishnus_blog/assigning-unique-automationid-for-silverlight-xaml-controls Tue, 21 Dec 2010 06:57:00 GMT https://blogs.msdn.microsoft.com/vishnus_blog/2010/12/21/assigning-unique-automationid-for-silverlight-xaml-controls/ If you want to run coded UI tests or create action recordings for your Silverlight 4 application, you must have a unique automation property that identifies each control. For more information about how to set up your Silverlight application so that the controls are recognized, see How to: Set Up Your Silverlight Application for Testing.

Static XAML Definition

To specify a unique automation property for a control that is defined in your XAML file, you can set the AutomationProperties.AutomationId or AutomationProperties.Name implicitly or explicitly, as shown in the following examples. Setting either of these values gives the control a unique automation property that can be used to identify the control when you create a coded UI test or action recording.

Set the Property Implicitly

Set the AutomationProperties.AutomationId to ButtonX using the Name property in the XAML for the control.

<Button Name="ButtonX" Height="31" HorizontalAlignment="Left" Margin="23,26,0,0"  VerticalAlignment="Top" Width="140" Click="ButtonX_Click" />

Set the Property Explicitly

Set the AutomationProperties.AutomationId to ButtonX explicitly in the XAML for the control.

<Button AutomationProperties.AutomationId=“ButtonX” Height="31" HorizontalAlignment="Left" Margin="23,26,0,0"  VerticalAlignment="Top" Width="140" Click="ButtonX_Click" />

 

Assigning AutomationId using UpdateAID tool

To simplify the process of assigning unique AutomationId, we have built a small tool that will help, when there are many static XAML controls in your silverlight application project. The steps to add the AutomationId are given below

Step 1. Build the Silverlight Application Project by specifying the "UpdateUid" switch

   msbuild /t:UpdateUid <SilverlightApplication1.csproj>  

   Please note that the switch applies only to the CSPROJ and not to the SLN file of the project. This creates an XAML directive "x"Uid" with an unique Uid for every XAML control.

   Say your SilverlightApplication1 project contains only the following XAML content

     <Button Content="Button" Height="23" HorizontalAlignment="Left" Margin="186,90,0,0" Name="button1" VerticalAlignment="Top" Width="75"  />  

   After building with UdpateUid switch, the XAML content will be as below with the highlighted part added

    <Button x:Uid="button1" Content="Button" Height="23" HorizontalAlignment="Left" Margin="186,90,0,0" Name="button1" VerticalAlignment="Top" Width="75"  />  

Step 2. The attached file UpdateAID.zip contains both the source(UpdateAIDToolSource.zip) of the tool as well as the compiled EXE(UpdateAIDTool.zip). Unzip the UpdateAIDTool.zip file to a folder.

Now the folder should contain two files - 1. UpdateAIDTool.exe 2. ControlList.txt

Step 3. Check if you have the desired list of controls in ControlList.txt file. You can remove or add more controls as you need. We suggest specifying the full control type name as it is in the XAML.

Step 4. From command prompt, run the following command

  >> UpdateAIDTool.exe <Silverlight Project top directory>

The tool adds the "AutomationProperties.AutomationId" property for all the XAML controls that had the Uid directive set earlier. After this, the XAML content will be as below with the highlighted part added

    <Button x:Uid="button1" Content="Button" Height="23" HorizontalAlignment="Left" Margin="186,90,0,0" Name="button1" VerticalAlignment="Top" Width="75"
            AutomationProperties.AutomationId="button1" />

For Silverlight controls other than the static XAML controls, please refer this article to know how to assign unique Automation ID - https://msdn.microsoft.com/en-us/library/gg413373.aspx

UpdateAID.zip

]]>