Recorder becomes disconnected after logging into the testing program.

Progress® Telerik® Test Studio® Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Completed

Last Updated: 03 Apr 2023 12:34 by ADMIN

Matt

Created on: 28 Sep 2022 20:31

Type: Bug Report

Recorder becomes disconnected after logging into the testing program.

I have an existing list of steps that I've made for a WPF application. If I select a test step that selects a different button on the testing application then select "Run To Here", wait for Test Studio to reach the previously mentioned test step and will timeout after a new screen opens. I have the Test Log in the attached describing the error (Test Log.txt), which I select test step #3 to "Run To Here". Using Progress Telerik Test Studio Version 2021.3.1103.0. I'm not using any of the web features for testing, and I have uninstalled and reinstalled this version of Test Studio in case this was causing the issue for the recorder to not record anymore.

Attached Files:

2 comments

ADMIN

Elena

Posted on: 03 Apr 2023 12:34

Hi Matt,

The misbehavior was addressed in Test Studio release 2022 R3 SP1 published on 13. October 2022 (v.2022.3.1013).

Regards,
Elena
Progress Telerik

Virtual Classroom is the free self-paced technical training portal that gets you up to speed with Telerik and Kendo UI products including Telerik Test Studio! Check it out at https://learn.telerik.com/.

ADMIN

Plamen Mitrev

Posted on: 05 Oct 2022 08:13

Hello Matt,

I am sorry to hear about the encountered issue with the recorder after partial test execution. I will do my best to help you figure out what is happening and look for a solution for the issue.

The version of Test Studio that you are using is not the latest, but it should work just fine for WPF tests in this scenario. My next though was that the issue might be application specific. I noticed in the video that the login window closes and some time after that the next window of the application opens. It is possible that during this time, Test Studio loses track of the application's processes and could not identify the new window as part of the same application. Please follow the steps below to gather more details on your end.

Open the Windows Task Manager on the machine with Test Studio and go to the Details tab.
Increase the execution delay from 5000 on step two to 20000 msec. This will give you more time to explore the processes.
Run the test again either with Run -> To Here or with the Execute button.
What is the process id and name of the application under test when only the login window appears?
When the login window is successfully automated and the new window appears, let me know what is its process id and name.

Although the above steps will give me some idea about what might be causing troubles, it will still be hard to troubleshoot the issue without access to the application under test. Please discuss it with your team, if it is possible to share the WPF app and testing credentials. I will try to reproduce the issue on my end and debug it against our product. Since this is a public thread, I recommend that you open a private support ticket and share the application there.

Thank you for contacting us and starting this discussion. I hope that we can work together to resolve the issue and enable you to continue with the test automation.

Regards,
Plamen Mitrev
Progress Telerik

Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Test Studio course! Check it out at https://learn.telerik.com/.