Questions testers ask

The expected result says one thing and the app does something reasonable but different. Pass or Fail? If the meaning matches, Pass with a note. If the difference would confuse a real user, or the checklist is clearly describing a specific behaviour that is absent, Fail. When torn, ask.

I found a bug that no step covers. File a defect anyway, with the nearest Step ID and a note that it was found incidentally. Bugs do not care about our checklist.

The step needs another tester and they are offline. Set In Progress, note who you are waiting for, move on, and come back. Do not mark Blocked for a person; Blocked is for the product.

Something failed yesterday and works today with no fix. That is an intermittent bug, and it is still a bug. Keep the defect open, add the note, and record what was different (network, build, data).

I marked the wrong status. Just change it. In the app, press the active button again to undo, then press the right one. The audit trail lives in the app and in the Round Log, not in individual cells.

Do I retype results from the app into the sheet? No. The lead copies ticks across daily. You add only Environment, notes, evidence and Defect IDs.

How long should a step take? Most take two to five minutes; setup and export steps longer. If a step is taking twenty, something is wrong: either you are blocked, or the instructions need clarifying. Write the Duration honestly; it plans the next round.

What if I disagree with a Tier or an assignment? Say so. Both are dropdowns for a reason.

The app is down and I cannot tick anything. Record in the workbook (Test Runs) and tell the lead, who re-enters the ticks in the app when it is back. Keep going; do not wait.

Windows warned me the app is from an unknown publisher. Expected, once. Click More info, then Run anyway. It is not a bug — see builds and environments.

The Mac app will not open on my Intel Mac. It is Apple Silicon only. Mark those steps Blocked with a note, not Fail.