QA workflow · 5 min read
Make a screenshot collection for QA feedback
A bug report is easier to act on when the screenshots show the sequence, not just the final error. Capture the steps in order, mark the exact issue and send one coherent handoff.
1. Name the collection after the task
Use a short name such as “Workspace settings — save feedback”. Put the screen or action first, so a teammate can find the report later. Start a collection before the first capture; subsequent screenshots belong to the same story.
2. Capture the sequence, not the desktop
Take an area, window or full-screen screenshot for each meaningful step: starting state, action and result. Keep only images that explain the issue. In Snipfolio, screenshots remain ordered in the collection and can be rearranged before sharing.
3. Mark what the reviewer should notice
Add an arrow to the control, a revision cloud around the changed area, or numbered steps for a longer path. Marks remain editable in the Mac collection. If the target moves or the wording changes, adjust the mark instead of recapturing the whole sequence.
4. Protect and check the handoff
Look for customer details, account names and notifications. Redact confidential fields before export, then inspect the rendered result. The editable source remains local; a shared link uses flattened images. Include a short written expected-versus-actual note so the screenshots have context.
5. Share one place to review
Send the collection as a link, PDF or Word document according to the recipient’s workflow. Open the exported file or link once yourself. If you need to revise the report later, return to the local collection, change the marks or order, and make a new export.