WindowsAutomation Reference 2.0 - Versionsgeschichte

Sv: Weiterleitung nach WindowsAutomation Reference 2.0/en erstellt

2018-07-03T10:44:06Z

Weiterleitung nach WindowsAutomation Reference 2.0/en erstellt

Lv: /* Preparing a remote system for test exeuction */

2018-06-04T07:59:23Z

Preparing a remote system for test exeuction

← Nächstältere Version		Version vom 4. Juni 2018, 07:59 Uhr
Zeile 59:		Zeile 59:
	\| -s \|\| Yes \|\| Tells the executable to run in server mode (as opposed to client mode).		\| -s \|\| Yes \|\| Tells the executable to run in server mode (as opposed to client mode).
	\|-		\|-
	\| -k \|\| Yes \|\| Tells the client to keep the connection open after aconnection has been terminated ~~saving~~ you the hassle to restart it every time a test finishes.		\| -k \|\| Yes \|\| Tells the client to keep the connection open after aconnection has been terminated. This saves you the hassle to restart it every time a test finishes.
	\|-		\|-
	\| -a <ip/hostname>\|\| Yes \|\| The IP-Address of the PC your application is running on.		\| -a <ip/hostname>\|\| Yes \|\| The IP-Address of the PC your application is running on.
Zeile 65:		Zeile 65:
	\| -p <int> \|\| No \|\| The port the server should listen on (default is 34318).		\| -p <int> \|\| No \|\| The port the server should listen on (default is 34318).
	\|}		\|}


	=Settings=		=Settings=

Lv: /* Keyboard */

2018-06-04T07:58:22Z

Keyboard

