Steps Pane scolls to bottom of page after playback.

[Jim]

Does anyone else have this problem?

I updated a few days ago 2023.1011.1.
I highlight and run a set of steps. When it ends, the Steps Pane scrolls to the bottom.
Since I may have hundreds of steps, remembering where I was and scrolling up to get there is time consuming.

If not perhaps it is a Win 11 issue.

[Alexander]

Hello Jim,

The scroll is designed to behave like this.
If a test fails, the scroll focus is set on the step that failed. This way it is easier to locate and analyze the failed step.
If all steps pass, then the focus is set on the last executed step (the last one in the test).

For easier navigation through your test steps you can use the search bar and the step type filter on the top of the step panel.

 

Hope this helps.

Regard,
Alexander
Progress Telerik

[Jim]

When I said "I highlight and run a set of steps" I did not mean to infer that I was running the whole test.  

My test has 37 steps. On the screen I can see 24 of them.

I agree: If I choose and run steps 3 and 4 and they fail, the scroll focus is set on the step that failed. The page does not scroll. 

If I choose and run steps 3 and 4 and they pass, the scroll focus is set on row 37. It does not matter if I have 37 rows or 370 rows it behaves the same way. It scrolls to the bottom of the test. 
So, the focus is not "set on the last executed step". 

[Alexander]

Hello Jim,

We registered this issue as a bug last week - the public item is published here.

It is listed in our product backlog and will be addressed in our future releases. 

Thank you for your understanding. 

Regards,
Alexander
Progress Telerik

[Steven]

I have not yet executed any tests on a Win 11 machine so someone else may be able to speak to that, however, I do find it much more manageable to change long tests (>70 steps for me) into a series of executable modules by using the "Test as Step" feature. For instance, the user login becomes a test module. Then - if the app I'm testing has 30 screens, each with unique business rules, I create an individual executable test module for each screen - where each test module may have multiple steps. This makes debugging much easier and also helps if the project stakeholders decide to remove functionality, it's often contained in an individual module.

Hope this helps!

SSq

[Jim]

I use Test as a Step and agree there is less scrolling.
There is one thing I don't like. If I begin the play back on the 'parent' test, and it fails on the 'child' test there are no green boxes, and no red box in the child. It's not that I can't figure it out it just takes longer. 

I just now learned that clicking View Complete Test Log is the log for the failed child. That should help. I always hit View log and scroll to the bottom.
I made the child fail on row 91. Oddly the Step Failure Details shows step 65. No idea why, even after doing the math covering the parent and the children. The test numbering takes into account rows hidden by If/Elses.