AutomationDriver in spec test with nullrhi on a build machine- can't click a button because hover isn't working

Hi Epic Friends!

I’ve written some spec tests that create a slate window, push some UI, and use the AutomationDriver to click some buttons. This works when I run tests locally from Rider- even with nullrhi. However, when it runs on the horde node (when I run our full automation suite) I get

[log] LogAutomationDriver: Element found but not located under the cursor: [By::Delegate] None

I’m not sure if this has something to do with the horde agent not having a window manager / cursor at all? How do y’all run tests on nodes like these? Should I just edit the engine and get rid of the hover check? Or are there some commandline params I should pass to make things work?

i’ve actually been thinking it might be nice to make sure the automation driver is more isolated from any real UI devices- even to the point of building a new system that works specifically within a slate window, so I can have multiple tests running on multiple slate windows at the same time- I’d just have to make sure the cursor is properly faked at the right level and isolated. Any thoughts or experience here? Is this a known issue, or do you need more info to repro?

Thanks very much!

Josh

[Attachment Removed]

Steps to Reproduce
use automation driver in a spec test that’s running on a horde node with nullrhi to try to click a slate button. you’ll get

[log] LogAutomationDriver: Element found but not located under the cursor: [By::Delegate] None

[Attachment Removed]

Unfortunately the AutomationDriver does not support null RHI mode.

It may work in some instance but that is not the expectation.

The AutomationDriver tries to interact with the actual placement of the UI element with Mouse events.

That said I believe your issue is the size of the desktop. If the UI element is offscreen, collapsed or accessible through scrolling, the UI element will not behave as expected.

[Attachment Removed]

Hi Jerome-

ok thanks, that’s helpful info! We’ll figure out how to work around those issues.

Best!

Josh

[Attachment Removed]