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 in the same path. When the last screen of a path is reused in a path, you'll get a message to remove the screen from the path or change your last scree...

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 mission must have at least one defined path — thi...

Unless your team is part of the live prototype embed closed beta and this feature is enabled, Maze doesn't automatically resync your prototype as you make changes in your prototyping tool. Instead,...

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...

Preview a single mission using the Quick Look feature You can preview each mission in your maze separately. This makes it quick and easy to ensure the mission is ready for testing. To preview a sin...

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

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 participate in the test, and these stat...

When you launch a maze live, we run one last validation check to make sure the test doesn't have any issues that might impact your tester experience. If there is an issue, we will prevent the maze ...

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:...