Test Run

From Tygron Support wiki
Revision as of 09:48, 13 August 2015 by Joris@tygron.com (talk | contribs)
Jump to navigation Jump to search

Template:Learned

What is a test run

A test run is a process designed to test whether a machine or system works well.

How does a test run relate to the Tygron Engine

A test run in relation to the Tygron Engine is a simple way of quickly testing the current state of your project. You can test the balance of your project: do all stakeholders have the correct Actions, do all stakeholders have enough Budget and do all the Actions have the correct effects. Using the test run to iterate over your project is an important step in developing a realistic, well-balanced and usable project.

Starting a Test run

The "Start Test run" button allows you to test your project during development. When the "start Test run" button is pressed, the test is started immediately. In the Virtual 3D World, you will experience the game from the perspective of the stakeholder selected in the editor ribbon bar. Depending on the configuration of your project, most likely the test run will start with a cinematic. The test run starts from the point where the players have passed all the starting screens. Once the cinematic has finished playing, all actions can be taken in the 3D World, as though you are actually putting your project to use.

Switching stakeholders

You can switch between stakeholders by using the "Switch Stakeholder" dropdown menu in the editor menu bar. When you switch to a different stakeholder, you will notice the interface in the Virtual 3D World panel changing, most notably the actions on the left of the panel and the indicators at the top. You can only switch to a stakeholder that is not yet selected by another user. When a user switches stakeholder, the original stakeholder is again available for selection.

To stop the testrun, press the button in the editor menu bar again, now labeled "Stop Testrun".

Note that it's also possible to start a testrun by directly taking an action, without pressing the "Start Testrun" button. When doing so, the flythrough at the beginning is skipped. The testrun can still be stopped in the same way, by pressing the "Stop Testrun" button.

When a testrun is started, all editing is temporarily suspended. Although the editor will remain active, all editing panels will be temporarily disabled. Most options in the editor menu bar will be greyed out as well. This holds true for all editing users, meaning that when you start a testrun, no user can edit until the testrun is stopped.

When a testrun is started, no other user can edit for the duration of the testrun. Editing can continue when the testrun is stopped.