Files
cc-ci/tests/hedgedoc/PARITY.md
autonomic-bot 242d56b56e
Some checks failed
continuous-integration/drone/push Build is failing
claim(mirror): Ph1+Ph2+Ph3 complete — mirrors created, hedgedoc tests, 9 recipes enrolled
Phase 1: Create 3 missing Gitea mirrors (lasuite-drive, mailu, mumble) via API + force-sync
  upstream main (f4135d78, 23309a1a, 9fa5e949). All 3 return 200/empty=false from Gitea API.

Phase 2: Author tests/hedgedoc/ (uptime-kuma template) — recipe_meta.py, functional/
  test_health_check.py (GET / → 200/302), functional/test_branding.py (brand markers),
  PARITY.md. Generic tiers cover install/upgrade/backup baseline.

Phase 3: Enroll 9 unenrolled recipes in nix/modules/bridge.nix POLL_REPOS:
  bluesky-pds, discourse, ghost, immich, lasuite-drive, mailu, mattermost-lts, mumble, plausible.
  Final POLL_REPOS: 20 entries (cc-ci + 19 recipes).

Gate Ph4 CLAIMED: operator must run `nixos-rebuild switch --flake .#cc-ci` on cc-ci after
Adversary-verifies Ph1+Ph2+Ph3. See STATUS-mirror.md for exact repro.
2026-06-02 00:25:12 +00:00

38 lines
1.9 KiB
Markdown

# Parity — hedgedoc
HedgeDoc (formerly CodiMD) is a collaborative real-time markdown editor. It is a single-service
app backed by sqlite (default) or PostgreSQL, with a Node.js backend on port 3000.
The upstream recipe-maintainer corpus (`recipe-info/hedgedoc/tests/`) does not exist, so this
PARITY.md documents the cc-ci-authored suite as the baseline.
## Recipe-specific tests (Phase mirror, ≥2 functional tests)
HedgeDoc's defining behaviors:
- Root path (`/`) responds 200 or 302 (redirect to `/login` or `/new` depending on auth config).
- Served HTML contains HedgeDoc/CodiMD branding markers + bundled JS/CSS assets.
| cc-ci file | what's verified | rationale |
|---|---|---|
| `tests/hedgedoc/functional/test_health_check.py` | `GET /` → 200 or 302 | Proves the app is up and routing through Traefik. A wedged HedgeDoc returns 5xx or no response. |
| `tests/hedgedoc/functional/test_branding.py` | `GET /` HTML contains hedgedoc/codimd/hackmd markers OR bundle asset refs | Distinguishes "HedgeDoc is serving its own content" from "fallback page." A misrouted or empty backend lacks these markers. |
## Backup data-integrity
The default compose.yml includes `backupbot.backup=${ENABLE_BACKUPS:-true}`. HedgeDoc stores data
in `codimd_database` (sqlite) and `codimd_uploads` volumes. The generic backup tier verifies a
snapshot artifact is produced. Recipe-specific backup data-integrity overlay (ops.py +
test_backup.py) is deferred; the generic tier suffices for initial enrollment.
## Playwright
Not yet authored. A Playwright flow would create an anonymous note, assert the content persists,
and verify the collaborative editor loads. Deferred — the current functional tests plus the
generic Playwright `assert_serving` pass the enrollment bar.
## Deferred
- Playwright note-creation + persistence flow
- ops.py pre_backup/pre_restore with note content verification
- PostgreSQL variant (`compose.postgresql.yml`) — current tests target sqlite (default)