injecting-mouse-and-keyboard

Use performMouseInput with the rightClick helper, which is shorthand for click(position, MouseButton.Secondary). Coordinates are node-local, so rightClick(center) clicks the center of the node under test.

Use performKeyInput with withKeyDown(Key.CtrlLeft) { pressKey(Key.S) }. The withKeyDown helper releases the modifier in a finally block, preventing leaked key state across tests if an assertion fails.

Call performMouseInput { enter(center) } to emit a hover-enter event, then assert the resulting HoverInteraction or tooltip visibility. Use exit(Offset(-1f, -1f)) to mimic the cursor leaving the surface.

Repeat events are driven by the input dispatcher's event time, not the Compose frame clock. Use advanceEventTime inside the performKeyInput block; the first repeat fires after 500 ms, then every 50 ms.

Use performMultiModalInput when modalities interleave in one gesture, such as hovering while Shift is held, since all sub-scopes share injection state. For independent actions, separate performMouseInput and performKeyInput calls read more clearly.

No. Mouse input is not interchangeable with touch on Android device tests. Use performClick(), which automatically resolves to a touch tap on Android and a mouse click on desktop.