CodedUiTest and VS2017 | Infragistics Forums

CodedUiTest and VS2017

Giulia posted over 6 years ago

Hi,

I have a Coded UI test project, created with VS2015 and Infragistics Version 15.1 (Windows Forms)

The tested application was migrated to VS2017 and Infragistics Version 17.2 and so I need to migrate my Coded Ui Test Project too.

I installed VS2017, the Coded Ui Test Extension in VS2017, Infragistics 17.2 and the Coded UI Extension.

First question is: why the size of the extension in the installer is 0 byte?

Then I rebuilded my project, fixed all compilation issues and started the tests.

I always obtain an error that is:

System.ArgumentException: The following is not a valid technology name: Infragistics.UIA.v17.2. To search for a control, you must specify a valid technology name.

Parameter name: TechnologyName

I also tried to create a new clean project and register some actions on my application.

Same error.

Parents

29105

Offline Michael DiFilippo posted over 6 years ago

Hello Giulia,

Thank you for contacting Infragistics. Please note, as a disclaimer, that the Enterprise Edition of VS 2017 is required for CodedUI. Do you have the VS2017 Test Agent only installed or both the IDE and Test Agent?

I've managed to reproduce the 0 byte information in the installer, and I will inform our release engineering team.

However, in the meanwhile I've tested the installer and CodedUI is still installed correctly. Please confirm if the Coded UI Test folder with the Infragistics assemblies are installed on the test agent machine.

Eg. The Infragistics4.Win.CodedUITest.UIA.VS15.v17.2.dll assembly is installed at the following location:

C:\Program Files (x86)\Infragistics\2017.2\Windows Forms\Coded UI Test

I strongly recommend reviewing our documentation for setting up CodedUI ==> Extension Overview

Let me know if you have any questions.
Cancel
Reply

Cancel
35

Offline Giulia posted over 6 years ago in reply to Michael DiFilippo

Hi Michael,

thank you for your reply.

I have VS2017 Enterprise installed and I have VS2017 on the same machine that I am using for testing.

I have all the assemblies in the folder that you are mentioning.

Moreover we tried to use the VS2015 with Infragistics 17.2 and it works fine, so the issue seems with VS2017 and Infragistics V17.2.
Cancel
Reply

Cancel
29105

Offline Michael DiFilippo posted over 6 years ago in reply to Giulia

Hello Michael,

Thanks for following up. Does the issue only occur with migrated coded ui tests from VS 2015? Can you reproduce the issue with any component? Please provide exact steps to reproduce the behavior.

I have VS 2017 so I am ready to start testing the areas of concern. Let me know if you have any questions.
Cancel
Reply

Cancel

Reply

35

Offline Giulia posted over 6 years ago in reply to Michael DiFilippo
The issue occurs also with a new Coded Ui Test created with VS2017 Enterprise.

The pre-requirements are to install Infragistics for Windows Forms and its extension for Coded Ui Test

To reproduce the issue to the following steps:

Create a new Coded Ui Test project in VS2017 under Visual C# -> Test as shown

Add as reference the Infragistics The Infragistics4.Win.CodedUITest.UIA.VS15.v17.2.dll assembly.

Record some actions on an Infragistics application, to be sure that in the TechnologyName field of the recorded items there is Infragistics.UIA.v17.2.

Play the recorded tests

Here you can find a small example created as described above.

https://drive.google.com/open?id=1XZiYXSvq0_i68qc1cKgvxaJwiQnmJ1D7
Cancel
Reply

Cancel

Children

29105

Offline Michael DiFilippo posted over 6 years ago in reply to Michael DiFilippo

Hello All,

I just verified a solid work around, for the time being.

Please copy the "Infragistics4.Win.CodedUITest.UIA.VS15.v17.2.dll",

found in it's installed directory path:
C:\Program Files (x86)\Infragistics\2017.2\Windows Forms\Coded UI Test

to this location will address the issue:
C:\Program Files (x86)\Common Files\microsoft shared\VSTT\15.0\UITestExtensionPackages

What's occurring is an issue with our installation which is being addressed.

Once you copy the assembly to the new location you can create a new test project. The project will automatically reference the Infragistics CodedUITest assembly and everything should work as expected.

At this time, existing test projects may continue to experience issues. Let me know if you have any questions.
Cancel
Reply

Cancel
29105

Offline Michael DiFilippo posted over 6 years ago in reply to Terry Hillson

Hello All,

Development ID 252090 was created to further investigate and resolve this issue. Please update your support cases with any questions you may have. Note, you may receive periodic updates from the development item in your support case as well.

Sincerely,

Michael Di Filippo
Associate Software Developer
Infragistics, Inc.
www.infragistics.com/support
Cancel
Reply

Cancel
0

Offline Terry Hillson posted over 6 years ago in reply to Michael Salmon

I'm glad to hear someone else is having the exact same problem as us. I have tried versions 17.2.20172.1000 and 17.2.20172.2039 (ie the latest one) and both have the bug in them.

The following is not a valid technology name: Infragistics.UIA.v17.2. To search for a control, you must specify a valid technology name.
Parameter name: TechnologyName

at Microsoft.VisualStudio.TestTools.UITesting.UITestControl.ValidateSearchProperties()
at Microsoft.VisualStudio.TestTools.UITesting.UITestControl.FindInternal()
at Microsoft.VisualStudio.TestTools.UITesting.UITestControl.<Find>b__175_0()
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.<>c__DisplayClass179_0.<GetProperty>b__0()
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.UITestControl.<>c__DisplayClass194_0.<WaitForControlPropertyEqual>b__0(UITestControl ctrl)
at Microsoft.VisualStudio.TestTools.UITesting.UITestControl.WaitForCondition[T](T conditionContext, Predicate`1 conditionEvaluator, Int32 millisecondsTimeout)
at Microsoft.VisualStudio.TestTools.UITesting.UITestControl.WaitForControlPropertyEqual(String propertyName, Object propertyValue, Int32 millisecondsTimeout)
at Microsoft.VisualStudio.TestTools.UITesting.UITestControl.WaitForControlExist(Int32 millisecondsTimeout)
at
Cancel
Reply

Cancel
29105

Offline Michael DiFilippo posted over 6 years ago in reply to Michael Salmon

Hello Giulia,

Thank you for following up. After investigating this further, I was able to reproduce the behavior.

I have created a support case for you with ID CAS-194856-B0J7B0. I've linked the case to a development item with ID: 252090 for our team of developers to investigate further. You could reach your case following the link bellow:

https://es.infragistics.com/my-account/support-activity

I will update you via the mentioned case, so if you have any further questions or comments please update your case.

Have a nice day.
Cancel
Reply

Cancel
0

Offline Michael Salmon posted over 6 years ago in reply to Giulia

@Michael DiFilippo
We are waiting to hear back from you on that.
It is a real blocker for our coming release.
Thanks
Cancel
Reply

Cancel