Test Run: Difference between revisions
No edit summary |
|||
| (25 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
{{ | A test run in relation to the {{software}} is a 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 [[Financial System|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. | ||
A test run | A test run in the {{software}} creates a space in which users can plan actions without permanently applying them to the current situation of your project, while also editing your project. The actions performed during a test run can be pre-made as measures or parametric designs, or actions for selections drawn by users. Stopping a test run allows users to easily revert back to the situation before the test-run was activated. However, this also removes all actions performed during this test run. | ||
== | ==Starting a Test run== | ||
[[File:Editor_ribbon_bar_testrun.jpg|thumb|left|Test Run]]<br clear=all> | |||
The "Start Test run" button allows you to test your project during development. | |||
[[File:Editor_ribbon_bar_testrun_active.jpg|thumb|left|Test Run Active]]<br clear=all> | |||
Pressing the "Test Run" button, starts the test run immediately. The text "Test run active" is displayed above the Test run buttons, the play button colors gray and the stop buttons colors red. In the 3D Visualization of your project, you will experience the [[session]] 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]]. Once the cinematic has finished playing, [[actions]] can be taken by interacting with the [[3D Visualization]]. | |||
When a test run is started, all editing is temporarily suspended. Although the editor will remain active, editing panels will be temporarily disabled. This applies to all users logged into the project, no other user can edit for the duration of the test run. Editing can continue when the test run is stopped. | |||
It's also possible to start a test run by directly taking an action. When taking an action the "Test Run" will be automatically activated. When doing so, the cinematic at the beginning is skipped. The test run can still be stopped by pressing the "Stop Test run" button. | |||
==Stopping a Test run== | |||
To stop the test run, press the square stop-button in the editor menu bar. All [[Actions]] and their effects taken since the start of the test run will be reverted. | |||
When a | ==Switching stakeholders== | ||
You can switch between stakeholders by pressing a different stakeholder button in the editor ribbon bar. When switching to a different stakeholder, parts of the interface will change, most notably the [[actions#categories|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 stakeholders, the original stakeholder is again available for selection. | |||
{{article end | |||
|seealso= | |||
* [[Session]] | |||
* [[SimState]] | |||
}} | |||
{{Template:Editor future design nav}} | |||
Latest revision as of 11:01, 21 February 2023
A test run in relation to the Tygron Platform is a 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.
A test run in the Tygron Platform creates a space in which users can plan actions without permanently applying them to the current situation of your project, while also editing your project. The actions performed during a test run can be pre-made as measures or parametric designs, or actions for selections drawn by users. Stopping a test run allows users to easily revert back to the situation before the test-run was activated. However, this also removes all actions performed during this test run.
Starting a Test run
The "Start Test run" button allows you to test your project during development.
Pressing the "Test Run" button, starts the test run immediately. The text "Test run active" is displayed above the Test run buttons, the play button colors gray and the stop buttons colors red. In the 3D Visualization of your project, you will experience the session 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. Once the cinematic has finished playing, actions can be taken by interacting with the 3D Visualization.
When a test run is started, all editing is temporarily suspended. Although the editor will remain active, editing panels will be temporarily disabled. This applies to all users logged into the project, no other user can edit for the duration of the test run. Editing can continue when the test run is stopped.
It's also possible to start a test run by directly taking an action. When taking an action the "Test Run" will be automatically activated. When doing so, the cinematic at the beginning is skipped. The test run can still be stopped by pressing the "Stop Test run" button.
Stopping a Test run
To stop the test run, press the square stop-button in the editor menu bar. All Actions and their effects taken since the start of the test run will be reverted.
Switching stakeholders
You can switch between stakeholders by pressing a different stakeholder button in the editor ribbon bar. When switching to a different stakeholder, parts of the interface will change, 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 stakeholders, the original stakeholder is again available for selection.
Future Design