First client side (use browser storage to limit across tabs), but server side is also needed to guarantee limiting.
The number of times one can request a job run per period should be controllable by system admins. Maybe even on course-level.

Update:
It’s managed server-side. Administrators can control the global setting for burst (3 by default) and wait time (10s to get a new ‘run test’-credit)
When reaching the rate-limit (run-credit at 0) after pressing one of the run-buttons, it will:

• style the run-buttons as disabled (only decorative, they’re still functional)
• show a greyish information message within the console that one has to wait 10s before starting a new run
• in case run-button is clicked within the wait time, display an alert message that one is exceeding the rate limit (run won’t be executed)

The administration page is extended with settings to control the burst and wait time. It also displays number of times rate limit has been exceeded since start or since change of rate limit settings.

Submitted by Elmer van Chastelet on 24 May 2023 at 10:38