In an effort to understand, qualitatively, what contributors' experiences replying to specific comments on talk page is like, we are going to run a usertesting.com test of the "replying to specific comments" workflow on desktop, as it currently exists.
These test results will also be a helpful baseline to compare against those in T236921.
=== "Done"
- [x] Draft testing goals
- [x] Run test(s)
- [ ] Summarize test findings
- [ ] Draft improvements to address test findings
---
== Usability Test
Test Script: [[ https://docs.google.com/document/d/12zaCdZDnlgwmzi93rRC8xu9DQJEG_0kfgfDWVhzBySQ/edit# | Google Doc ]]
== Testing Goals
Talk pages are integral to many workflows including receiving feedback on edits from other contributors. This year, the Editing team’s goal is to partner with communities to trial features that make contributing to Talk pages, and understanding the information and activity inside them, easier and more intuitive. Our first iteration on Talk pages is tackling the workflow for how contributors respond to comments. There are many obstacles for both junior and senior contributors in the current workflow, including figuring out where to respond and how to sign and indent their responses.
The primary goals of this test are to gain insights on discovery, composition and view history of Discussion pages.
== Research Questions
//Discovery//
- Are users able to successfully select the reply button without any guidance/onboarding?
Composition
- [Junior Contributors] Is the replying workflow – in its entirety – intuitive and easy to use?
- At what points – if any – are participants not sure what to do? At what points – if any – are participants not able to predict what impact their actions will have?
//Revisions//
- Are users able to successfully select and compare revisions from the History page?
- Are users able to tell what was added to the page?
- Is the information presented presented in a way that is understandable to users? Are they able to tell what was removed or added?