How to: Conduct user testing¶
This is a how-to article to explain how to run user testing sessions for the GRASA Event Locator. It intends to be a blueprint for these sessions but it is not exhaustive.
Background¶
User testing is a helpful way to collect feedback about how people use and interact with our application. To date, Lei Mon conducted user tests early on in the development cycle. This guide is formed from her notes and questions. For consistency’s sake, make sure user tests are as consistent as possible across sessions.
Questionnaire¶
These are questions to answer during user testing. Feel free to add new ones through a pull request:
- User demographics
- Age, race/ethnicity, occupation, etc.
- Ask interviewee how they identify
- Estimated background with technology?
- Overall familiarity with desktop or mobile devices?
- What are users’ thoughts while viewing search/filter on the homepage?
- How easy or difficult was it to navigate across the pages?
- Is there anything the user does not understand?
- What are users’ overall thoughts on the design and layout?
- How long did it take the user to complete a task?
- User’s overall satisfaction with website?
- What did the user like the most and the least?
- Any problems finding the information wanted by the user?
- Any difficulties using it on mobile devices?
- Does the user prefer a mobile or desktop view?
Tasks¶
This is an idea list of tasks you can run a user through, depending what user they simulate.
Admins¶
- Change Site Logo
- Approve new user
- Reject new user
- Approve new event
- Reject new event
Providers¶
- Login
- Register
- Forgot Password
- Create Event
- Edit Event
- Change Organization Logo
Families¶
- Filter for an Event
- View Event