test-execution-contract

name	test-execution-contract
description	Tier 4 workflow for deterministic test execution planning and evidence capture independent of specific test framework tooling.
tier	operational
godot_version	4.6+
doc_anchors	["godot-docs/tutorials/editor/command_line_tutorial.rst","godot-docs/tutorials/scripting/debug/overview_of_debugging_tools.rst","godot-docs/engine_details/architecture/unit_testing.rst"]
tags	["tests","validation","workflow"]
depends_on	["godot-skills/godot-operational/qa-validation-loop/SKILL.md"]

Test Execution Contract

Use When

• Running validation tests after implementation or refactor changes.

Outcomes

• Test scope progresses from smallest relevant slice to broader coverage.
• Failures are captured with deterministic reproduction context.
• Validation evidence is suitable for automation and review.

Required Rules

• Start with the smallest relevant test scope before broader suites.
• Keep environment and seed inputs explicit for deterministic reruns.
• Capture first failure location and command for every failed run.
• Re-run targeted slice after fixes before full sweep.

Workflow

1. Select test scope (single module -> integration -> full run).
2. Execute with deterministic environment inputs where possible.
3. Capture failures with file/test identifiers and first error.
4. Re-run targeted slice after fixes before broad sweep.

Validation

• Repeat same test command twice and confirm consistent pass/fail result.
• Intentionally fail a known test and verify first failure output is captured.
• Confirm output includes identifiers that CI or scripts can parse.

Failure Modes

• Full-suite-only runs slow iteration and hide local regressions.
• Non-deterministic inputs make failures irreproducible.
• Failure logs omit identifiers, blocking automated triage.

Local Doc Anchors

• godot-docs/tutorials/editor/command_line_tutorial.rst
• godot-docs/tutorials/scripting/debug/overview_of_debugging_tools.rst
• godot-docs/engine_details/architecture/unit_testing.rst