Two tools: the in-app checklist and the workbook
Results live in two places, and it is important everyone knows which one wins.
The in-app checklist
Inside AfriAnnotate, open your account menu and choose My testing checklist. You see your suites and steps. Pressing Pass, Fail or Skip records the result instantly; press an active button again to undo. Pressing Fail opens a bug report for you, pre-filled with the step ID and the page you are on, and files it to GitHub, where the developers work. You never need a GitHub account.
The lead sees a live suite-by-tester matrix under Platform → Testing.
This is the source of truth for ticks.
Details of the report form and the staff view are on the testing programme page.
The workbook (tracker)
The Excel file AfriAnnotateTestingTracker_v2.xlsx holds what the app
does not: who is assigned to what, which build each result came from,
defect severity and priority, the retest queue, hygiene checks and the
round sign-off.
It is also the fallback if the app is down or a tester cannot reach it.
This is the source of truth for coordination.
Keeping them in step
To keep them in step, the lead copies the app's matrix into the Status column of the workbook once a day. Testers do not need to enter results twice:
- Tick in the app.
- Add to the workbook only what the app cannot hold: the environment, notes, evidence links, the Defect ID.
If the app is unavailable, record in the workbook and tell the lead, who re-enters the ticks in the app.
| Question | Answer |
|---|---|
| Did the step pass or fail? | The app wins. |
| Who is doing it, on which build, how bad is the bug, is it fixed yet? | The workbook wins. |
| They disagree | Fix the workbook to match the app's tick, then check the rest of the row. |
Two sources of truth drift within days unless the daily copy actually happens. Put it in your calendar. If it becomes a burden, drop to one: tell testers to work only in the workbook and treat the app as optional.