Skip to main content

The workbook, tab by tab

The tracker has nine tabs. Testers only ever type in two of them (Test Runs and Defects) and read one (My Work). The lead uses the rest.

TabWhoWhat for
READMEeveryoneA one-page version of this guide inside the file, plus the legends
Test Runstesters typeOne row per step — the result, environment, notes, defect ID
My Worktesters readYour own steps, filtered and colour-coded
Dashboardlead readsTotals, percentages, hygiene counters, breakdowns
Defectstesters and lead typeOne row per distinct bug
TestersleadWho is who, their devices and builds
EnvironmentsleadThe exact builds under test
SuitesleadReference list of the 39 suites
Round LogleadOne row per round, with criteria and sign-off

README​

A one-page version of this guide inside the file, plus the legends. Read it once; come back when you forget a status meaning.

Test Runs (testers type here)​

One row per step, 556 rows for R1. The columns, left to right:

ColumnWhat it holdsWho fills it
Run IDTR-0001 and so on. A unique label for this row, used when a later round retests it.Pre-filled
RoundR1, R2… which round this row belongs to.Pre-filled
Suite, Module, Section, Step IDWhere the step sits. Filter on these to work through one suite.Pre-filled
TierSmoke, Core or Extended. Do Smoke first.Pre-filled, lead may change
What to do / Expected resultThe step itself, copied from the checklist.Pre-filled
RolesEvery role the checklist says could cover the step. Reference only.Pre-filled
Assigned ToThe one person responsible. Turns red if empty.Lead
EnvironmentThe build you used, from the dropdown. Web steps are pre-filled with ENV-WEB; mobile and desktop steps are blank until you pick. Turns amber if you record a result without one.Tester
StatusThe result, from the dropdown. Colours the whole row.Tester
Result NotesAnything worth knowing: what you actually saw, why you skipped, what blocked you.Tester
Defect IDThe DEF number that explains a Fail. Turns red while a Fail has none.Tester
Evidence LinkLink to a screenshot or recording.Tester
Tested On / Duration (min)The date, and roughly how long the step took. Duration helps plan Round 2.Tester
Retest OfFor Round 2 rows: the Run ID of the R1 row being repeated.Lead

There is also a hidden helper column (T) that makes the My Work tab work. Leave it alone.

Never delete a row

If a step no longer applies, set its Status to Obsolete. Deleting a row breaks the counts and loses the history.

My Work (testers read here)​

Pick your tester ID in cell B1 and the round in E1. The tab lists your steps in order, colour-coded, with counters for done, failed, blocked and Smoke steps still to run.

It is read-only by design. To record a result, go to Test Runs, filter the Assigned To column by your ID, and set Status there.

Dashboard (lead reads here)​

Pick a round in B1 (or ALL). Everything below follows that choice: totals and percentages, defects and blockers open, the retest queue, three hygiene counters that should read zero, then breakdowns by tier, module and tester, and open defects by severity. Nothing on this tab is typed.

The three hygiene counters:

  1. Fails without a Defect ID
  2. Unassigned steps
  3. Touched steps with no Environment

Defects (testers and lead type here)​

One row per distinct bug. Reporting a bug explains how to fill it in. The example row at the top shows the expected shape; delete it once a real defect exists.

Testers, Environments, Suites, Round Log (lead)​

  • Testers records who is who, their device, OS, browser and build, time zone and availability, and whether they are onboarded. Columns N to P count each person's load for the Dashboard round.
  • Environments lists the exact builds under test. Add a row for each new build and set old ones to Retired rather than deleting.
  • Suites is the reference list of the 39 suites.
  • Round Log holds one row per round with dates, criteria and sign-off; its Steps Executed, Pass Rate and Blockers columns calculate themselves.