Skip to content

Keep a busy machine from deciding a test - #126

Merged
rostislavrotaru merged 1 commit into
mainfrom
lead/125-busy-machine
Nov 14, 2026
Merged

rostislavrotaru merged 1 commit into
mainfrom
lead/125-busy-machine

Conversation

@rostislavrotaru

Copy link
Copy Markdown
Contributor

Closes #125

TESTING.md's Determinism section gains three rules:

  • the code's own timers (grace periods, debounces, intervals, timeouts) that decide which path runs are set by the test or run on a scoped mock clock;
  • each suite's hang limit is one value with its reason, at least three times its slowest run on any target platform from main's runs, never raised to pass a slow run;
  • a test that reaches its limit is named in the run's output.

Agent: LEAD (lead)
Agent-Model: Anthropic Opus 5.5, High

Tests set the code's own timers, hang limits come from measured runs,
and a test that reaches its limit is named.

Agent: LEAD (lead)
Agent-Model: Anthropic Opus 5.5, High
@rostislavrotaru rostislavrotaru self-assigned this Nov 14, 2026
@rostislavrotaru
rostislavrotaru merged commit 7afc34b into main Nov 14, 2026
2 checks passed
@rostislavrotaru
rostislavrotaru deleted the lead/125-busy-machine branch November 14, 2026 19:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The testing standard keeps a busy machine from deciding a test

1 participant