GoDAM QA

GoDAM : where test cases and QA docs live

All files on main in rtCamp org repos.

GoDAM plugin + Woo

github.com/rtCamp/godam-plugin-automation· 89 spec files
DocumentWhat it is
Automation-Coverage.mdThe test case register and source of truth for maintained cases. Every covered feature in plain language, so non-QA readers can tell what is guarded. Deferred rows link to their blockers.
docs/reference/GODAM_TEST_PLAN.md
GODAM_WOO_TEST_PLAN.md
~280 cases broken down by block and surface, each with a description, expected behaviour and selector.
docs/TEST-CONTEXT.md
docs/PREREQUISITES.md
What each spec needs to run — fixtures, plugins, data — paired with the site state a run assumes.
docs/RUNBOOK.mdHow to run, seed, extend and troubleshoot the suite.
docs/RELEASE-QA-RUNBOOK.md
docs/coverage/FEATURE_PR_PLAYBOOK.md
End-to-end release validation, and what happens when a feature PR arrives.
docs/context/DATA_TEST_IDS.mdThe selector contract the cases depend on. Further per-area flow notes in docs/context/.
docs/releases/Release sign-offs, one per release, archived from the ticket comment. v2.5.0 covers 13 items with ~118 assertions, each recorded as claim → result.
docs/TODO.mdWhat isn’t covered and why, so nothing silently disappears.
qa-dashboard/README.mdCoverage dashboard — tracks 25 GoDAM repos nightly and auto-files a regression issue with the repo owner.

GoDAM Core (Central, the SaaS side)

github.com/rtCamp/godam-core-automation· 44 spec files
DocumentWhat it is
docs/TEST-COVERAGE.mdThe per-spec register — Core’s equivalent of Automation-Coverage.
docs/ISSUES.mdLive defects and environment behaviour on pre-prod, written symptom → cause → action, so failures get diagnosed instead of blindly re-run.
docs/analysis-raw/Per-area surface analysis the cases were derived from — auth, billing, media, video editor, team/sites, livestreams. A writer contract keeps the format consistent.
docs/RUNBOOK.mdHow to run, provision, extend and debug.
docs/releases/Release sign-offs, same format as the plugin side, with a template.
PROJECT_CONTEXT.mdArchitecture and repository structure.
Both repos also carry CLAUDE.md and .claude/skills/ — a task-to-doc router and reusable release-QA / PR-triage skills that drive the runbooks by reference.