I use WinAppDriver to automate button click. To avoid performance hit, instead of using "app", "root", I use
capabilities.SetCapability("appTopLevelWindow", topLevelWindowHandle);
Still finding an element by it's Id or Name takes more time (around 5 seconds initially) and the problem gets worse when WinAppDriver runs continuously for more than 30 minutes or 1 hour.
It is clear from Task manager that memory consumed by the application (which is automated) continues to grow for each function call on WindowsDriver object.
I use WinAppDriver to automate button click. To avoid performance hit, instead of using "app", "root", I use capabilities.SetCapability("appTopLevelWindow", topLevelWindowHandle);
Still finding an element by it's Id or Name takes more time (around 5 seconds initially) and the problem gets worse when WinAppDriver runs continuously for more than 30 minutes or 1 hour.
It is clear from Task manager that memory consumed by the application (which is automated) continues to grow for each function call on WindowsDriver object.
Please check and provide a solution. Thanks.