Learn by doing

AutoSimulatedMouse
User guide & practice

Place a MousePot on a live control below. Choose an action in the extension, press Run, and watch the result here.

Covers the 0.21 action set. Update your extension if an option is missing.

  1. Open the panelInstall from Chrome Web Store, open this page in Chrome, then open AutoSimulatedMouse.
  2. Place a pointClick AddPt (Add when collapsed). Drag the point onto a control. Where brings it into view, shows a free cursor trail, then pulses it three times. Stop a running sequence before locating.
  3. Choose & runChoose an action and its settings. Pro: use Run n× = 1 for one pass. Free: use a short duration, then Stop.
Two input modes

Page events sends JavaScript events to webpage controls. Browser input uses Chrome's input mechanism for supported clicks and native pickers; Chrome shows a debugging notice during the run. Neither is an operating-system mouse controller.

Practice scenarios inspired by Automation Testing Practice. This is an independently built AutoSimulatedMouse guide, not a copy of or affiliation with that website. Demo data stays in this page and is cleared on reload.

Practice choices such as Canada, Blue and Green stay in English so the example values match in every language.

01

Mouse / Page events or Browser input

Left click

Use on webpage buttons, checkboxes, radio buttons and links. Place the point at the center of the control.

Try this
Action: Left click. Interval to next point: 1000 ms. Run one pass.
Expected
The page counter increases by 1. Running again adds another click to this counter.

A synthetic click does not necessarily open a native calendar or select popup. Use Open picker for those controls.

Live target0 clicksUnchecked
02

Mouse / Page events or Browser input

Right click

Use on an element with a webpage context-menu handler. This example displays its own menu, without navigating away.

Try this
Place a point on the purple target and choose Right click.
Expected
The page's context menu opens and the event counter increases.

Page events can trigger a site's menu, but do not open Chrome's own context menu. Browser menus are outside the page.

Webpage context menu0 context menus opened
03

Mouse / Page events or Browser input

Double click

Use when a webpage listens for a double-click, such as an edit or copy action.

Try this
Put a point on Copy text. Choose Double click, then Run once.
Expected
The source text appears in the result field. A Left click alone does not copy it.

Page mode sends two clicks with increasing detail and a dblclick event. It is not an OS-level double-click.

04

Mouse / Page events or Browser input

Triple click

Use on controls that explicitly handle three consecutive clicks. There is no standard DOM triple-click event; sites can check click detail.

Try this
Choose Triple click on the green target.
Expected
The target receives a click with detail = 3, updating the result.

Text selection depends on the website and input mode. This example verifies the event sequence, not paragraph selection.

Three-click target0 triple clicks
05

Mouse / Page events

Repeat click

Repeat left clicks at the same point. This does not hold the mouse button down.

By count
Set duration to 2000 ms and count to 5. With Run n× = 1, expect 5 clicks; 2 passes produce 10.
By interval
Set duration to 2000 ms and interval to 500 ms. Timing controls the result; it is not an exact-count mode.

A duration-based run may stop partway through this action. For exact counts, use By count with Run n×. Very slow webpages can extend a count-based pass.

Cumulative page counter0 clicks
06

Mouse / Page events

Move in range

Move around a point without clicking or holding a button. Use for hover and mouse-move handlers.

Try this
Place a point in the center of the grid. Choose Move in range, duration 2000 ms, range 40 px.
Expected
The crosshair follows mousemove coordinates inside the grid. Clicks remain 0.

This is not drag-and-drop or slider dragging. Page-mode movement is a virtual cursor and does not guarantee CSS :hover behavior.

Movement area
Move events: 0 · Clicks: 0
07

Form / Text entry

Insert text

Use on an editable input, textarea or contenteditable element. Place the point inside the text area, not on its label or border.

Try this
Text to insert: Hello. Typing speed: 80 ms per character. Time to next point: 1000 ms.
Expected
Hello is appended to the current content and input/change events update the preview. Reset before repeating if you want an empty field.

Read-only, disabled and non-editable targets fail precheck. Use Set date or Choose dropdown option for typed values in those controls.

No input yet
08

Form / Open without selecting

Open picker

