Mechanical port to the assertion-only contract (no softened/skipped assertions): install uses live_app + generic.assert_serving (extend) + the recipe's http/playwright/api checks; upgrade seeds its data marker then generic.do_upgrade + asserts survival; backup/restore split into test_backup.py (seed->do_backup->mutate) + new test_restore.py (do_restore->assert original). Recipe-specifics preserved verbatim (keycloak realm+admin-console+kc_admin, matrix/lasuite db-service psql markers, cryptpad/n8n volume markers). No recipe now double-deploys under the deploy-once orchestrator. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
25 lines
1.1 KiB
Python
25 lines
1.1 KiB
Python
"""cryptpad — RESTORE overlay (Phase 1d, DG4): data-integrity, extends the generic restore.
|
|
|
|
Runs after the backup overlay (test_backup.py) on the SAME shared deployment, which left the
|
|
cryptpad_data marker mutated to "mutated" after backing up "original". This restores the snapshot via
|
|
the shared op helper (`generic.do_restore`, which also asserts the app is healthy + serving
|
|
afterwards), then asserts the volume data returned to the pre-mutation "original" — the app-specific
|
|
data integrity the generic restore cannot check. Reads the marker via `exec_in_app` (data isn't
|
|
HTTP-served). Assertion-only (no deploy/teardown)."""
|
|
|
|
import os
|
|
import sys
|
|
|
|
sys.path.insert(0, os.path.join(os.path.dirname(__file__), "..", "..", "runner"))
|
|
from harness import generic, lifecycle # noqa: E402
|
|
|
|
MARKER = "/cryptpad/data/ci-marker.txt"
|
|
|
|
|
|
def test_restore_returns_state(live_app, meta):
|
|
domain = live_app
|
|
generic.do_restore(domain, meta) # restore + assert healthy/serving
|
|
assert (
|
|
lifecycle.exec_in_app(domain, ["cat", MARKER]).strip() == "original"
|
|
), "restore did not return the pre-mutation state"
|