Page MenuHomePhabricator

Reply v2.0: conduct usability test (MediaWiki)
Closed, ResolvedPublic

Description

Test goals

At a high level, this test intended to answer the following questions:

  1. What are peoples' impressions of the tool?
  2. Are the tool's features easy for people to discover?
  3. Are the tool's features intuitive for people to use?

We are specifically interested in understanding peoples' experiences completing the following tasks:

  • Format the content of the comment they are writing using rich text
  • Ping/@ mention another user. Scenarios:
    • Ping someone who has commented in the discussion the tester is commenting in
    • Ping someone who has commented in a different discussion on the talk page the tester is commenting on
    • Ping someone who has not commented on the talk page the tester is commenting on
  • Edit the ping they originally wrote
  • Insert a link into the comment they are writing
  • Add/remove the talk page they are responding on to their Watchlist from within the Reply tool

We are also curious to understand whether the tool posts the comments people draft to the talk page in the way they expect.

Test

https://www.mediawiki.org/wiki/Talk_pages_project/replying/prototype_testing#Reply_tool_version_2.0

Done

Event Timeline

This task can't be picked up by @iamjessklein until the prototype is done, due to the team's desire to repeat the Replying 1.0 testing strategy. Once the prototype is complete, testing onwiki can happen in parallel with T246190.

Prompted by the feedback @Pelagic shared about the v2.0 mockups on mw.org [i], I've updated the task description to make sure "Testing goals" includes us understanding whether Senior Contributors [ii] find the current implementation of @-mentioning to be intuitive.


i. https://w.wiki/PNj
ii. https://www.mediawiki.org/wiki/Talk_pages_project/Glossary

Prompted by the feedback @Samat, @TheDJ and others shared about the v2.0 mockups on mw.org [i][ii], I've updated the task description to make sure "Testing goals" includes us understanding whether Senior Contributors [ii] find the current implementation of adding/removing the talk page they are responding on to their Watchlist from within the Reply tool to be intuitive.


i. https://www.mediawiki.org/w/index.php?title=Topic:Vju7lfcav875rt8r&topic_showPostId=vk634g9c14vyrxwh#flow-post-vk634g9c14vyrxwh
ii. https://www.mediawiki.org/w/index.php?title=Topic:Vju7lfcav875rt8r&topic_showPostId=vlk2wob7xoi454qa#flow-post-vlk2wob7xoi454qa

Updating the task description with the specific below in response to the feedback we mentioned receiving in T246191#6107400 and T246191#6091905:

  • Ping/@ mention another user. Scenarios:
    • Ping someone who has commented in the discussion the tester is commenting in
    • Ping someone who has commented in a different discussion on the talk page the tester is commenting on
    • Ping someone who has not commented on the talk page the tester is commenting on

cc @iamjessklein

Next step

  • @iamjessklein to share feedback on the test draft with the following questions in mind:
    • What – if any – tasks should be added?
    • What – if any – changes do you think would make the test easier for people to understand and engage with?

@ppelberg - I directly ended the sandbox. I primarily adjusted the language to be more action oriented (less "imagine if" and more verbs).

In step 10 - I wasn't sure if you wanted me to look on the page and find my reply and then go to the history (2 steps) or if you just wanted me to view the history log. If you clarify that it should be in good shape. I would invite the "friends and family" testers to go ahead and populate the page with meaningful content.

@ppelberg - I directly ended the sandbox. I primarily adjusted the language to be more action oriented (less "imagine if" and more verbs).

Good spots. Thank you, Jess.

In step 10 - I wasn't sure if you wanted me to look on the page and find my reply and then go to the history (2 steps) or if you just wanted me to view the history log. If you clarify that it should be in good shape.

Oh, yeah. Two steps.

@iamjessklein, how does this look to you: https://office.wikimedia.org/w/index.php?title=User%3APPelberg_%28WMF%29%2Fsandbox&type=revision&diff=270628&oldid=270559

I would invite the "friends and family" testers to go ahead and populate the page with meaningful content.

Good idea. We'll reach out to a few people before announcing it more broadly on the project page.

Done

The usability test has been posted: https://www.mediawiki.org/wiki/Talk_pages_project/replying/prototype_testing#Reply_tool_version_2.0

Next steps

(all of the above is reflected in the task description)

ppelberg edited projects, added Editing-team (Tracking); removed Editing-team.
ppelberg updated the task description. (Show Details)
ppelberg moved this task from Backlog to Community Engagement on the Editing-team (Tracking) board.
ppelberg added a subscriber: Whatamidoing-WMF.
  • @Whatamidoing-WMF: share test with an initial group of testers to make sure it is clear and functional

Done.

Call for people to test version 2.0 has been posted to the Reply tool's project page: https://www.mediawiki.org/w/index.php?title=Talk_pages_project%2Freplying&type=revision&diff=3878919&oldid=3824134


Next steps

I am moving this task to "Required after release" considering the remaining action (below) can happen after the tool is deployed as a Beta Feature.

I've got this error message:

talk_pages_404.png (577×1 px, 57 KB)

The message appeared after I clicked on the Reply button. Reloading the page solved it.

Should I open a new ticket for it? Do we have ticket with similar issue already?

I've got this error message:

talk_pages_404.png (577×1 px, 57 KB)

The message appeared after I clicked on the Reply button. Reloading the page solved it.

Thank you for saying something, @Samat; this is not expected.

Should I open a new ticket for it? Do we have ticket with similar issue already?

Yes, please open up a ticket for this issue and, if you are able to, list the steps we might be able to take to reproduce the issue you experienced.

Ok, thank you for your reply!

Yes, please open up a ticket for this issue and, if you are able to, list the steps we might be able to take to reproduce the issue you experienced.

I tried: T255963