test-execution-contract

Plan and execute deterministic validation tests with reproducible failure capture.

2|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/DubDev720/gdref --skill test-execution-contract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-execution-contract
Source: https://github.com/DubDev720/gdref/tree/main/godot-skills/godot-operational/test-execution-contract
Command: npx skills add https://github.com/DubDev720/gdref --skill test-execution-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of running validation tests, ensuring that test execution is deterministic and that failures are captured with clear, reproducible context, independent of specific testing frameworks.

Core Features & Use Cases

  • Scoped Test Execution: Plan and execute tests starting from the smallest relevant scope and expanding coverage.
  • Deterministic Inputs: Ensure test runs are reproducible by managing environment and seed inputs explicitly.
  • Failure Capture: Reliably record the first failure location and the exact command needed to reproduce it.
  • Use Case: After refactoring a module, use this Skill to run targeted tests, capture any regressions with precise details, fix them, and then re-run the affected slice before a full suite validation.

Quick Start

Use the test-execution-contract skill to plan and execute validation tests for the multiplayer module.

Frequently Asked Questions about test-execution-contract

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make test execution deterministic after refactoring a module?

Deterministic test execution is achieved by explicitly managing environment and seed inputs. This Skill plans validation workflows to ensure test runs are reproducible, capturing the first failure location and the exact command needed to replicate it.

What is scoped test progression and how does it improve regression testing?

Scoped test progression starts validation from the smallest relevant code slice and expands coverage. It improves regression testing by isolating affected slices, fixing failures first, and then running a full suite validation for reproducible context.

How do I capture reproducible failure context during validation workflows?

Reproducible failure context is captured by logging the first failure location and the exact reproduction command. This approach relies on deterministic inputs and explicit environment management to reliably record actionable failure details.

Can I use this for post-implementation testing with any testing framework?

Yes, this framework-agnostic approach supports post-implementation testing phases. It applies deterministic test execution planning and evidence capture independent of specific testing frameworks to ensure reproducible validation workflows.

What's the best way to plan validation tests for reproducible runs?

The best way to plan validation tests is by enforcing explicit input management and scoped test progression. This ensures deterministic test execution by starting with the smallest relevant scope before expanding to full suite validation.