TestStudio support for desktop application

[Palani]

Hi All,

We have few desktop applications, which has developed using .NET technologies and Java as well. I tried recording script using Test Studio and it was rejected as the application is not WPF app.

Is there any way to automate these non-WPF based applications?

 

Thanks,

Palani

[Boyan Boev]

Hello Palani,

Thank you for contacting us.

Test Studio supports only WPF base applications, unfortunately there is no way to automate a non WPF application.

Thank you for your understandings.

Regards,
Boyan Boev
Telerik by Progress

 

[Gift]

Good Day

i have run the web the test for testing studio but is failing with following error

Failure Information: 
~~~~~~~~~~~~~~~
Unable to locate element. Details: Attempting to find [Html] element using 
Find logic 
 (Html): [id 'Exact' ctl00_cntMain_gdvCompanyList_ctl02_imgARStatus] AND [tagname 'Exact' img]

Unable to locate element. Search failed!

Learn more about finding elements here:
http://docs.telerik.com/teststudio/troubleshooting-guide/test-execution-problems-tg/unable-to-locate-element
------------------------------------------------------------
'6/28/2018 5:25:34 AM' - Detected a failure. Step is marked 'ContinueOnFailure=False' aborting test execution.
------------------------------------------------------------
'6/28/2018 5:25:34 AM' - Overall Result: Fail
'6/28/2018 5:25:34 AM' - Duration: [0 min: 18 sec: 40 msec]
------------------------------------------------------------
'6/28/2018 5:25:35 AM' - Test completed!

[Elena]

Hello Gift,

Thank you for reaching us out, 

As far as I could see from the shared failure details it seems the test wasn't able to log in to the application under test and expected the target element from the next page will not be available. Therefore you first need to ensure the login screen is successfully handled by the test - enter username and password, enter Captcha image information (which probably should be done manually), then click on Submit. 

You might need to include wait steps and/or execution delays to control the speed of execution, enable real user actions for the click and type steps if necessary (please see the screenshots attached). To be able to better see what might be going wrong during execution you could enable the annotations during the run (please see point 5. in this article) which will highlight the target element of each step and will ease you analyze what should be updated. 

In addition you could change the elements' find expressions if necessary - although the recorded expression from you current test seems to be a proper one which will uniquely identify the element. 

Also here you could find useful advice how to configure a Test Studio project so that you could maintain it seamlessly. 

I hope the above shared information will be helpful to you to adjust your test. 

Thank you for your cooperation in advance!

Regards,
Elena Tsvetkova
Progress Telerik