This repository owns the default community-health files, organization profile,
and generated portfolio dashboard for
qa-test-automation-frameworks.
The organization has seven public repositories: five frameworks, the shared
Quality Reference Application, and this governance/dashboard repository.
| Evidence | Link |
|---|---|
| Portfolio dashboard | Scheduled evidence dashboard |
| Organization profile | Profile source |
| Repository matrix | Machine-readable source |
| Dashboard assets | Site source |
| Operations decisions | Budgeted operation report and method |
| CI | Dashboard workflow |
The dashboard refresh workflow reads public GitHub metadata and durable evidence records and writes a timestamped, pre-rendered snapshot that remains complete without JavaScript. It separates execution from publication, shows the latest attempt and last success, checks source compatibility and declared freshness, and displays known limitations. It does not claim private adoption, production usage, or organizational outcomes that cannot be independently verified. See the Portfolio Evidence Standard, the runtime policy, the durable-publication status, and the dashboard evidence-state and refresh-health notes. The shared Quality Reference Application is implemented and used by all five frameworks. ADR 007 records the original design decision; the target identity page tracks its current source, image and consumer evidence.
site/data/portfolio.json in this checkout is a committed seed snapshot for local rendering
and testing, not the live evidence record. The scheduled workflow regenerates the deployed
version on GitHub Pages; check generatedAt in the deployed file, not this one, for current
freshness.
Retained operation windows and release packets are indexed under
portfolio/operation-samples/ and portfolio/release-assurance/. The separate
retained samples workflow checks them
when their inputs, scripts, or reports change. Packet replay uses the last
recorded artifact retrieval time and labels its output as historical. It does
not establish current release readiness; live checks still use the current time.
Use Node.js 24.21.0 from .nvmrc (see the supported runtime policy), then run:
node --test scripts/dashboard.test.mjs scripts/evidence-contract.test.mjs
node scripts/validate-dashboard.mjsThese scripts use Node's standard library; no npm install, credentials, network
or browser is needed for this stored-snapshot check. Repeat the same commands
after editing. The committed snapshot may correctly warn that it is stale; this
path checks its contract and fallback, not current live evidence. Refreshing with
node scripts/refresh-dashboard.mjs separately needs a read token in GITHUB_TOKEN
and network access. CI selects .nvmrc; a stable later Node24 patch/minor is
allowed but not automatically verified. Unsupported runtimes fail before token
or snapshot handling with a setup instruction.
At this dated snapshot, the version3 evidence contract
separated native execution, artifact publication and historical attestations.
Default-branch durable publication and retrieved, checksummed bundles had been
verified for ARIA, k6, Playwright and Selenium; the dashboard recorded a Verity
publication gap and a Selenium Firefox failure. Run 39003146926 deployed a
snapshot generated at 2026-10-17T04:35:46Z. Its schedule-health data was last
checked at 2026-09-09T09:00:22Z. These statements describe that snapshot only.
For current run, publication and schedule status, use the live dashboard above.
site/data/portfolio.json here is a seed snapshot for local rendering, not the live
record; check the deployed timestamp before relying on live cards. Synthetic fixtures
remain contract controls, not framework execution proof.