test_disaster_recovery_gate.py

Source file: tests/governance/test_disaster_recovery_gate.py

Module: tests-governance

Size: 49 lines

SHA-256: 7c6f4b8c108abcb1e89ef3edffe46b77bad1f965c772a9d077c6e209d2aa73ca

Responsibility

Checks project policy and release gate behaviour.

Declared entry points

• RecoveryGateTests — source line 13.
• setUp — source line 14.
• tearDown — source line 32.
• test_clean_evidence_passes — source line 35.
• test_changed_command_blocks — source line 36.
• test_new_history_requires_review — source line 39.
• test_stale_wp_page_blocks — source line 42.
• test_missing_topic_blocks — source line 45.

Imports and dependencies

• Line 2: import importlib.util
• Line 3: import json
• Line 4: import tempfile
• Line 5: import unittest

Behaviour and audit locations

Review control flow and returned values in the named source file; no special integration marker was detected.

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.