VisualWorks Testing Plugin Reference/en - Versionsgeschichte

Cg: /* Problem Statement */

2023-07-18T13:30:30Z

Problem Statement

← Nächstältere Version		Version vom 18. Juli 2023, 13:30 Uhr
Zeile 6:		Zeile 6:
	[[Datei:VW_in_GuiBrowser_WA.png\|450px]]		[[Datei:VW_in_GuiBrowser_WA.png\|450px]]

	as you can see, VisualWorks looks to the outside world as a single big window - no input fields, buttons, lists etc. are visible.		as you can see, VisualWorks looks to the outside world as a single big window - no input fields, buttons, lists etc. are visible (except for the buttons in the window's caption area).

Cg: /* Problem Statement */

2023-07-18T13:29:01Z

Problem Statement

← Nächstältere Version		Version vom 18. Juli 2023, 13:29 Uhr
Zeile 1:		Zeile 1:
	= Problem Statement =		= Problem Statement =
	Graphical VisualWorks ("VW") applications do not use "proper" windows to represent widgets such as buttons, input fields etc. Thus, most UI automation and testing tools will not be able to automate VisualWorks applications on a logical widget level. Instead, they ~~will~~ see a single window, and you have to navigate to widgets by position offset or image detection mechanisms. They ~~will~~ also no be able to extract attributes (such as selection index, text contents, enabled state etc.), and you have to use mechanisms like bitmap image comparison to find elements and OCR (optical character recognition) to extract semantic data (text contents) from the VW user interface.		Graphical VisualWorks ("VW") applications do not use "''proper''" windows to represent widgets such as buttons, input fields etc. All widgets are drawn into a single top-level view. Thus, most UI automation and testing tools will not be able to automate VisualWorks applications on a logical widget level. Instead, they see a single window, and you have to navigate to widgets by position/offset or image detection mechanisms. They are also no be able to extract attributes (such as selection index, text contents, enabled state etc.), and you have to use mechanisms like bitmap image comparison to find elements and OCR (optical character recognition) to extract semantic data (text contents) from the VW user interface.

	Typical UI inspection tools will present VisualWorks application windows as shown in this screenshot (which shows what WindowsAutomation sees):		Typical UI inspection tools will present VisualWorks application windows as shown in this screenshot (which shows what WindowsAutomation sees):

Cg am 18. März 2021 um 08:30 Uhr

2021-03-18T08:30:38Z

← Nächstältere Version		Version vom 18. März 2021, 08:30 Uhr
Zeile 153:		Zeile 153:
	This is preliminary information; the plugin is being developed and major changes are to be expected.		This is preliminary information; the plugin is being developed and major changes are to be expected.

	[[Category: Plugins/en]]		[[Category: Plugins/en]]<br>
	[[Category: Advanced/en]]		[[Category: Advanced/en]]<br>

Cg am 18. März 2021 um 08:16 Uhr

2021-03-18T08:16:33Z

← Nächstältere Version		Version vom 18. März 2021, 08:16 Uhr
Zeile 152:		Zeile 152:

	This is preliminary information; the plugin is being developed and major changes are to be expected.		This is preliminary information; the plugin is being developed and major changes are to be expected.

			[[Category: Plugins/en]]
			[[Category: Advanced/en]]

Cg am 21. September 2020 um 05:37 Uhr

2020-09-21T05:37:33Z

← Nächstältere Version		Version vom 21. September 2020, 05:37 Uhr
Zeile 140:		Zeile 140:
	This means, that widgets (currently) have to be addressed via an xpath, which usually enumerates (parts of) the hierarchy-path, instead of a single automationID.		This means, that widgets (currently) have to be addressed via an xpath, which usually enumerates (parts of) the hierarchy-path, instead of a single automationID.

	To better support automatic tests, VW-application ~~programmes~~ should provide a unique id as a property of the component:		To better support automatic tests, VW-application programs should provide a unique id as a property of the component:
	someComponent propertyAt:'automationID' put:<someUniqueID>		someComponent propertyAt:'automationID' put:<someUniqueID>
	where <someUniqueID> can be a string or a UUID.		where <someUniqueID> can be a string or a UUID.

Cg: /* Locating Widgets by XPath */

2020-09-21T00:01:36Z

Locating Widgets by XPath

← Nächstältere Version		Version vom 21. September 2020, 00:01 Uhr
Zeile 88:		Zeile 88:
	=== Locating Widgets by XPath ===		=== Locating Widgets by XPath ===

	VisualWorks widgets are referred t ~~ousing~~ an XPath locator.		VisualWorks widgets are referred to using an XPath locator.
	Notice, that the XPath implementation (inside the VW image) supports a subset of the full XPath feature set,		Notice, that the XPath implementation (inside the VW image) supports a subset of the full XPath feature set,
	and that (currently) the verbose syntax (i.e. like "/child::tag") is not supported.		and that (currently) the verbose syntax (i.e. like "/child::tag") is not supported.

Cg: /* Code Execution */

2020-09-21T00:00:26Z

Code Execution

← Nächstältere Version		Version vom 21. September 2020, 00:00 Uhr
Zeile 53:		Zeile 53:
	[[Datei:NewVWSmalltalkActionCode1.png\|450px]]		[[Datei:NewVWSmalltalkActionCode1.png\|450px]]

	The VW-action will be executed inside your VW image. Thus, these blocks allow you to open additional windows, to interact with custom interfaces, custom widgets or to start background processes inside VisualWorks. It is also possible to interact with model objects, as long as you provide some accessors as class methods (of course, as a Smalltalker, you can get any object eg. with "someClass allInstances do:[...]"; however it is less obscure, if you use concrete getter methods).		The VW-action will be executed inside your VW image. Thus, these blocks allow you to open additional windows, to interact with custom interfaces, custom widgets or to start background processes inside VisualWorks. It is also possible to interact with model objects, as long as you provide some accessors as class methods (of course, as an experienced Smalltalker, you can get any object eg. with "<CODE>someClass allInstances do:[...]</CODE>"; however it is less obscure, if you use concrete getter methods).

	== GUIBrowser Integration ==		== GUIBrowser Integration ==

Cg: /* Code Execution */

2020-09-20T23:59:24Z

Code Execution

← Nächstältere Version		Version vom 20. September 2020, 23:59 Uhr
Zeile 47:		Zeile 47:
	[[Datei:newVWSmalltalkAction_de.png\|200px]]		[[Datei:newVWSmalltalkAction_de.png\|200px]]

	The instantiated action will execute a dummy default action, ~~whichz~~ simply outputs some text onto the (expecco-) Transcript (not the remote Smalltalk's Transcript). Make sure to show the expecco console ("Extras" - "Tools" - "Transcript") before you run this action.		The instantiated action will execute a dummy default action, which simply outputs some text onto the (expecco-) Transcript (not the remote Smalltalk's Transcript). Make sure to show the expecco console ("Extras" - "Tools" - "Transcript") before you run this action.

	You can change the code, for example to open a new application inside the VisualWorks image:		You can change the code, for example to open a new application inside the VisualWorks image:

Cg: /* Introduction */

2020-09-20T23:57:57Z

Introduction

← Nächstältere Version		Version vom 20. September 2020, 23:57 Uhr
Zeile 13:		Zeile 13:
	= Introduction =		= Introduction =

	The VisualWorks plugin interfaces to running VisualWorks applications via the expecco bridge protocol, which is based on the common bridge protocol described [[ Embedded_Systems_C_Bridge_API#Bridge_Wire_Protocol \| here ]].		The VisualWorks plugin interfaces to running VisualWorks applications via the expecco bridge protocol, which is based on the common bridge protocol described [[ Embedded_Systems_C_Bridge_API#Bridge_Wire_Protocol \| here]].

	The plugin provides the following functionality:		The plugin provides the following functionality:

Cg: /* Problem Statement */

2020-09-20T23:57:29Z

Problem Statement

← Nächstältere Version		Version vom 20. September 2020, 23:57 Uhr
Zeile 3:		Zeile 3:

	Typical UI inspection tools will present VisualWorks application windows as shown in this screenshot (which shows what WindowsAutomation sees):		Typical UI inspection tools will present VisualWorks application windows as shown in this screenshot (which shows what WindowsAutomation sees):

	<br>
	[[Datei:VW_in_GuiBrowser_WA.png\|450px]]		[[Datei:VW_in_GuiBrowser_WA.png\|450px]]

	~~<br>~~as you can see, VisualWorks looks to the outside world as a single big window - no input fields, buttons, lists etc. are visible.		as you can see, VisualWorks looks to the outside world as a single big window - no input fields, buttons, lists etc. are visible.