Testing dashboard
Issue personal tester links, watch results arrive, and follow every finding from report to released fix.
Issue personal tester links, watch results arrive, and follow every finding from report to released fix.
Loading…
Tenacity staff with the test harness admin role sign in with their Google work account, the same sign-in as the release dashboard.
A plan is two small YAML files. manifest.yaml lists the
tests: what the tester checks, grouped into sections, each test with a stable
id that never changes across builds (that is what powers the
Fixed/Regression comparison). build.yaml is the per-build cover
sheet: version, date, what is new. The editors below start with a working
skeleton; replace the example text and add tests. Commit, wait about a minute
for the render workflow, then Publish to cut the release testers use.
Tip: pick an existing plan under "Start from" and you only need to update the build.yaml facts and any new tests; keeping test ids identical is what makes results comparable between builds.