Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 971
    • Issues 971
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 27
    • Merge requests 27
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #18762
Closed
Open
Issue created Dec 15, 2021 by sajolida@sajolidaMaintainer49 of 49 checklist items completed49/49 checklist items

Usability tests of Tor Connection (Round 2)

  • Ask people about their understanding of the autoconfig: what information is shared with whom?
  • Test the UX when time sync fails: how is the UX? what can we do better?
  • Make sure that the wording of the Wi-Fi notification works fine
    • "Configure Only Once" was confusing to boyska. He thought that it was persisting only this Wi-Fi network

Scheduled for August 18 to 21.

  • Recruiting
    • Schedule slots (3 hours, with actual tests from 00:30 to 02:30)
    • Create screening survey
    • Test screening survey
    • Send link to screening survey
    • Select participants using screening spreadsheet in ux/private
    • Answer to all candidates using email templates
    • Only confirm after sound check
  • Preparation
    • Prepare the tasks
    • Prepare a fallback bridge in QR code
    • Adapt research information sheet
    • Adapt consent form
    • Adapt checklist
      • Think and pilot test the reset procedure
      • Explicit recording procedure
    • Bring mouse and keyboard
    • Test the recording setup
    • Prepare incentives
    • Print
      • Research information sheet
      • Consent forms
      • Tasks
  • Analysis
    • Create rainbow table
      • Check issues that were reported in the last round of similar tests
      • Mark new issues
      • Document benefit
      • Document cost
      • Document solved issues
      • Link rainbow table from here: https://gitlab.tails.boum.org/tails/ux/-/raw/master/network/rainbow_table_tor_connection_2022_08_Sao_Paulo.fods?inline=false
    • Update GitLab
      • Document findings in existing issues
      • Create missing issues
      • Link all issues to this one
      • Link related issues together
      • Verify labels on all issues
    • Share highlights on tails-dev
    • Prioritize work together with the developers
    • Prepare video clips
    • Save candidates in email database
    • Add to achievements.mdwn
    • Get reimbursed for travel, incentives, etc.
    • Improve checklist
    • Write notes about organizing
      • 3 hours slots
      • Having 2 tests a day and spread out to fix most obvious issues between them
      • Best days of the week
    • Report findings about the Activities overview and the Applications menu to #17077
Edited Dec 14, 2022 by sajolida
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking