Skip to content

testing.md

Latest commit

 

History

History
50 lines (32 loc) · 1.44 KB

testing.md

File metadata and controls

50 lines (32 loc) · 1.44 KB

Testing

Issue-Flow keeps its test surface small and focused. The main goal is to protect the workflow contract rather than to simulate a full agent runtime.

Test Suites

State machine tests

bash tests/state-machine/run-tests.sh

These tests validate that the state-transition guard allows legal transitions and blocks invalid ones.

Skill loading tests

bash tests/skill-loading/run-tests.sh

These tests validate SKILL.md files, including required frontmatter and structural expectations.

Codex install tests

bash tests/codex-install/run-tests.sh

These tests validate that the Codex installer script exists and can stage the expected local plugin and marketplace layout in a temporary home directory.

Run Everything

bash tests/state-machine/run-tests.sh && bash tests/skill-loading/run-tests.sh && bash tests/codex-install/run-tests.sh

When To Run Tests

  • Run both suites before opening a pull request
  • Run the state-machine suite after changing workflow phases, transition rules, or guard logic
  • Run the skill-loading suite after editing any SKILL.md file or metadata
  • Run both suites when adding a new workflow skill such as a new issue-* phase

If You Change Behavior

If a change affects the visible workflow, do all of the following:

  • update the relevant docs
  • update tests if the contract changed intentionally
  • explain the behavior change in the pull request summary