On this page

Run a test session with Snaglist

For teams testing a new release or design with testers. At the end, every tester's issues are in GitHub, tagged by page and component, sorted by how bad they are. Allow 30 minutes to set up, then the session itself.

Before you begin

The steps at a glance

  1. Activate Snaglist for the test build only
  2. Record more for the session
  3. Choose an extra question for the session
  4. Brief the testers
  5. Triage the reports
  6. Deactivate the extra recording
flowchart TD
  accTitle: The steps at a glance
  accDescr: The steps in order: activate Snaglist for the test build only; record more for the session; choose an extra question for the session; brief the testers; triage the reports; deactivate the extra recording.
  A[Activate for the test build] --> B[Record more]
  B --> C[Choose an extra question]
  C --> D[Brief the testers]
  D --> E[Triage the reports]
  E --> F[Deactivate extra recording]

Step 1: activate Snaglist for the test build only

Follow Activate or deactivate Snaglist for everyone and set enabled from your build or a feature flag.

Step 2: record more for the session

Offer more report types (Choose the report types), and record the technical details for every report with collect: { styles: true, layout: true, errors: true, console: true }: Choose what a report records. Check your error and console messages hold no personal details first.

Step 3: choose an extra question for the session

Ask the extra question with "heuristics" for a usability review, "wcag" for an accessibility check, or your own list: Choose the kinds of issue and how bad they can be.

Step 4: brief the testers

Send them Report issues on a site that uses Snaglist, the address of the test build, and what to try. Ask for one report per problem.

Step 5: triage the reports

Sort, reproduce and close: Triage reports on GitHub.

Step 6: deactivate the extra recording

Set the collect settings back to "auto", or deactivate Snaglist, before the release goes live.

What next

This page on GitHub, where the help is written.