Prototype testing

A mission is a task for testers to complete. Create missions to learn what actions users perform in your prototype. For every mission tested, Maze will give you usability metrics and data you can a...

The last screen of a path shouldn't be reused on the same path or on another path in the same block. When the last screen of a path is reused in a path, you'll get a message to remove the screen fr...

The expected path is the flow of screens you want a tester to go through in order to complete a mission (i.e. your prototype or website test). Each prototype mission must have at least one defined ...

You should refresh the prototype in your draft maze every time you change your prototype. This will fetch the latest version of the prototype, while maintaining all blocks and paths in the draft ma...

A mission is a task (i.e. a prototype or a website test) your testers will have to complete. To create a mission, you have to define the task, a description, and the expected path(s) inside the pro...

Previewing Using the Quick Look feature You can preview each prototype block in your maze separately. This makes it quick and easy to ensure the test is ready for participants. To preview a single ...

In addition to skipping questions, testers also have the option to stop a prototype task at any moment. This helps them move forward in the maze, even if they don't reach a success screen. The Stop...

Ending your expected path with a state change brought on by a different trigger type, such as hover or drag, may cause your maze not to complete when testers take part in the test, and these state ...

Before launching a maze, we conduct a final validation check to ensure that there are no issues that could affect the tester's experience. If there is an issue, we'll prevent the maze from going li...

Maze allows you to conduct user testing with the prototypes you've imported. If you've imported your prototype but are missing screens, these steps may help you resolve the problem. Solution Figma:...