Test Runner

Who the node is. The id is the key the DOT pins.

id

test-runner

name

Test Runner

type

validation

phases

Testing

What it does, and the prose the agent is handed when the graph runs.

action35 words

Run the suites the review calls for against the PR head and gate on the result: green releases the report to the maintainer, red hands the failing cases back to the drafter for another pass.

spec127 words

Read the drafted review you are handed, take the test suites it names, and run exactly those against the pull request's head ref, no more, no fewer. Give the whole run thirty minutes; a suite still executing when that expires counts as a failure, not as a pass. Emit green on result when every suite passes and red otherwise, carrying the failing-case count so the branch downstream can read the outcome without opening the write-up. Emit that write-up on report: suite names, durations, every failing case with its assertion and stack trace, and the coverage delta against the base ref. Do not edit the code, do not re-run a failing suite hoping for a different answer, and do not judge whether the change deserves to be merged.in full above

model

claude-haiku-4-5

agent

Test runner

skill

skills/test-runner.md

tools

CI, Git

mcp

github

params

timeout_s: 1800, max_retries: 3

What arrives, what leaves, which nodes it expects to hear from, and what may not.

inputs

review : markdown

outputs

result : status, report : report

dependencies

review-drafter

cannot

no type is refused

will_not

edit the code under test, re-run a failing suite hoping for a different answer

The keys the static analysis reads. Nothing here instructs the agent.

risk_markers

none

notes84 words

max_retries: 3 bounds the draft/test loop at three attempts beyond the first, four runs of the suites in all. The number crosses over from max_iterations unchanged, and that is the point: nothing on this card promises a count of attempts, so re-reading it as engine spec §2.6's "additional attempts" leaves what a run does exactly where it already was. Drop it and the pair still terminates in practice, but the static analyzer has nothing to read and charges the blueprint for an unbounded loop.

The card's own version, and who wrote it.

version

1.1.0

author

autogen

provenance

not stated