← Nächstältere Version		Version vom 4. Juni 2018, 07:58 Uhr
Zeile 242:		Zeile 242:
	If you need more fine grained control over the keyboard, you can make use of '''Scan Codes'''. The keyboard sends a scan codeto the operating system whenever a key is pressed or released.		If you need more fine grained control over the keyboard, you can make use of '''Scan Codes'''. The keyboard sends a scan codeto the operating system whenever a key is pressed or released.
	Microsoft provides a list of the scan codes it supports [https://docs.microsoft.com/en-us/previous-versions/visualstudio/visual-studio-6.0/aa299374(v=vs.60)].		Microsoft provides a list of the scan codes it supports [https://docs.microsoft.com/en-us/previous-versions/visualstudio/visual-studio-6.0/aa299374(v=vs.60)].
	'''Press Key By Scan Code''' sends Windows a signal that a key with a given scan code has been pressed (and is ~~hold~~ down). The matching '''Release Key By Scan Code''' sends Windows the adverse signal.		'''Press Key By Scan Code''' sends Windows a signal that a key with a given scan code has been pressed (and is held down). The matching '''Release Key By Scan Code''' sends Windows the adverse signal.
	Please note that a key that is pressed, stays pressed until it is explicitly released. If you want to just press and release a key by scan code, use '''Type Key By Scan Code'''.		Please note that a key that is pressed, stays pressed until it is explicitly released. If you want to just press and release a key by scan code, use '''Type Key By Scan Code'''.


	=== Mouse ===		=== Mouse ===

Lv am 30. Mai 2018 um 14:09 Uhr

2018-05-30T14:09:57Z

← Nächstältere Version		Version vom 30. Mai 2018, 14:09 Uhr
Zeile 233:		Zeile 233:
	If you do not want to wait for the mouse to move, you can also use the '''Set Focus''' block instead.		If you do not want to wait for the mouse to move, you can also use the '''Set Focus''' block instead.

			=== Keyboard ===
	===
			The plugin provides blocks interacting with the keyboard on different abstraction levels. The most versatile block is '''Type With Control Keys Pressed''' where you can specify a string of characters to be typed while any number of control keys (e.g. esc, alt, shift, ctrl, ...) are held down. All other blocks are specializations of this block.

			'''Press Control Keys''' e.g. allows you to enter key commands such as renaming files (ALT+F2), starting the task manager (CTRL+ALT+DEL), or closing a window (ALT+F4). '''Press Control Key''' makes it easy to just press a single key (e.g. RETURN to start a new line in an edit box). The '''Shortcuts''' group provides an assorted collection of often used key combinations for your convenience.

			Use the '''Type''' to just type some text or, if you just need some throwaway demo text, use '''Type Random Phrase'''.

			If you need more fine grained control over the keyboard, you can make use of '''Scan Codes'''. The keyboard sends a scan codeto the operating system whenever a key is pressed or released.
			Microsoft provides a list of the scan codes it supports [https://docs.microsoft.com/en-us/previous-versions/visualstudio/visual-studio-6.0/aa299374(v=vs.60)].
			'''Press Key By Scan Code''' sends Windows a signal that a key with a given scan code has been pressed (and is hold down). The matching '''Release Key By Scan Code''' sends Windows the adverse signal.
			Please note that a key that is pressed, stays pressed until it is explicitly released. If you want to just press and release a key by scan code, use '''Type Key By Scan Code'''.


			=== Mouse ===
			The plugin provides blocks manipulating the mouse in three ways: '''Clicking''', '''Moving''', and interacting with its '''Buttons'''.


			<br clear=all>
			== Recording and Taking Screenshots ==

Lv am 30. Mai 2018 um 12:07 Uhr

2018-05-30T12:07:08Z

← Nächstältere Version		Version vom 30. Mai 2018, 12:07 Uhr
Zeile 108:		Zeile 108:
	[[Bild:WindowsAutomation_Library_AccessBlocks.PNG\|frame\|The Library's GUI Element Access Blocks.]]		[[Bild:WindowsAutomation_Library_AccessBlocks.PNG\|frame\|The Library's GUI Element Access Blocks.]]
	[[Bild:WindowsAutomation_Library_AccessBlocksExamples.PNG\|frame\|A Few Examples on How to Access Elements in Notepad.]]		[[Bild:WindowsAutomation_Library_AccessBlocksExamples.PNG\|frame\|A Few Examples on How to Access Elements in Notepad.]]
		⚫	[[Bild:WindowsAutomation_Library_AccessBlocksModes.PNG\|frame\|Different Ways to Reference a GUI Element.]]
	All Windows applications are built as a ''' tree''' of ''' GUI elements''' .		All Windows applications are built as a ''' tree''' of ''' GUI elements''' .
	Some elements act as container of other element - their children. Tables, for example, are containers		Some elements act as container of other element - their children. Tables, for example, are containers
Zeile 157:		Zeile 158:
	: <code>/Window[1]/Document[1] </code>		: <code>/Window[1]/Document[1] </code>
	: <code>/Window[1]/Document[last()] </code>		: <code>/Window[1]/Document[last()] </code>

			'''Please Note''': You can '''only''' use the three predicates above in your XPaths. Other predicates '''DO NOT''' work! If you want to search
			an element by another property (e.g. its help text), use the '''By Property''' variant of the block instead. If the property is not unique,
			you can select a unique ancestor of the target by property or XPath relative to which the property is unique.
			You can then use that ancestor as anchor in the '''Get GUI Element By Property (Relative to Anchor)''' block.

	=== Using Wildcards in XPaths ===		=== Using Wildcards in XPaths ===
Zeile 180:		Zeile 186:

	=== XPath Resolution in Action Blocks ===		=== XPath Resolution in Action Blocks ===

⚫	[[Bild:WindowsAutomation_Library_AccessBlocksModes.PNG\|frame\|Different Ways to Reference a GUI Element.]]
	Getting a reference to the GUI Element everytime you need to manipulate it in any way can make for very unclean looking test suites as two blocks are needed to perform any action - one for getting a reference to the element and another one for perform the action. The library therefore also allows you to directly feed an xpath into every block that would take a reference to a GUI Element.		Getting a reference to the GUI Element everytime you need to manipulate it in any way can make for very unclean looking test suites as two blocks are needed to perform any action - one for getting a reference to the element and another one for perform the action. The library therefore also allows you to directly feed an xpath into every block that would take a reference to a GUI Element.

Zeile 187:		Zeile 193:
	You also can recycle the GUI element reference as seen in 3). This is invaluable as the XPath only has to be resolved once. This speeds up test execution by a lot as XPath resolution is very expensive operation.		You also can recycle the GUI element reference as seen in 3). This is invaluable as the XPath only has to be resolved once. This speeds up test execution by a lot as XPath resolution is very expensive operation.

	'''Rule of thumb''': Always use Variant 1 except if you need the reference to the GUI element ~~not more than~~ once ~~during test execution~~.		'''Rule of thumb''': Always use Variant 1 except if you need the reference to the GUI element only once.

	<br clear=all>		<br clear=all>
