QHuman

Loop one click forever

Record a single click on a big Submit button, then loop it as fast as QHuman will go and watch the huge counter climb. This is the safe version of a load test: a button you own, a counter you control, and a reset key when you want to run it again. Short and satisfying.

record + replay loop counter Free 5 min

This is the same trick behind stress-testing a button in your own app, farming an idle-clicker tap, or just seeing how many clicks a second your machine can push. Record once, loop forever, and let the number run.

Open the target first. It opens in a new tab. Point QHuman at its Submit button and read the counter as it climbs.

Open Stress Button
The whole target: one number, one button. Only clicks that land on Submit count, so the number climbing is proof every looped click is still hitting it. R resets the count to 0 between runs, F hides the page chrome for a clean capture.

Build the macro

  1. Stop recording your mouse path A load test wants the click and nothing else, so before you record, go to Settings in the left rail, open Recording, and untick Record mouse movements. Normally it makes playback glide like a hand. Here it is dead weight: on, every loop replays your whole approach to the button; off, playback jumps straight to the click. Then put the Stress Button tab where you can see it and QHuman both.
    Settings → Recording. Movements ship on, and this is the one lab that wants them off.
  2. Record a single click on Submit Click Record (or Ctrl+F9), then click the big blue Submit button exactly once. Registered clicks goes to 1. That one click is the whole macro: you teach it the spot, the loop does the rest.
  3. Stop and save Press Ctrl+Alt+S to stop, then Save. With movements off, the whole macro is the two rows below: one click is a press and a release, and there is nothing in between for playback to sit through.
    Two rows, one click. Your coordinates will differ. Had you left movements on, a Move row carrying your whole path would sit above these, and every loop would replay it.
  4. Play it once, and watch it stop Before you touch any loop setting, press Play All. One click lands, Registered clicks ticks to 1, and playback ends right there. The first time, that looks broken. It is not: a macro runs a single pass unless you tell it to repeat. The rest of this lab is flipping that one switch.
  5. Now loop it forever That switch is the editor's Playback tab, at the bottom of the right pane. It ships on Play 1 times, which is the single pass you just watched. Pick Loop forever instead. Infinite loops are Free, so run it as long as you like.
    One radio is the entire change. The delays on the right are the gaps QHuman inserts around a run, and Between loops already ships at zero, so the clicks fire back to back with nothing added.
  6. Reset the counter, then Play Press R on the Stress Button page to send Registered clicks back to 0, click back onto QHuman, and press Play All. Hands off, and watch the number run. To stop, use the indicator's Stop, or slam your mouse into any screen corner: the fail-safe is on by default, under Settings → Playback.
Checkpoint

Hands off the mouse, Registered clicks climbs on its own, one per click, and it does not stop until you stop it. Stop playback and it holds; press R and it snaps back to 0 for another run.

If it went wrong

  • Registered clicks stays at 0 The looped click is missing the button. Re-record it squarely in the middle of Submit, and keep the Stress Button tab in the same place, since the macro replays a screen position, not a button.
  • Each loop takes a visible moment Record mouse movements was still on, so the macro is replaying your mouse path before every click. Untick it and record again: the action list should be the two rows above and nothing else.
  • You want it faster still What is left between clicks is your own press-and-hold time. Settings → Playback → Ignore time held during playback fires every action back to back and drops it.
  • It will not stop Loop forever means forever. Use the floating indicator's Stop, or throw the mouse into a screen corner to trigger the fail-safe.

Act 3: the same loop, but polite

Zero delay is the brutal version. The same one-click loop can be gentle instead, and a real button will make you prove it. Open Spam Guard: the same blue Submit button, now behind a one-second double-submit guard, with a Guard pill and an Event log that stamps every attempt accepted or blocked.

Leave the Guard pill on ON and point the same macro at its Submit button. The only thing you change is Between loops, the delay that already read 0.00 Seconds in step 5. Run it at zero, press R to clear, then run it again at anything past one second, and read the log.

Same macro, same button, one number changed. The log reads newest first and numbers every attempt, so the blocked run on the left is the burst being thrown away: the guard only accepts a click a full second after the last one it accepted, and Submissions registered crawls up roughly once a second no matter how hard you hammer it. That is why a human gap between clicks matters.

Keep going

Want more patterns like this one? The use cases guide walks through idle games, QA click-through, form-filling, and more real jobs for a looped macro. Ready for the next lab? Next up is Hotkeys three ways, where you drive a macro by press, hold, and toggle instead of a loop.