States of Running Tests

These are the different states of running tests which can be shown by the group-monitor.

Background: There are plenty of different combinations of state-values of a running test: Some states are reported by the frontend, like CONTROLLER, some come from the backend like if the test is locked. State means a set of values represenatating, wether the test is started, which unit was shown last, the remaining time, an error if there is any, wether it is locked and so on. Various combinations are possible: a test can be locked and paused at the same time for example. Those things are boiled down to the following states (internally called super-states) to be displayed to be more convinient for the user. The order means the importance: if there is a error, the super-state will be error, regardless of if the test is paused or not.

	pending
	Tooltip: `Test noch nicht gestartet`
	The test has not been started yet.

	locked
	Tooltip: `Test gesperrt`
	This state is reached if the participant pressed the "Quit"-button or a supervisor hit the "Quit all"-button

	error
	Tooltip: `Es ist ein Fehler aufgetreten!`
	An error has occurred a the participants computer. Probably a network error or the like, but can also indicate bugs and should be investigated if possible. The participant should reload his browser and get support if the problem still exists.

	controller_terminated
	Tooltip: `Testausführung wurde beendet und kann wieder aufgenommen werden. Der Browser des Teilnehmers ist nicht verbunden und muss neu geladen werden!`
	Test execution has been completed and can be resumed. The browser of the participant is not connected and must be reloaded! Condition occurs when the "Unlock"-Button was used in the group monitor.

	connection_lost
	Tooltip: `Seite wurde verlassen oder Browserfenster geschlossen!`
	The connection to the participant's browser is demolished. He could have closed the window or the network connection is demolished.

	paused
	Tooltip: `Test pausiert`
	undefined

	focus_lost
	Tooltip: `Fenster/Tab wurde verlassen!`
	Another window or another tab was selected, but the site is still open and connected.

	idle
	Tooltip: `Test ist 5 Minuten oder länger inaktiv!`
	The participant was idle for five minutes or longer. This state can only be displayed on polling mode and is intended to be a fallback for the case that the participant's browser or computer was shut down and not able to report the lost connection. It' s not appropriate to measure testees behaviour.

	connection_websocket
	Tooltip: `Test läuft, Verbindung ist live`
	Test runs and participant is connected in live mode (= WebSocket).

	connection_polling
	Tooltip: `Test läuft`
	Test runs and participant is connected in the polling mode connection. This si a fallback for the case that the live-mode is not possible due to the supervisor's browser or a technical error. It works the same but the monitors performance is less smooth because new data is polled every 5 seconds and not pushedwhen there is anything.

	ok
	Tooltip: `Test läuft`
	Test seems to run but the connection type is unknown. This is is more or less a fallback state which indicates, that nothing is known about the test except for it's existence. This could be the case in various error-scenarios or misconfigurations but should not happen in general. It should be investigated, but most likely the test can be continued safely since the error is more likely on the monitor's side.