Zeile 207:		Zeile 213:
	=== The 'Patterns' Group ===		=== The 'Patterns' Group ===

	This group contains blocks that are applicable to GUI elements supporting a certain '''pattern'''.		This group contains blocks that are applicable to GUI elements supporting a certain '''pattern'''. '''Patterns''' describe how a GUI element '''behaves''' rather than what it '''is'''. An element can also support multiple patterns
			at the same time. You can find out which patterns an element supports with the '''Get Supported Patterns''' block or by taking a look at Microsoft's documentation about patterns [https://docs.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-control-patterns-overview].

			Pattern blocks can therefore be '''re-used''' between GUI elements of different types. The '''Expand''' block of the '''ExpandCollapse pattern''', for example, can be used to expand Comboboxes, Menus, Submenus, or Trees.

	=== The 'Properties' Group ===		=== The 'Properties' Group ===

			Blocks in the '''Patterns''' and '''Elements''' group already allow you to query the value of properties pertaining to that element or pattern. Blocks of the '''Properties''' group allow you to query properties all elements share as well as arbitrary properties. If you try to retrieve a property an element does not support, the block will fail.

			Please note that the '''Get Arbitrary Property''' block can only query for properties that belong to a pattern. You cannot, for example, query "Text" from a textfield as this is not a property, use "Value" of the value pattern instead. Microsoft's documentation has a list of patterns and the properties they provide [https://docs.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-control-patterns-overview#control-pattern-classes-and-interfaces]

			<br clear=all>
	== Automating Keyboard and Mouse ==		== Automating Keyboard and Mouse ==
			[[Bild:WindowsAutomation_Library_KeyboardMouse.png\|frame\|The Library's Blocks for Interacting With Keyboard and Mouse.]]

			You can control keyboard and mouse with the blocks in the groups '''Keyboard''' and '''Mouse''' that can be seen on the right. In contrast to the blocks above which work in context of a GUI element, the keyboard and mouse blocks work on a global level. You therefore do not need to provide a GUI element when using them.

			You might want to execute some blocks in context of a GUI elemenet nontheless (e.g. enter a number into a text field instead of just pressing keys while the application is running). You can achieve this by selecting the element with the mouse beforehand as you would do when using the application normally (use the '''Left/Double/Right Click On Element''' blocks for this).
			If you do not want to wait for the mouse to move, you can also use the '''Set Focus''' block instead.

			===


Zeile 216:		Zeile 239:

	== What is the difference between Click/Invoke/Select/Toggle? ==		== What is the difference between Click/Invoke/Select/Toggle? ==

			== My element supports a certain pattern but blocks of that pattern don't work? ==

			== I have designed custom elements, how can I automate them? ==

			== I have extended my GUI elements to have custom properties, how can I query them? ==

Lv am 30. Mai 2018 um 09:09 Uhr

2018-05-30T09:09:21Z

← Nächstältere Version		Version vom 30. Mai 2018, 09:09 Uhr
Zeile 190:		Zeile 190:

	<br clear=all>		<br clear=all>
	== ~~Manipulating~~ GUI Elements ==		== Interacting with GUI Elements ==
			Once you retrieved a GUI element, you can interact with it by making use of the library's blocks located in the groups '''Elements''', '''Patterns''', and '''Properties'''.
			Blocks in those categories take a GUI Element (and sometimes additional data) as input and manipulate it or query for its properties in some way.

			[[Bild:WindowsAutomation_Library_ElementsPatternsProperties.png\|frame\|The Library's Blocks for Interacting With Elements.]]
	== Checking the State of GUI Elements ==


			=== The 'Elements' Group ===

			This group contains blocks that are applicable to blocks that only work on '''GUI elements of a specific type'''. For a block's detailed description with examples ,
			take a look at the block's documentation in expecco.

			Even though not only Checkboxes can be 'checked', the '''Check''' block in the '''Checkbox group''' only works for checkboxes and not e.g. for radio buttons.
			Because of this limitation there are not that many blocks targeting specific elements. Most blocks target a specific '''pattern''' instead and are therefore in the '''Patterns''' group.

			=== The 'Patterns' Group ===

			This group contains blocks that are applicable to GUI elements supporting a certain '''pattern'''.
			=== The 'Properties' Group ===

			== Automating Keyboard and Mouse ==


			= Frequently Asked Questions =

			== What is the difference between Click/Invoke/Select/Toggle? ==

Lv am 28. Mai 2018 um 15:11 Uhr

2018-05-28T15:11:06Z

← Nächstältere Version		Version vom 28. Mai 2018, 15:11 Uhr
Zeile 179:		Zeile 179:
	You can also search for elements by property by specifying a value an element's property with the given name must have. For a list of properties a GUI element might have, take a look at Microsoft's documentation [https://docs.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-control-patterns-overview#control-pattern-classes-and-interfaces]. It specifies the supported properties for each pattern an element can support.		You can also search for elements by property by specifying a value an element's property with the given name must have. For a list of properties a GUI element might have, take a look at Microsoft's documentation [https://docs.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-control-patterns-overview#control-pattern-classes-and-interfaces]. It specifies the supported properties for each pattern an element can support.

	=== XPath ~~resolution~~ in ~~action~~ ~~blocks~~ ===		=== XPath Resolution in Action Blocks ===
	[[Bild:WindowsAutomation_Library_AccessBlocksModes.PNG\|frame\|Different Ways to Reference a GUI Element.]]		[[Bild:WindowsAutomation_Library_AccessBlocksModes.PNG\|frame\|Different Ways to Reference a GUI Element.]]
	Getting a reference to the GUI Element everytime you need to manipulate it in any way can make for very unclean looking test suites as two blocks are needed to perform any action - one for getting a reference to the element and another one for perform the action. The library therefore also allows you to directly feed an xpath into every block that would take a reference to a GUI Element.		Getting a reference to the GUI Element everytime you need to manipulate it in any way can make for very unclean looking test suites as two blocks are needed to perform any action - one for getting a reference to the element and another one for perform the action. The library therefore also allows you to directly feed an xpath into every block that would take a reference to a GUI Element.

	The image on the right shows this mode in action. Variants 1 and 2 are functionally equivalent.		The image on the right shows this mode in action. Variants 1 and 2 are functionally equivalent.
	While Variant 2 is more concise, Variant 1 is the right choice in most cases.		While Variant 2 is more concise, Variant 1 is the right choice in most cases. While it has an additional block, you have control over the other input parameters.
			You also can recycle the GUI element reference as seen in 3). This is invaluable as the XPath only has to be resolved once. This speeds up test execution by a lot as XPath resolution is very expensive operation.

			'''Rule of thumb''': Always use Variant 1 except if you need the reference to the GUI element not more than once during test execution.

			<br clear=all>
	== Manipulating GUI Elements ==		== Manipulating GUI Elements ==

Lv am 28. Mai 2018 um 14:53 Uhr

2018-05-28T14:53:54Z

← Nächstältere Version		Version vom 28. Mai 2018, 14:53 Uhr
Zeile 179:		Zeile 179:
	You can also search for elements by property by specifying a value an element's property with the given name must have. For a list of properties a GUI element might have, take a look at Microsoft's documentation [https://docs.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-control-patterns-overview#control-pattern-classes-and-interfaces]. It specifies the supported properties for each pattern an element can support.		You can also search for elements by property by specifying a value an element's property with the given name must have. For a list of properties a GUI element might have, take a look at Microsoft's documentation [https://docs.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-control-patterns-overview#control-pattern-classes-and-interfaces]. It specifies the supported properties for each pattern an element can support.

	=== XPath ~~resultion~~ in action blocks ===		=== XPath resolution in action blocks ===
			[[Bild:WindowsAutomation_Library_AccessBlocksModes.PNG\|frame\|Different Ways to Reference a GUI Element.]]
			Getting a reference to the GUI Element everytime you need to manipulate it in any way can make for very unclean looking test suites as two blocks are needed to perform any action - one for getting a reference to the element and another one for perform the action. The library therefore also allows you to directly feed an xpath into every block that would take a reference to a GUI Element.
			The image on the right shows this mode in action. Variants 1 and 2 are functionally equivalent.
			While Variant 2 is more concise, Variant 1 is the right choice in most cases.

		⚫	== Manipulating GUI Elements ==

		⚫	== Checking the State of GUI Elements ==
	<h1>
⚫	Manipulating ~~Gui~~ Elements
	</h1>

	<h1>
⚫	Checking the State of ~~Gui~~ Elements
	</h1>

Lv am 28. Mai 2018 um 14:30 Uhr

2018-05-28T14:30:27Z

← Nächstältere Version		Version vom 28. Mai 2018, 14:30 Uhr
Zeile 107:		Zeile 107:
	== Accessing GUI Elements ==		== Accessing GUI Elements ==
	[[Bild:WindowsAutomation_Library_AccessBlocks.PNG\|frame\|The Library's GUI Element Access Blocks.]]		[[Bild:WindowsAutomation_Library_AccessBlocks.PNG\|frame\|The Library's GUI Element Access Blocks.]]
			[[Bild:WindowsAutomation_Library_AccessBlocksExamples.PNG\|frame\|A Few Examples on How to Access Elements in Notepad.]]
	All Windows applications are built as a ''' tree''' of ''' GUI elements''' .		All Windows applications are built as a ''' tree''' of ''' GUI elements''' .
	Some elements act as container of other element - their children. Tables, for example, are containers		Some elements act as container of other element - their children. Tables, for example, are containers
Zeile 120:		Zeile 121:
	:If ensureExclusive is set and more than one element is found, the block will fail and notify you of the ambiguity. This is disabled by default as checking for uniqueness is a very costly operation.		:If ensureExclusive is set and more than one element is found, the block will fail and notify you of the ambiguity. This is disabled by default as checking for uniqueness is a very costly operation.
	:You can also specify a '''timeout''' after which the search is aborted. This is useful if you know an element should be there soon but might currently be loading.		:You can also specify a '''timeout''' after which the search is aborted. This is useful if you know an element should be there soon but might currently be loading.


	;Get GUI Elements: returns '''all''' GUI Element matching the search condition. If no element is found, it returns an empty list <b> Timeout </b> and <b>cacheXPath</b> are also applicable.		;Get GUI Elements: returns '''all''' GUI Element matching the search condition. If no element is found, it returns an empty list <b> Timeout </b> and <b>cacheXPath</b> are also applicable.
Zeile 129:		Zeile 129:


	=== ~~Constructing~~ XPaths ===		=== Using XPaths ===

	'''XPath''' is the query language this plugin uses for selecting GUI elements in the application's element tree.		'''XPath''' is the query language this plugin uses for selecting GUI elements in the application's element tree.
Zeile 175:		Zeile 175:
	But be careful. Using wildcards comes at a steep <b>performance cost</b>. If your tests run unacceptably slow, first try to '''remove wildcards where they are not needed'''.		But be careful. Using wildcards comes at a steep <b>performance cost</b>. If your tests run unacceptably slow, first try to '''remove wildcards where they are not needed'''.

			=== Using Properties===
	<h2> Accessing by Property </h2>

	<p>
			You can also search for elements by property by specifying a value an element's property with the given name must have. For a list of properties a GUI element might have, take a look at Microsoft's documentation [https://docs.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-control-patterns-overview#control-pattern-classes-and-interfaces]. It specifies the supported properties for each pattern an element can support.
	</p>

	~~<h2>~~ XPath resultion in action blocks ~~</h2>~~		=== XPath resultion in action blocks ===
	<p>

	</p>

	</section>
	<section>
	<h1>		<h1>
	Manipulating Gui Elements		Manipulating Gui Elements
	<h1>		</h1>

	<p>
	</p>
	</section>
	<section>
	<h1>		<h1>
	Checking the State of Gui Elements		Checking the State of Gui Elements
	<h1>		</h1>
	<p>
	</p>
	</section>
	</html>

Lv am 28. Mai 2018 um 13:34 Uhr

2018-05-28T13:34:35Z

Änderungen zeigen