Winappdriver: Performance Issues When Many Elements Are Present

[tobindh]

I am evaluating being able to use WinAppDriver (version 1.1), and I am having some performance issues.

The software I am testing has DataGrids used to display a variety of records. The grid I am currently testing has 23 columns - with 50 rows returned, it took 36 seconds to complete the following locator to find the number of rows (i.e. 50 elements that match) :

Grid.FindElementsByTagName("Custom")

The same grid with only 10 rows returned took almost 8 seconds to complete the same lookup.

CPU and memory aren't being taxed at all while the wait is happening, the driver log is just waiting for a response to the request. Inspect.exe can display the grid tree with all of the rows in seconds. Is having that many elements in the page source just beyond the realm of what WinAppDriver was designed for, or is there something in the works to address performance for these situations?

[hassanuz]

Hi @tobindh,

Thanks for reporting this. We're aware of performance being less than ideal - and this is something we hope to resolve in a future update along with an overhaul of XPath handling.
.

[kfrajtak]

Got the same issue, rolled my own driver :) Check my repo.