-
Notifications
You must be signed in to change notification settings - Fork 49
error messages 8377 usability testing guide
Original available here: https://editor.apps.ei8fdb.org/fcfo2Y-8RyqOw0oNyCYCrA#
Thank you for taking part in our testing today. This work can only be successful with input from users so I appreciate your time.
I'll give some background on the work we're doing. The pip team are working on improving pip's dependency resolver. As part of this we're working on improving the messages that users see when pip runs into a problem.
Today we'll be focusing on testing these error messages. In this testing there is no right or wrong answer. We're not testing you, or your knowledge of Python - we're testing our work - to make sure these error messages are understood and helpful for users.
So it's good to hear about what works well in the error messages, but more importantly I'm interested in hearing what about doesn't work well. If there is something that needs to be improved, please tell me. You won't insult me!
I'll ask you a few questions about your use of Python and pip, and then we'll get to the testing. The session will last 25 minutes. OK?
Before we start, have you got any questions?
- What do you do? What do you spend most your time doing?
- What do you use Python for?
- How often do come across dependency conflicts?
- When you do, what sources of information do you use to fix them?
- What is the most difficult part of dealing with dependency conflicts?
- What do you do when you can't resolve a conflict?
Great, thanks for telling me that. It's very helpful to understand how people deal with dependency conflicts. Now we'll move onto the testing.
As I mentioned earlier, today we'll be testing pip's the error messages displayed when pip runs into a problem with package installing.
We're going to use a scenario for this testing. I'll explain everything now.
Here is the scenario we will use
One of your friends, Bernard, wants to use a Python application. He is following instructions to install it, and has ran into a problem. He's not an expert in Python.
The instructions tell him he must run the command:
pip install ward==0.46.0-b.0 py2neo==4.3.0 --unstable-feature=resolver
He's tried this but he gets an error message and doesn't understand what went wrong. He is now asking for your help.
He will do a screen-share with you so you can see what's happening and help.
Help him understand what went wrong, and how he might fix this.
I am going to play the part of your friend. I will share my screen with you and you'll attempt to guide me through the steps. I'll ask you to also think out loud as.
OK, so far? Good!
I'll start by sharing my screen:
(SHARE VM SCREEN)
Can you see the osboxes CLI? Great.
As I mentioned, I'm trying to follow these instructions to install this application. It's telling me to run this command and to use the "unstable resolver feature":
pip install ward==0.46.0-beta.0 py2neo==4.3.0 --unstable-feature=resolver
I guess I'll start with the command.
(run command)
(Indicate on the error message on the screen) It's giving me this error message again.
- Can you tell me what has happened?
- What does the first line for package ward means? Can you explain it to me?
- What does the ~= mean in the second line mean?
- How are we going to solve this?
- Is there anything in the error message that gives you a clue of what to do next?
- There's a link there. What if I click on it?
- Before I click on the link, what do you expect to find there?
I'll paste the link for you into the Google meet chat:
Generic package names: https://hackmd.io/@M95RnJ03QpCMXfii_RnsGw/HJhwX0hnI
Specific package names: https://hackmd.io/-ChkslWrQf2Zpysy2dQ5ZQ?view
(after clicking on the link)
I'd like you to read this now. As you are reading it please tell me if you have any thoughts about what you are reading.
- What is the most useful information on this page?
- What is the least useful information on this page?
- Is there any information you don't understand?
- From the information on this page, what option do you recommend me to try?
So that's the end of the test. Thanks for your time. Do you have any closing thoughts?
I appreciate your time and comments. We will use them to improve our work. If you are interested in taking part in more research, keep an eye out for another email. Bye!