2026-04-29 19:48:14 +00:00
|
|
|
# uptimerunner-basic
|
|
|
|
|
|
|
|
|
|
This scenario verifies the first concrete uptime.link runner flow:
|
|
|
|
|
|
|
|
|
|
1. A target HTTP service responds with `healthy`.
|
|
|
|
|
2. A fake uptime.link coordinator exposes the runner protocol.
|
|
|
|
|
3. The runner polls `/api/runner/v1/checks`.
|
|
|
|
|
4. The runner executes the assigned HTTP check locally.
|
|
|
|
|
5. The runner posts the result to `/api/runner/v1/results`.
|
2026-04-30 07:13:20 +00:00
|
|
|
6. The scenario verifies scheduling, status derivation, snapshot restore,
|
|
|
|
|
unauthorized access rejection, token rotation, disabled runner rejection, and
|
|
|
|
|
label updates.
|
