Skip to content

Add TEST.md: upgrade-testing methodology#23

Merged
wnstfy merged 1 commit into
mainfrom
docs/upgrade-test-methodology
May 21, 2026
Merged

Add TEST.md: upgrade-testing methodology#23
wnstfy merged 1 commit into
mainfrom
docs/upgrade-test-methodology

Conversation

@wnstfy

@wnstfy wnstfy commented May 21, 2026

Copy link
Copy Markdown
Contributor

Summary

New repo doc codifying the pre-flight testing methodology for high-risk dependency bumps that the PR CVE gate alone can't catch.

Scope:

  • Major image bumps (mariadb 11 → 12, redis 7 → 8, mongo 7 → 8).
  • On-disk format changes.
  • Major bumps of trusted CI Actions.

Patch image bumps and application-image bumps stay covered by the existing CVE gate; this is the extra-care path layered on top.

Hard rules (codified)

  • All test artefacts in /tmp/upgrade-tests/<n>/ only.
  • Tests MUST NOT collide with running stacks: explicit tmp-test- prefix on compose project / container / network names, no ports: host bindings, no named volumes, bind mounts only into /tmp.
  • Test credentials must be obvious placeholders.
  • Cleanup is conditional: only on success (zero error logs, all checks green). Failed tests leave artefacts in /tmp for investigation.
  • Every test that follows this methodology must land a ### Verified block in CHANGELOG.md [Unreleased] before the Renovate upgrade PR merges.

Test plan

  • `actionlint` n/a (no workflow changes).
  • `scan`, `misconfig` pass — doc-only change.
  • After merge, run the first round of tests under this methodology on the queued Renovate upgrades (mariadb 12, redis 8, mongo 8.3, rabbitmq 4.3, stoatchat 0.13.6, plus the major action bumps) — capture results to /tmp and add a Verified block to CHANGELOG.

Documents the extra-care path for high-risk dependency bumps
that the PR CVE gate alone can't catch:
- major image bumps (mariadb 11->12, redis 7->8, mongo 7->8)
- on-disk format changes
- major bumps of trusted CI Actions

Codifies the isolation rules tests MUST follow so they cannot
interact with running production stacks: /tmp-only artefacts,
explicit tmp-test- prefixes on project/container/network names,
no host-port bindings, no named volumes, no real credentials.

Per-test structure (seed -> stop -> upgrade -> verify -> report)
with conditional cleanup (only on success) so failed runs leave
artefacts in /tmp for inspection.

Each upgrade that follows this methodology must add a Verified
line to CHANGELOG.md [Unreleased] before the Renovate PR merges.
@wnstfy
wnstfy enabled auto-merge (squash) May 21, 2026 12:22
@github-actions

Copy link
Copy Markdown
Contributor

Trivy misconfiguration findings (HIGH + CRITICAL)

✅ No HIGH or CRITICAL misconfigurations detected.

@wnstfy
wnstfy merged commit 95a533e into main May 21, 2026
3 checks passed
@wnstfy
wnstfy deleted the docs/upgrade-test-methodology branch May 21, 2026 12:22
wnstfy added a commit that referenced this pull request May 21, 2026
TEST.md describes the maintainer's internal pre-flight upgrade-
testing methodology, not project-facing documentation. It was
added in #23 but should not have been committed publicly.

Local content is preserved off-repo for ongoing use.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant