GuiBrowser/en - Versionsgeschichte

Cg: /* Why is the Widget Hierarchy not Updated Automatically? */

2020-05-06T14:11:03Z

Why is the Widget Hierarchy not Updated Automatically?

← Nächstältere Version		Version vom 6. Mai 2020, 14:11 Uhr
Zeile 5:		Zeile 5:
	Also views such as popup or dialogs might vanish, when you click elsewhere - especially when you leave your application and click in expecco (i.e. change the focus).		Also views such as popup or dialogs might vanish, when you click elsewhere - especially when you leave your application and click in expecco (i.e. change the focus).
	An automatic update would make it very hard to inspect and automate this kind of window.		An automatic update would make it very hard to inspect and automate this kind of window.
	For this reason, expecco will only update its tree upon request - either by mouse click, or by hotkey or by setting a timed update (update after X seconds). Take a look at the items found in the GuiBrowser's ''update'' menu ().		For this reason, expecco will only update its tree upon request - either by mouse click, or by hotkey or by setting a timed update (update after X seconds). Take a look at the items found in the GuiBrowser's ''update'' menu ([[Datei:guiBrowserUpdateButton.png]]).

	== Why are Broken Connections not Always Shown Immediately as Such? ==		== Why are Broken Connections not Always Shown Immediately as Such? ==

Cg: /* Why is the Widget Hierarchy not Updated Automatically? */

2020-05-06T14:10:26Z

Why is the Widget Hierarchy not Updated Automatically?

← Nächstältere Version		Version vom 6. Mai 2020, 14:10 Uhr
Zeile 5:		Zeile 5:
	Also views such as popup or dialogs might vanish, when you click elsewhere - especially when you leave your application and click in expecco (i.e. change the focus).		Also views such as popup or dialogs might vanish, when you click elsewhere - especially when you leave your application and click in expecco (i.e. change the focus).
	An automatic update would make it very hard to inspect and automate this kind of window.		An automatic update would make it very hard to inspect and automate this kind of window.
	For this reason, expecco will only update its tree upon request - either by mouse click, or by hotkey or by setting a timed update (update after X seconds). Take a look at the items found in the GuiBrowser's ''update'' menu.		For this reason, expecco will only update its tree upon request - either by mouse click, or by hotkey or by setting a timed update (update after X seconds). Take a look at the items found in the GuiBrowser's ''update'' menu ().

	== Why are Broken Connections not Always Shown Immediately as Such? ==		== Why are Broken Connections not Always Shown Immediately as Such? ==

Cg: /* Why is the Widget Hierarchy not Updated Automatically? */

2020-05-06T14:08:36Z

Why is the Widget Hierarchy not Updated Automatically?

← Nächstältere Version		Version vom 6. Mai 2020, 14:08 Uhr
Zeile 5:		Zeile 5:
	Also views such as popup or dialogs might vanish, when you click elsewhere - especially when you leave your application and click in expecco (i.e. change the focus).		Also views such as popup or dialogs might vanish, when you click elsewhere - especially when you leave your application and click in expecco (i.e. change the focus).
	An automatic update would make it very hard to inspect and automate this kind of window.		An automatic update would make it very hard to inspect and automate this kind of window.
	For this reason, expecco will only update its tree upon request - either by mouse click, or by hotkey or by setting a timed update (update after X seconds).		For this reason, expecco will only update its tree upon request - either by mouse click, or by hotkey or by setting a timed update (update after X seconds). Take a look at the items found in the GuiBrowser's ''update'' menu.

	== Why are Broken Connections not Always Shown Immediately as Such? ==		== Why are Broken Connections not Always Shown Immediately as Such? ==

Cg am 6. Mai 2020 um 14:02 Uhr

2020-05-06T14:02:40Z

← Nächstältere Version		Version vom 6. Mai 2020, 14:02 Uhr
Zeile 1:		Zeile 1:

	== Why ~~are~~ ~~broken~~ ~~connections~~ not ~~always shown immediately as~~ ~~such~~? ==		== Why is the Widget Hierarchy not Updated Automatically? ==

			Many applications change their state with mouse-enter/leave and especially with focus change events.
			Also views such as popup or dialogs might vanish, when you click elsewhere - especially when you leave your application and click in expecco (i.e. change the focus).
			An automatic update would make it very hard to inspect and automate this kind of window.
			For this reason, expecco will only update its tree upon request - either by mouse click, or by hotkey or by setting a timed update (update after X seconds).

			== Why are Broken Connections not Always Shown Immediately as Such? ==

	Even if there is no interaction with the application will the connection be checked in regular time intervals (a kind of ping). By default, this interval is 5 seconds. It can be changed by evaluating "GuiBrowser::GUIApplication connectionAliveCheckCycle:<seconds>", which can be done in the expecco startup script, in an expecco notepad or in an elementary action.		Even if there is no interaction with the application will the connection be checked in regular time intervals (a kind of ping). By default, this interval is 5 seconds. It can be changed by evaluating "GuiBrowser::GUIApplication connectionAliveCheckCycle:<seconds>", which can be done in the expecco startup script, in an expecco notepad or in an elementary action.

Cg: /* Start Windows Applications */

2020-05-06T13:57:56Z

Start Windows Applications

← Nächstältere Version		Version vom 6. Mai 2020, 13:57 Uhr
Zeile 9:		Zeile 9:
	If you have already started your target app on your computer, select eg. "Windows Automation2" in the GuiBrowser when connecting and leave the default settings in the connect dialog (localhost, port=xxxx, timeout=xx s). Then a process is started (WindowsAutomation Client) which connects expecco to your application or desktop. After connecting, you will see the window elements of your application (or all applications on your computer) in the GuiBrowser under the connection.		If you have already started your target app on your computer, select eg. "Windows Automation2" in the GuiBrowser when connecting and leave the default settings in the connect dialog (localhost, port=xxxx, timeout=xx s). Then a process is started (WindowsAutomation Client) which connects expecco to your application or desktop. After connecting, you will see the window elements of your application (or all applications on your computer) in the GuiBrowser under the connection.

	:To start the application, it is best to create a new block in the test-suite, name it e.g. "Start ~~Client~~" and insert one of the existing "OS-Start-Process" blocks (from the standard library).		:To start the application, it is best to create a new block in the test-suite, name it e.g. "Start Client2" and insert one of the existing "OS-Start-Process" blocks (from the standard library).

	It is a good idea to put application start and stop into separate actions (and separate testplan elements),		It is a good idea to put application start and stop into separate actions (and separate testplan elements),

Cg: /* Start Windows Applications */

2020-05-06T13:57:33Z

Start Windows Applications

← Nächstältere Version		Version vom 6. Mai 2020, 13:57 Uhr
Zeile 5:		Zeile 5:

	== Start Windows Applications ==		== Start Windows Applications ==
	:In general, no applications are started via the GuiBrowser (although it is possible *). Rather, it establishes connections to running applications.		In general, no applications are started via the GuiBrowser (although it is possible *). Rather, it establishes connections to running applications.

	:If you have already started your target app on your computer, select eg. "Windows Automation2" in the GuiBrowser when connecting and leave the default settings in the connect dialog (localhost, port=xxxx, timeout=xx s). Then a process is started (WindowsAutomation Client) which connects expecco to your application or desktop. After connecting, you will see the window elements of your application (or all applications on your computer) in the GuiBrowser under the connection.		If you have already started your target app on your computer, select eg. "Windows Automation2" in the GuiBrowser when connecting and leave the default settings in the connect dialog (localhost, port=xxxx, timeout=xx s). Then a process is started (WindowsAutomation Client) which connects expecco to your application or desktop. After connecting, you will see the window elements of your application (or all applications on your computer) in the GuiBrowser under the connection.

	:To start the application, it is best to create a new block in the test-suite, name it e.g. "Start ~~Client2~~" and insert one of the existing "OS-Start-Process" blocks (from the standard library).		:To start the application, it is best to create a new block in the test-suite, name it e.g. "Start Client" and insert one of the existing "OS-Start-Process" blocks (from the standard library).

	It is a good idea to put application start and stop into separate actions (and separate testplan elements),		It is a good idea to put application start and stop into separate actions (and separate testplan elements),

Cg am 6. Mai 2020 um 13:57 Uhr

2020-05-06T13:57:02Z

← Nächstältere Version		Version vom 6. Mai 2020, 13:57 Uhr
Zeile 3:		Zeile 3:

	Even if there is no interaction with the application will the connection be checked in regular time intervals (a kind of ping). By default, this interval is 5 seconds. It can be changed by evaluating "GuiBrowser::GUIApplication connectionAliveCheckCycle:<seconds>", which can be done in the expecco startup script, in an expecco notepad or in an elementary action.		Even if there is no interaction with the application will the connection be checked in regular time intervals (a kind of ping). By default, this interval is 5 seconds. It can be changed by evaluating "GuiBrowser::GUIApplication connectionAliveCheckCycle:<seconds>", which can be done in the expecco startup script, in an expecco notepad or in an elementary action.


	== Start Windows Applications ==		== Start Windows Applications ==

Cg am 6. Mai 2020 um 13:56 Uhr

2020-05-06T13:56:51Z

← Nächstältere Version		Version vom 6. Mai 2020, 13:56 Uhr
Zeile 1:		Zeile 1:

			== Why are broken connections not always shown immediately as such? ==

			Even if there is no interaction with the application will the connection be checked in regular time intervals (a kind of ping). By default, this interval is 5 seconds. It can be changed by evaluating "GuiBrowser::GUIApplication connectionAliveCheckCycle:<seconds>", which can be done in the expecco startup script, in an expecco notepad or in an elementary action.


	== Start Windows Applications ==		== Start Windows Applications ==

Cg: /* What is the purpose of the Preview Window (at the bottom left) */

2020-05-06T13:44:08Z

What is the purpose of the Preview Window (at the bottom left)

← Nächstältere Version		Version vom 6. Mai 2020, 13:44 Uhr
Zeile 36:		Zeile 36:
	* to enlarge sections		* to enlarge sections
	* to find out geometry data, such as rectangles or positions		* to find out geometry data, such as rectangles or positions
			* to provide element highlighting for GUI technologies, which do not support flashing or highlighting

Cg: /* What is the purpose of the prevEbene-2-Überschrift */

2020-05-06T13:43:26Z

What is the purpose of the prevEbene-2-Überschrift

← Nächstältere Version		Version vom 6. Mai 2020, 13:43 Uhr
Zeile 30:		Zeile 30:
	(*) but in the included libraries you can also find action blocks to start applications, which you can of course insert into a recorded sequence like any other action. However, we recommend that you define the start and stop of actions as separate steps in the test plan. This may disable them to avoid long startup times during test development.		(*) but in the included libraries you can also find action blocks to start applications, which you can of course insert into a recorded sequence like any other action. However, we recommend that you define the start and stop of actions as separate steps in the test plan. This may disable them to avoid long startup times during test development.

	== What is the purpose of the ~~prevEbene-2-Überschrift~~ ==		== What is the purpose of the Preview Window (at the bottom left) ==
	* for windowless applications (headless browser)		* for windowless applications (headless browser)
	* for devices on remote computers (also mobile devices in the server room)		* for devices on remote computers (also mobile devices in the server room)
	* to hold the image of transient (disappearing) windows (i.e. menus and dialogs that disappear in case of focus loss)		* to hold the image of transient (disappearing) windows (i.e. menus and dialogs that disappear in case of focus loss)
	* to enlarge sections		* to enlarge sections
			* to find out geometry data, such as rectangles or positions