Open a calendar or dropdown without entering text or selecting a value. This is the renamed Select Option action.

Native date / dropdown
Choose Browser input and place the point inside either native control. Run once: its picker should open without changing the value.
Webpage calendar
Use Page events on the jQuery UI fields in the Set date example below; focusing the field opens the webpage calendar.

Native popups are not webpage DOM. Do not place a second page point inside a native popup; choose a value with Set date or Choose dropdown option instead. Chrome may restrict picker opening.

No value selected
09

Form / Native select elements

Choose dropdown option

Select an item directly, without opening the popup. Supports native single-select and multi-select lists.

One option
Place the point on Country. Match by Text: Canada; Value: ca; or Position: 2. Positions start at 1.
Multiple options
Place the point inside Colors. Match by Text, with Blue and Green on separate lines. The old selection is replaced.

Use the webpage's actual value, not a guessed abbreviation: Germany uses de in this example. If unsure, match the full option text. Matching is case-sensitive. Missing, disabled or ambiguous options fail validation. For custom menus, use Open picker then Left click on an item.

Country: United States · Colors: none
10

Form / Native date & jQuery UI

Set date

Set a date directly. The extension uses native date values or the supported widget API instead of typing blindly into a text field.

Try this
Choose Set date, select October 15, 2026 in the extension, and place the point on any date field here.
Expected
US format: 10/15/2026. Day-first format: 15/10/2026. Native value: 2026-10-15; its visual format follows your browser locale.

The day-first field is read-only but uses a supported jQuery UI widget. A generic read-only input is not supported. All demo dates are limited to 2026. Native min/max/step and supported widget restrictions are checked.

Native date range
No date set

Running your workflow

One pass is not always one click.

Page-event clicks, text entry, dropdown selection, date setting, webpage picker focus and range movement continue on their original targets outside the viewport, without scrolling back. Browser input keeps its mode but stops and asks you to bring the point back into view. Removed, hidden, disabled or covered targets stop the run. Native picker restrictions still apply; background-tab timing is not guaranteed.

Until duration
The list repeats until the time budget is reached. A short run can stop in the middle of an action.
Run n× (Pro)
A pass visits every point in order. Left click does one click, Double click does two, and Repeat click does its configured work. Run n× = 1 does not reduce all actions to a single click.
Which counter?
The extension's point counter resets at the start of each Run. This page's counters accumulate until you click Reset or reload. Use the page counter to verify that repeated runs really fire clicks.
Time input
Time fields accept milliseconds, expressions such as 20*60*1000, and units such as 20h, 30m, or 1.5s. The extension shows the converted value while you edit.
Timing
For click actions, the interval to the next point starts after the click action finishes; mouse travel does not shorten this wait. The final click point of the final count-based pass has no trailing wait. Text entry must finish before moving on.
Pause & Stop
Run is disabled while the extension is running. Pause suspends the current run; Stop ends it. After a new extension version loads, refresh your test page and add new points if old points cannot be controlled.

Compatibility & troubleshooting

Choose the action for the control.

A click has no visible effect

Check the point position with Where. A plain click cannot guarantee native picker opening or a site's default mouse behavior. Try Browser input for supported click actions, Open picker to open a control, or a direct-value form action. A disabled control or a site rejecting synthetic events may still refuse the action.

The precheck reports an invalid target

Move the point inside the editable field or native select. Insert text cannot target a button. Set date accepts native date inputs and initialized jQuery UI datepickers, not every text input. Choose dropdown option accepts native select elements, not custom listbox markup.

What is not demonstrated or supported here?

This guide does not automate Chrome's interface, CAPTCHA challenges, file dialogs, OS windows, native alerts, cross-origin iframes, drag-and-drop or slider dragging. Opening a picker does not guarantee access to every third-party widget. Successful tests here do not guarantee compatibility with all websites.

Will these examples submit my information?

No. These controls are local demonstrations with no form submission, payment, storage or analytics. Use sample text, not passwords or personal information. Reloading clears the results.

Reference: Automation Testing Practice. The form, date and double-click practice concepts are adapted into original examples for this product. jQuery and jQuery UI are bundled under the MIT license; see third-party notices.