Every modl.ai user gets access to the Modl Demo organization, which includes an upload of the Unity demo project and previously run test reports. To view the modl demo studio test reports, log in to the platform and go to Modl Demo > See reports > View report.

The game includes predefined bugs, errors for modl to report on.

The table below includes the predefined bugs, errors and events:

Error or event	Use case
Null Reference Exception	The `Goal` prefab has an attached `NextLevelLoader` script. When a player collides with the `Goal` prefab, the script loads the level defined in the Name of next level field. In the project, the next level is misspelled so that the script throws a `NullRef`.
Out of bounds	There is a large plane at the bottom of the level that reports a `FellOffLevel` event if the player falls off the level and collides with it.
Collectibles	An event reports if the player picks up a collectible. The event also saves the score as a state in the test report.
Ground layers check	This is a one-off check that runs during `Start()`. If your ground layer extends to more GameObjects than you intended, you might experience bugs. For example, if a wall is defined as ground, your player could scale the wall when it jumps. This game includes a `LevelSetupTests` script that compares the number of ground objects with a number you specify. If the number is higher, you'll see it in the report. To specify an acceptable number of ground layers, go to the Player character > ThirdPersonController.
Collider issues	The doors in the `Labyrinth` level have colliders that are too small, allowing the player to pass by without a key. An `EndZoneNoKey` event reports if the player gets past the door without the key.