Files
computer-playbook/docs/agents/action/testing.md
T
kevinveenbirkenbachandClaude Sonnet 4.6 821c3c53b6 feat(pre-commit): introduce pre-commit hook enforcement and modular environment test suite
- Add .pre-commit-config.yaml running make test on non-doc changes
- Add pre-commit to pyproject.toml dev dependencies
- Add scripts/install/pre-commit.sh for hook registration
- Add install-python-dev Makefile target; wire into environment-bootstrap
- Rename setup-development → mark-development (env.ci override marker)
- Refactor scripts/tests/environment.sh into modular 00–10 scripts with orchestrator
- Add 09_commit.sh validating pre-commit enforcement and --no-verify bypass
- Update docs/agents/action/commit.md and testing.md for new hook behavior
- Update makefile.md, setup.md, installation.md accordingly

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-04-08 16:58:24 +02:00

1.5 KiB

Testing

Test Changes

  • After every change to a test file, you MUST run the specialized test for that file using TEST_PATTERN before continuing with any further action. See Unit Tests, Integration Tests, and Lint Tests for examples.
  • You MUST NOT run more than one unit test command at the same time. Unit tests MUST be executed serially, never in parallel.
  • If a new test is created or an existing test has been changed since the last test run, you MUST rerun it after every subsequent action until it passes.
  • If the last test run for a test failed, you MUST rerun it after every change until it succeeds.

Commits

  • make test is enforced automatically by the pre-commit hook before every commit for changes that include at least one file that is not .md, .rst, or .txt. You do NOT need to run it manually.
  • For markdown/reStructuredText/text-only changes, the hook skips make test automatically.
  • If the pre-commit hook warns about a staged file or its role, you MUST ask whether to fix that warning before you continue.
  • Keep the follow-up limited to the roles touched by staged files so the change stays focused.

On Failure

  • If that validation fails, you MUST run make clean and rerun it.
  • If the failure says service "infinito" is not running, restart the stack with Development Environment Setup and retry the validation.