What you need for a UX test: equipment, a quiet room and thinking aloud

What “thinking aloud” means and why clients need it

In a typical UX test you complete tasks on a website or in an app while software records your screen and voice. The client then watches the recording to find the moments where a person got lost, hesitated or could not find what they needed. A silent recording tells them almost nothing: they can see where you clicked, but not why.

UserTesting puts it simply: narrate what you see and do in real time, as if you were talking a friend through it on the phone. The practice test exists to check that you are comfortable speaking your thoughts out loud and can follow instructions.

• what you see: “I’m on the home page, there’s a menu at the top and a sign-in button on the right”
• what you are looking for: “I want to find delivery info, so I’m checking the menu”
• what you expect: “I think tapping this will open the cart”
• what surprises or annoys you: “I can’t tell how these two plans differ”
• how it went: “Found it, but it took a while, I might have given up”

Equipment: what to check in advance

Exact device requirements differ between platforms and change over time, so check the help centre before you sign up. There is a comparison table in our article on testing websites and apps for money.

For desktop tests, Userlytics requires a Mac with OS X 10.11 or later or a PC with Windows 7 or later, fast internet, a standard browser such as Chrome or Edge, headphones and a working microphone, plus a webcam for some tests. Mobile tests need an iPhone on iOS 16 or later or Android 9 or later. dscout has the same phone minimums: iOS 16 or Android 9, with a working camera and microphone.

• microphone: unmuted, not blocked in the browser and close to you; UserTesting advises against Bluetooth headphones
• screen-recording permission: take extra care on Android and macOS, where the system asks separately
• notifications: turn them off so they do not end up in the recording or distract you
• browser: up to date; for Userlytics live sessions, the latest version of Chrome

Your computer: UserTesting sets the highest bar

Among the big platforms, UserTesting has the strictest computer requirements. If your laptop meets them, it will work for most others too. If it does not, start with platforms that ask for less, such as Userlytics.

Testing on your phone: what to watch for

Mobile tests are convenient because your phone is always at hand, but the requirements are stricter than they look. The platform’s app records your screen and voice at the same time, and on a phone below the requirements you simply cannot install it: dscout, for example, says plainly that without iOS 16 or Android 9 and a working camera and microphone you will not be able to download its app.

For iPhones, UserTesting accepts only the two latest iOS versions. For Android its pages disagree: the applicant FAQ says Android 8.0 or later, while the marketing page says Android 10 or later and advises against Xiaomi phones. If your phone is borderline, go by the stricter requirement. For game tests, PlaytestCloud needs Android 10 or later, excluding Amazon Fire tablets, Android Go devices, Samsung Galaxy A15 and Motorola G phones, or iOS 16 or later, from iPhone 8 onwards.

Before a test, charge your phone, free up storage for the recording, and give the app permission to use the microphone and record the screen. Both Android and iOS ask for these permissions separately, and if you refuse, the recording will have no sound or no screen.

A live session with a moderator: a separate checklist

Some tests happen live: you see a moderator, they see you and your screen and guide you through the tasks. Userlytics publishes detailed requirements for these sessions, and they are a good benchmark for any platform.

Open the session link at least 15 minutes before it starts: a system check runs first, asks you to share your screen and tells you what to fix. If the moderator does not turn up, Userlytics shows a 20-minute countdown, and you are still paid for your time.

Place and time

Noise is the most common reason for a poor recording. UserTesting advises finding a quiet, distraction-free space, turning off notifications and cutting background noise. PlaytestCloud requires you to record somewhere quiet, away from other people, and to stay fully engaged in the test.

Leave yourself enough time. The UserTesting practice test takes about 10 minutes and must be done in one sitting: you cannot pause and resume later. For live sessions, Userlytics advises having enough free time to finish the whole test.

How to do the test itself

UserTesting suggests getting into the mindset: treat the scenario as if you were genuinely trying to complete the tasks on your own. Do not guess what the client wants to hear, and do not praise things just to be polite: the value of a test is your honest reaction, including negative ones. PlaytestCloud says both positive and negative opinions are welcome, and that the best comments are fair and useful.

Keep talking even when everything is clear. A short “yes, that’s obvious, tapping it” is information too. If you get stuck, say so out loud and explain what you were looking for: those are the moments clients value most.

In English-language tests, use simple sentences. PlaytestCloud requires commentary in English and your device set to English unless the test says otherwise. UserTesting accepts contributors who speak English, French or German fluently.

• read each task aloud before you start it
• do not rush: the client needs your natural pace
• do not use search engines or AI helpers unless you are asked to
• do not take screenshots or discuss the products you test with others if the platform forbids it

Personal data: what never to enter

Tests often involve filling in forms: sign-up, a cart, checkout. Userlytics says plainly that you do not need to use real data. If a test asks for financial or personal information, such as a card number, passwords or your home address, stop the test and contact the platform’s support.

Remember that the client sees the recording. Close extra tabs, your email and anything else you do not want to show before you share your screen.

What happens after the test

The UserTesting practice test is reviewed by hand, and the result is sent by email. While it is being reviewed the status is “In Review”; once approved it becomes “Done”. If the test does not meet the requirements, you get feedback and may be given one more try: the status changes to “Try again”.

After your first paid test, UserTesting temporarily pauses your invitations until its quality team reviews the recording and gives your first rating. After that, clients rate your tests, and those ratings affect how many invitations you get. Userlytics also asks clients to rate feedback and says the most helpful feedback combines webcam video, speech and written answers.