UI Automation Add-in object recognition time is 300% above MSAA with Excel 2016 as AUT on Windows 10
Question ID: 108137
1
0

Using UFT 14.02. Not able to use scripts with UI Automation add in due to unreasonably long times it takes for the script to query UI Automation object hierarchy. Scripting just a simple test to use ".Exist(0)" on Excel window, Ribbon and Titlebar using UI Automation add-in technology and Standard Window tech (MSAA), in some cases the timings for UIA are 300% and above that of in some cases then MSAA.

Marked as spam
Posted by (Questions: 424, Answers: 91)
Asked on January 30, 2018 10:57 pm
116 views
Answers (3)
1
Private answer

There are known limitations specifically when using Windows 10 and UI Automation:

https://admhelp.microfocus.com/uft/en/14.02/UFT_Help/Content/User_Guide/Trb_Lim_UIAutomation.htm

''Known Issues - UI Automation Support: UI Automation on Windows 10 - UI Automation recording and UI Automation spy mode can experience unexpected behavior when running UFT on Windows 10. (Note that these functionalities are not officially supported for UFT running on Windows 10.)''

Until these issues are ironed out, Micro Focus suggests using Windows 7 instead when using Office 2016 as your AUT under UI Automation.

Marked as spam
Posted by (Questions: 0, Answers: 771)
Answered on January 30, 2018 10:59 pm
0
That's a bummer. I'll try Windows 7 but hope that UI Automation is officially supported in Windows 10 in the future.
( at January 30, 2018 11:01 pm)
0
Private answer

This issue was reported by an Automation engineer in my organization. We've been working with Orasi and Micro Focus on it. We have a live session scheduled with them this week. Hope something comes of that. This has been a major pain. Micro Focus documentation states that UFT 14.x is compatible with Office 2016. Sounds like they may have made some mutually exclusive statements.

Marked as spam
Posted by (Questions: 0, Answers: 2)
Answered on January 30, 2018 11:12 pm
0
Private answer

The fact that we are replatforming to Win10/Office 2016 is the very reason we need it to work. We're trying to refresh our smoke test repository. I'm a little surprised, as Win10 and Office 2016 have been out for quite a while.

Marked as spam
Posted by (Questions: 0, Answers: 2)
Answered on January 30, 2018 11:17 pm
EyeOnTesting

Welcome back to "EyeOnTesting" brought to you by Orasi Software, Inc.

X
Scroll to Top