test_agent_guides.py
Source file: tests/governance/test_agent_guides.py
Module: tests-governance
Size: 117 lines
SHA-256: 6c0d6e8b68dde5825e07d90f6423c8a88128c370fe32ba8a1ae4aa87f5a9dd4f
Responsibility
Checks project policy and release gate behaviour.
Declared entry points
GuideTests— source line 28.setUp— source line 29.p— source line 32.test_clean_fixture_passes— source line 40.test_missing_guide_blocks— source line 41.test_file_edit_blocks— source line 43.p— source line 44.test_new_file_blocks— source line 45.test_deleted_file_blocks— source line 47.test_renamed_file_blocks— source line 49.test_empty_directory_needs_guide— source line 51.test_missing_todo_blocks— source line 53.test_missing_changelog_blocks— source line 55.test_guide_edit_needs_review— source line 57.test_timestamp_does_not_refresh_content— source line 59.test_short_acknowledgement_rejected— source line 61.test_edit_requires_updated_todo_and_log— source line 63.test_reviewed_edit_passes— source line 66.test_symlink_escape_blocks— source line 72.test_missing_registry_blocks— source line 74.test_unknown_compare_base_blocks— source line 76.test_history_release_seal_exclusion_does_not_exempt_real_history— source line 78.test_dependency_cache_exclusion_explicit— source line 84.test_unrecognised_generated_directory_not_excluded— source line 87.
Imports and dependencies
- Line 3:
import json - Line 4:
import subprocess - Line 5:
import sys - Line 6:
import tempfile - Line 7:
import unittest
Behaviour and audit locations
- Line 24:
Run success, cancellation, timeout and permission tests before acknowledging source edits.
Relationship to the system
This page is the file-level source reference, not the architecture rationale. Read the module explanation, the corresponding architecture decision and user guide before changing behaviour. Names and line locations above are extracted from this exact source version; they are reference points, not proof that an external service or a phone feature works.
Change verification
Review the entry points and errors in this file, then run the module’s associated tests, source dependency gate, history gate and documentation coverage check. If the file changes an API response, user interaction, data model, deployment or third-party dependency, revise those human explanations and disaster recovery/licensing when relevant. Do not infer actual native or external API operation from source presence.