Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

test-execution-contract

Étoiles2

Forks0

Mis à jour22 février 2026 à 21:02

Tier 4 workflow for deterministic test execution planning and evidence capture independent of specific test framework tooling.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

DubDev720

DubDev720/gdref

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

SKILL.md

readonly

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

Select test scope (single module -> integration -> full run).
Execute with deterministic environment inputs where possible.
Capture failures with file/test identifiers and first error.
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

Plus depuis ce dépôt

même dépôt

foundation-architecture

DubDev720/gdref

Foundational architecture skill for Godot workflows. Defines authority boundaries, composition strategy, scene ownership, command pathways, and replaceability constraints.

2026-02-222

foundation-asset-resource-pipeline

DubDev720/gdref

Foundation rules for deterministic asset import, resource ownership, and reproducible content pipeline behavior.

2026-02-222

foundation-data-interfaces

DubDev720/gdref

Foundational skill for data contracts, resources, interface boundaries, command/result schemas, and deterministic ordering.

2026-02-222

foundation-editor-workflow

DubDev720/gdref

Foundational skill for Godot editor-facing workflows: plugin entry points, menu/settings registration lifecycle, editor UX consistency, and teardown cleanliness.

2026-02-222

foundation-gdscript-system-design

DubDev720/gdref

Tier 1 foundation for game-agnostic GDScript system design: ownership boundaries, signal contracts, composition, and resource-backed configuration.

2026-02-222

foundation-godot-version-doc-alignment

DubDev720/gdref

Tier 1 foundation for strict Godot version/documentation alignment using local pinned docs as source of truth and explicit churn checkpoints.

2026-02-222

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

Select test scope (single module -> integration -> full run).
Execute with deterministic environment inputs where possible.
Capture failures with file/test identifiers and first error.
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