Last Updated: 27 Dec 2019 07:46 by ADMIN
Created on: 13 Dec 2019 12:31
Type: Feature Request
Add ScrollToVisible option for all actions that simulate real user behavior

The ScrollToVisible option is not available for some of the actions that use translators. One of them is the RadSearchBox, where this property is not available.

Currently the workaround is to add an Enter text step against the <input> element. To do that, you need to use the highlighter and record any verification step. Then add the Enter text step from the step builder, enable SimulateRealTyping and change the ScrollToVisible option.

Plamen Mitrev
Posted on: 16 Dec 2019 11:12


Thank you for sharing additional feedback on the topic.

The ScrollToVisible action is generally a very quick action that ensures the element is visible on the page. In recent versions of Test Studio, we added the ScrollToVisibleType option that allows you to chose whether to scroll the element to the top or bottom of the page. This was introduced because of the static headers that appear over the target element and prevent further actions.

The above mentioned option is missing for some steps, like entering text in RadSearchBox and other controls. I hope that we will be able to fix all of them and add the ScrollToVisibleType option to make the ScrollToVisible more configurable and work well with applications that use a static header.

I see your point about not even scrolling, if the element is already visible on the page. This was something that we considered, but the actual verification whether the element is visible on the page or not will take more time than scrolling to it. Another concern that we had in the back of our minds, was that there might be something we missed and that could break a lot of existing tests. Our current implementation turned out to be the quickest and is backwards compatible.

Thank you for your feedback and for your understanding. I remain available, if you have any follow up questions or suggestions.

Plamen Mitrev
Progress Telerik

The New Release of Telerik Test Studio Is Here! Download, install,
and send us your feedback!
Posted on: 13 Dec 2019 15:20

I'd vote this is a bug since the element is already visible on the page and this scrolling action is what causes the problem, but having this property available would possibly be a workaround.  I don't know if changing the behavior might have other side effects for my tests.

If the goal is to make sure the element is visible, why not detect whether it is already visible before doing any scrolling?  I would think you could determine element position or even use your image detection to look for it before attempting to scroll to it.