> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/guides/courses/from-usertesting-to-dscout/usability-testing-in-dscout-vs-usertesting.md).

# Usability testing in Dscout vs UserTesting

We’ll cover each of Dscout’s individual mission/study types in depth in other courses, but there are a few important clarifications to make regarding usability testing when transitioning from UserTesting to Dscout.

## Usability tests combine “think out loud” and “interaction test” studies

In Dscout, we use our single **usability test** mission type to accomplish what UserTesting splits in two: Think Out Loud (TOL) studies and Interaction Tests.

In Dscout, usability tests offer:

* **Continuous recordings:** Dscout usability tests are continuously recorded, and you can even customize whether you want to capture just a participant’s screen or both their screen and camera. You’ll have access to the full recordings during analysis.
* **Talk-out-loud questions:** Instead of conducting a dedicated test just to hear participants talk through tasks or responses, Dscout usability tests let you include talk-out-loud questions, which specifically prompt participants to talk through what they’re thinking. And those responses are included in the overall recording of the study.
* **Task- and study-level prototype control:** While UserTesting often restricts the level of control you have over how your prototypes are presented within a study, Dscout gives you the power to add prototypes at the study level (for use at multiple points throughout your study) or at the task level (for use on individual tasks).

With the above options, rather than having you choose between recording participant responses or hearing them talk through their thoughts, Dscout lets you do both at once in a single study.

{% hint style="info" %}
**Note:** The above list covers the differences between what UserTesting and Dscout offer in terms of usability testing. To learn more about Dscout usability tests, see [Usability tests](https://help.dscout.com/hc/en-us/categories/37242165204116-Usability-tests-and-surveys) on our help center.
{% endhint %}

Now that you’re familiar with what’s in your Dscout toolkit, we have one final (but important) difference between Dscout and UserTesting to cover: how you’ll compensate your participants for their time and effort.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.dscout.com/guides/courses/from-usertesting-to-dscout/usability-testing-in-dscout-vs-usertesting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.