Run from here deactives the debugger

Second problem:   manually setted breakpoints ("Toggle breakpoint") are ignored, too.

Here is started at test step 51 with "Run from here" - and taken screenshot at step 54.  The breakpoint at step 53 was ignored.

Hi Paul,

I am sorry to hear you have faced any troubles while debugging your tests and will be happy to assist you with sorting this out.

The Breakpoints in Test Studio are respected from the Visual Debugger tool - this is being started, depending on the current settings, by each quick test execution.

On the other hand, Test Studio allows you to partially execute any test using the Run.. context menu options. And since there is a recorder attached to the browser, you can continue debugging the recorded steps - this is why the Visual Debugger is not launched when there is an active recording session. 

Still, you can continue executing a set of steps and not all of these while in recording mode. Here is what the three options under the Run.. menu are dedicated for: 

• Run.. To Here - select any step in the test and choose this option. The test will be executed up until this step, or at an earlier stage if a failure occur, and the recorder will be attached to the current state of the application. 
• Run.. Selected Step(s) - select one or more consequent steps and choose to execute only these in the current recording session. Thus, if the steps are supposed to be executed against a page other than the current loaded, these will fail. 
• Run.. From Here - select a step from the test and choose this option. The test will be executed from that step further against the same recording session. Again, if that selected step is supposed to be executed against a page other than the current loaded, it will fail. The recording session remains open after the selected and following steps are executed and you can continue recording or debugging. 

I hope that these notes will help you better understand the different tools and how these can be helpful in debugging the tests in Test Studio. Of course, if you need further assistance on any topic, please do not hesitate to get back to me.

Thank you for your cooperation in advance.

Regards,
Elena
Progress Telerik

Hi Elena,

thanks for the explenation.

I use the "Run to here" option to start at the point i was the last time working on.  All ok here - in command prompt box output the debugger is enabled and halt on all errors active, as i set it in studio.

After about a minute the selected step is reached. The browser ist still open and recorder running and connected.
Now i click at the next step and select "Run from here" in context menu  ->  the test continues but without debugging, as you can see in the first screenshot "runfromhere_cmd.png":    "Debugger Enabled = 'False'   Debugger Mode = 'Normal'"

For me this is a bug - or it's a feature of the "Run FROM here" function that the debugger is here always deactivated?

>"Run.. Selected Step(s)"

I will use this one as workaround. Up now i use this for one step only. Doesn't used it with several steps.  This allows me to run only the next nn steps

Hello Paul,

Thanks for sharing these notes. It seems that you haven't upgraded to the latest official version of Test Studio - 2020.1.331, as it doesn't the console window anymore. The reason for this change is that the mentioned command prompt window wasn't providing much useful information to rely on for test debugging. 

Therefore, we decided to remove this and focus the attention on the actual tools developed in Test Studio, which helps you in debugging any errors in the tests - these are the Visual debugger and its options, or the active recording session and the partial run of a test. I am glad to hear that you find these useful and you fix your tests with their help. 

Of course, if there is anything you have difficulties with, please, do not hesitate to get back to me and continue the discussion.

Thank you once again for your understanding in our discussions.

Regards,
Elena
Progress Telerik

Thanks for the info  :)   But how can i update..?

Actually i have an 2019.xxxxxxxx - when i select "Check for updates" i get "Your software is up to date".

I got it.  Thats strange, because we have test studio licence for several weeks up now - and the 2020.1 update was from march.  It's installed now. I will test it.
Strange is also, why  the 2019 version has said that there are no newer updates.

Hi Paul,

I am glad to know that you managed to upgrade to the latest version of Test Studio. 

The 'Check For Update' service is using reaching the Telerik server in the background and I suspect it could have been prevented from some firewall or antivirus system. Possibly, this will be again failing, so you can check the application log. First clear it, then click the 'Check For Update' - it will report there is no newer version, but in the application log there will be an exception if the service failed. 

Alternatively, you can check with your IT department if there are any restrictions on the machine or network, which may be preventing Test Studio to contact an online server and check for updates. 

Once this service can contact the server, you can also enable the automatic check for updates, which will be triggered on Test Studio startup and will notify you when we publish a new version.

I hope these additional details will help you sort out what prevents the check for updates on your end. Of course, if you need further assistance, please, do not hesitate to get back to me. Thank you for your continuous cooperation.

Regards,
Elena
Progress Telerik