PROD Hermes Workspace
76 pages 76 clean 0 need attention
Page navigation 76

Project

Domains

Folders · apps/

Folders · docs/

Folders · knowledge/

Folders · ops/

Folders · packages/

Folders · scripts/

Folders · tests/

Folders · pods/

Folders · tools/

Shared

Metadata clean
Route
/knowledge/portal/project/folders/tests
Source
knowledge/portal/project/folders/tests.md
Covered files
0
Last generated
unknown

tests/

State: folder wiki page generated by deterministic sync

Folder: tests/

What

tests/ contains root test suites for cross-package/system-level regression coverage. This boundary currently has 14 direct file(s) and 0 direct subfolder(s).

Does

It contains automated checks that validate behavior contracts and guard regressions (dominant direct file kinds: .py:13, .md:1).

Why

Reliable tests are the safety net that keeps migration velocity high without breaking runtime behavior.

Subfolders

  • (no direct subfolders)

Files

  • README.md — What: tests/ contains root test suites for cross-package/system-level regression coverage. This boundary currently has 14 direct file(s) and 0 direct subfolder(s). Does: It contains automated checks that validate behavior contracts and guard regressions (dominant direct file kinds: .py:13, .md:1). Why: Reliable tests are the safety net that keeps migration velocity high without breaking runtime behavior.
  • test_backup_restore_drill_scheduler.py — What: Tests backup restore drill scheduling behavior in ops/scripts/backup_restore_drill.py. Does: Verifies scheduler tick execution when due and skip behavior when cadence window is still active. Why: Prevents regressions in TASK-205 automated drill cadence and state persistence contract.
  • test_backup_restore_verification.py — What: Tests automated backup restore verification behavior in ops/scripts/backup_restore_drill.py. Does: Verifies disposable restore validation succeeds for healthy backups and fails when restored data drifts. Why: Protects TASK-197 backup restore verification automation contracts (schema, row-count, checksum, retention).
  • test_compose_sampler_entrypoint.py — What: Compose sampler entrypoint contract tests for ops/compose stack definitions. Does: Verifies dev/prod sampler services execute the real dashboard sampler module and reject stale root-level sampler paths. Why: Prevents promotion drills from silently passing with a restarting sampler container due to a broken command path.
  • test_compose_secret_delivery_pipeline.py — What: Contract tests for TASK-157 SOPS+Age compose secret delivery pipeline. Does: Verifies compose lanes are wired to materialized secret env files and validates authorized vs unauthorized decryption behavior. Why: Prevents plaintext secret drift and ensures only authorized age keys can materialize compose runtime secrets.
  • test_env_isolation_check.py — What: Automated contract tests for ops/scripts/env_isolation_check.py. Does: Verifies complete DEV/TEST Hermes lane matrix passes and missing/colliding lane bindings fail. Why: Proves environment-isolation guardrails catch real lane misconfiguration before promotion claims.
  • test_gemma4_benchmark.py — What: Unit tests for TASK-222 Gemma 4 benchmark evidence script. Does: Verifies available, deferred, and ruled-out benchmark states without calling live Ollama. Why: Keeps model benchmark evidence generation deterministic and aligned with small-profile operations policy.
  • test_legacy_artifact_report.py — What: Python module for test legacy artifact report behavior in tests. Does: Implements runtime logic, API contracts, or automation helpers used by this lane. Why: Concentrates boundary logic so agents can reason about impact quickly.
  • test_nginx_tls_contract_check.py — What: Tests for TASK-241 nginx TLS contract probe script. Does: Verifies positive and negative aggregation paths plus strict exit behavior. Why: Keeps TLS/certbot/security-header evidence checks trustworthy before operator use.
  • test_portal_monitoring_scripts.py — What: Tests for ops monitoring scripts used by admin drift/smoke APIs. Does: Verifies DEV theme contract checks, tailnet parity skip behavior, and Ollama warmup timing telemetry. Why: Covers TASK-144, TASK-149, and TASK-199 smoke assertions without requiring online tailnet access.
  • test_secrets_hygiene_gate.py — What: Tests for TASK-209 secrets hygiene gate script. Does: Verifies plaintext secret scan and rotation evidence freshness checks for pass/fail and override paths. Why: Keeps CI and promotion gates enforceable without manual inspection.
  • test_secrets_inventory_check.py — What: Python module for test secrets inventory check behavior in tests. Does: Implements runtime logic, API contracts, or automation helpers used by this lane. Why: Concentrates boundary logic so agents can reason about impact quickly.
  • test_wiki_sync.py — What: Python module for test wiki sync behavior in tests. Does: Implements runtime logic, API contracts, or automation helpers used by this lane. Why: Concentrates boundary logic so agents can reason about impact quickly.
  • test_zero_shim_cleanup.py — What: Zero-shim import boundary tests for Portal/TzenBoard runtime ownership. Does: Detects forbidden imports of retired scrumai shim modules and verifies active code paths avoid those legacy modules. Why: Prevents regressions back into compatibility shims after TASK-224 cleanup.