error in automation running: not a valid technology name: Telerik.UIA

6 posts, 0 answers
  1. Paul
    Paul avatar
    8 posts
    Member since:
    Mar 2014

    Posted 13 Aug 2014 Link to this post

    I got following error while running a coded ui automation against WPF windows application with Telerik control.

    Test method XXXX threw exception: System.ArgumentException: The following is not a valid technology name: Telerik.UIA. To search for a control, you must specify a valid technology name.Parameter name: TechnologyName

    The code generated by coded UI is like following...

            #region Properties
            public UITestControl UI_caseIdTextBoxEdit
            {
                get
                {
                    if ((this.mUI_caseIdTextBoxEdit == null))
                    {
                        this.mUI_caseIdTextBoxEdit = new UITestControl(this);
                        #region Search Criteria
                        this.mUI_caseIdTextBoxEdit.TechnologyName = "Telerik.UIA";
                        this.mUI_caseIdTextBoxEdit.SearchProperties[UITestControl.PropertyNames.ControlType] = "Edit";
                        this.mUI_caseIdTextBoxEdit.SearchProperties["AutomationId"] = "_caseIdTextBox";
                        this.mUI_caseIdTextBoxEdit.SearchProperties["HelpText"] = null;
                        this.mUI_caseIdTextBoxEdit.WindowTitles.Add("Glidewell Office");
                        #endregion
                    }
                    return this.mUI_caseIdTextBoxEdit;
                }
            }

    The automation can run on my dev machine but failed to run on test machine without VS.

    I copied the Telerik.VisualStudio.TestTools.UITest.Extension.ExtensionsCore.dll together with my automation binaries. Also I installed Telerik UI for WPF and Testing Framework on the test machine. But I still got the same error.






  2. Alek
    Admin
    Alek avatar
    78 posts

    Posted 14 Aug 2014 Link to this post

    Hi Paul,

     We will need additional information in order to investigate this scenario. 

    Please, specify the following:

     - the control you are trying to automate;
     - the version of the control;
     - also, you wrote that there is no VS installed in the test pc. Please let us know did you succeed to run CodedUI tests recorded over default WPF controls;
     - the path where the Telerik.VisualStudio.TestTools.UITest.Extension.ExtensionsCore.dll is copied;
    - did  you add the Telerik.VisualStudio.TestTools.UITest.Extension.ExtensionsCore.dll into the GAC;
    - do you use an additional tool for test automation;

    Looking forward toyour answer.

    Regards,
    Alek
    Telerik
     
    Check out Telerik Analytics, the service which allows developers to discover app usage patterns, analyze user data, log exceptions, solve problems and profile application performance at run time. Watch the videos and start improving your app based on facts, not hunches.
     
  3. UI for WPF is Visual Studio 2017 Ready
  4. Paul
    Paul avatar
    8 posts
    Member since:
    Mar 2014

    Posted 14 Aug 2014 in reply to Alek Link to this post

    Here I am posting some detailed tracing information. Later I will post the answer to your enquiry.

        <UnitTestResult executionId="3afe244c-68b9-4791-8ae5-e7c7a17238f5" testId="a2d2ee7f-ad7b-12ab-0f5a-88ae754ff13c" testName="CaseInformation_WorkflowTrackingSteps_BasicTest_CUIT" computerName="UATW732BIT01" duration="00:00:32.2190167" startTime="2014-08-14T15:12:59.3299053-07:00" endTime="2014-08-14T15:13:31.5571277-07:00" testType="13cdc9d9-ddb5-4fa4-a97d-d965ccfc6d4b" outcome="Failed" testListId="8c84fa94-04c1-424b-9868-57a2d4851a1d" relativeResultsDirectory="3afe244c-68b9-4791-8ae5-e7c7a17238f5">
          <Output>
            <ErrorInfo>
              <Message>Test method WorkflowTracking_Test.WorkflowTrackingServiceTestClass.CaseInformation_WorkflowTrackingSteps_BasicTest_CUIT threw exception: 
    System.ArgumentException: The following is not a valid technology name: Telerik.UIA. To search for a control, you must specify a valid technology name.
    Parameter name: TechnologyName</Message>
              <StackTrace>    at Microsoft.VisualStudio.TestTools.UITesting.UITestControl.ValidateSearchProperties()
       at Microsoft.VisualStudio.TestTools.UITesting.UITestControl.FindInternal()
       at Microsoft.VisualStudio.TestTools.UITesting.UITestControl.&lt;Find&gt;b__d()
       at Microsoft.VisualStudio.TestTools.UITesting.CodedUITestMethodInvoker.InvokeMethod[T](Func`1 function, UITestControl control, Boolean firePlaybackErrorEvent, Boolean logAsAction)
       at Microsoft.VisualStudio.TestTools.UITesting.UITestControl.Find()
       at Microsoft.VisualStudio.TestTools.UITesting.UITestControl.GetPropertyPrivate(String propertyName)
       at Microsoft.VisualStudio.TestTools.UITesting.UITestControl.&lt;&gt;c__DisplayClass11.&lt;GetProperty&gt;b__10()
       at Microsoft.VisualStudio.TestTools.UITesting.CodedUITestMethodInvoker.InvokeMethod[T](Func`1 function, UITestControl control, Boolean firePlaybackErrorEvent, Boolean logAsAction)
       at Microsoft.VisualStudio.TestTools.UITesting.UITestControl.GetProperty(String propertyName)
       at Microsoft.VisualStudio.TestTools.UITesting.ALUtility.GetTechElementFromUITestControl(UITestControl uiTestControl)
       at Microsoft.VisualStudio.TestTools.UITesting.ActionExecutorManager.GetActionExecutor(UITestControl uiControl)
       at Microsoft.VisualStudio.TestTools.UITesting.Mouse.ClickImplementation(UITestControl control, MouseButtons button, ModifierKeys modifierKeys, Point relativeCoordinate)
       at Microsoft.VisualStudio.TestTools.UITesting.Mouse.&lt;&gt;c__DisplayClass6.&lt;Click&gt;b__5()
       at Microsoft.VisualStudio.TestTools.UITesting.CodedUITestMethodInvoker.InvokeMethod[T](Func`1 function, UITestControl control, Boolean firePlaybackErrorEvent, Boolean logAsAction)
       at Microsoft.VisualStudio.TestTools.UITesting.Mouse.Click(UITestControl control, MouseButtons button, ModifierKeys modifierKeys, Point relativeCoordinate)
       at Microsoft.VisualStudio.TestTools.UITesting.Mouse.Click(UITestControl control, Point relativeCoordinate)
       at MERPTestAutomation.UIMaps.GO2UIMapClasses.GO2UIMap.GO_CaseInformation_GetCase() in c:\B01\2\QA\MERPTestAutomation\Sources\QA\source\MERPTestAutomation\MERPTestAutomation\UIMaps\GO2UIMap.Designer.cs:line 43
       at WorkflowTracking_Test.WorkflowTrackingServiceTestClass.CaseInformation_WorkflowTrackingSteps_BasicTest_CUIT() in c:\B01\2\QA\MERPTestAutomation\Sources\QA\source\MERPTestAutomation\MERPTestAutomation\TestClasses\WorkflowTrackingServiceTestClass.cs:line 89
    </StackTrace>
            </ErrorInfo>
            <TextMessages>
              <Message>New order 1017944750 was created and will be used to testing.</Message>
            </TextMessages>
          </Output>
          <ResultFiles>
            <ResultFile path="UATW732BIT01\CaseInformation_WorkflowTrackingSteps_BasicTest_CUIT.png" />
          </ResultFiles>
          <ExtensionResult>Exception has been thrown by the target of an invocation.</ExtensionResult>
        </UnitTestResult>
  5. Paul
    Paul avatar
    8 posts
    Member since:
    Mar 2014

    Posted 14 Aug 2014 in reply to Alek Link to this post


     - the control you are trying to automate;
    A:
    ControlType: Edit 
    ClassName: Uia.TextBox 
    TechnologyName: Telerik UIA
    all of above information is quoted from coded ui test builder

     - the version of the control;
    A: UI for WPF 2014 Q1 331

     - also, you wrote that there is no VS installed in the test pc. Please let us know did you succeed to run CodedUI tests recorded over default WPF controls;
    A: Yes. Actually the failed point is in the middle of test of an automation. Before it can successfully logon and open some windows in automation.

     - the path where the Telerik.VisualStudio.TestTools.UITest.Extension.ExtensionsCore.dll is copied;
    A: I specified to copy the referenced assembly to local. So it's in the same folder as the test automation assembly.

    - did  you add the Telerik.VisualStudio.TestTools.UITest.Extension.ExtensionsCore.dll into the GAC;
    A: Yes. I tried just now. But it still failed.

    - do you use an additional tool for test automation;
    A: No.

  6. Alek
    Admin
    Alek avatar
    78 posts

    Posted 15 Aug 2014 Link to this post

    Hello Paul,

    Thank you for the details you have sent us.

    Regarding the first question we would like to know which of ours RadControls you are working with in this scenario. For example, is it RadAutoCompleteBox or RadComboBox, RadWatermarkTextBox, RadDateTimePicker etc.?

    Also, we have noticed that you've wrote " Before it can successfully logon and open some windows in automation.". Did you replace only the Telerik.VisualStudio.TestTools.UITest.Extension.ExtensionsCore.dll or there is another change in the application so now you are experiencing the issue?

    Regards,
    Alek
    Telerik
     
    Check out Telerik Analytics, the service which allows developers to discover app usage patterns, analyze user data, log exceptions, solve problems and profile application performance at run time. Watch the videos and start improving your app based on facts, not hunches.
     
  7. Paul
    Paul avatar
    8 posts
    Member since:
    Mar 2014

    Posted 18 Aug 2014 in reply to Alek Link to this post

    What's wired - there is only one control (text box) which the test builder identify as Telerik.UIA. The other telerik controls e.g. gird, they do not even be taken as Telerik.UIA.

    I walk around this issue by handing code instead of using coded UI test builder generated code.


Back to Top
UI for WPF is Visual Studio 2017 Ready