Idea ID: 2796220

Silk Test should support .Net Core Apps

Status: Waiting for Votes

Waiting for Votes

See status update history

Currently Silk Test does not work well with .Net Core apps.  It is not that Silk Test is not able to map any controls with the .Net Core version of an app.  Silk Test is able to map some controls but not all.  For example Silk Test is able to map the main window for one of our .Net Core apps, however other tools and controls within the main window are simply called “Control” without any unique identifier like automationId.  

This automationId will enable us to uniquely identify a control as most windows/controls are mapped as “Control”.   When we contacted Micro Focus support we were told: "With regard to your question on .Net Core; this technology is not currently supported by SilkTest. As all SilkTest techdomains are loaded into the Recorder by default there are no options or settings that could have an influence on the lack of object recognition. Under these circumstances you will likely need to rely on fallback mechanisms such as image and text recognition (if possible) and low level events such as mouse moves and TypeKeys() to navigate the application. The fact that the controls are not recognised at all unfortunately limits the options available to you."

We were also told that any controls that were identified by Silk Test for a .Net Core app were accidental as Silk Test does not support .Net Core apps.

As a result a whole automation test suite consisting of about 525 test cases that was developed using Silk Test for a WPF app targeting .Net Framework 4.6 is rendered useless for the .Net Core version of the same WPF app.  A version of Silk Test that supports .Net Core apps will be extremely helpful to us.