EventGenerator does not work correctly for views-tests, since in most of these tests, it operates on the root-window set-up by the TestScreen instance. However, since the Widgets (and their backing aura window trees) are disconnected from that, the events generated from EventGenerator do not reach their intended targets.
Additional issue: once EventGenerator is used to move the mouse, it doesn't update display::Screen::GetCursorScreenPoint(). This is because ScreenMus::GetCursorScreenPoint() looks at a memory shared with mus-ws, and EventGenerator only moves the cursor in client-local space (i.e. mus-ws isn't aware of this change). So tests that depend on this directly or indirectly (e.g. View::IsMouseHovered()) does not work correctly.
EventGenerator now works with mus. In chrome code, if you create an EventGenerator with a null window, the EventGenerator will end up sending events over mojom to ash. We may want to add some cover functions that abstract this way, but that can be done separately.
Comment 1 by sadrul@chromium.org
, May 28 2016