AutoIt Library/en - Versionsgeschichte

Cg: /* Introduction */

2022-03-23T17:51:46Z

Introduction

← Nächstältere Version		Version vom 23. März 2022, 17:51 Uhr
Zeile 12:		Zeile 12:
	* integrates smoothly with database, telecom or automation scenarios.		* integrates smoothly with database, telecom or automation scenarios.

	No attempt was made to support AutoIt's scripting facilities. These are better implemented using expecco's own mechanisms for looping, alternatives, assertions etc.		No attempt was made to support AutoIt's scripting facilities. These are better implemented using expecco's own mechanisms for looping, alternatives, assertions etc. These are also better used by calling autoIt directly, for example via a shell/batch action.

	Also, no integration to the expecco GUI browser is available. This means that neither recording nor inspection of the application's widget hierarchy is supported with autoIt.		Also, no integration to the expecco GUI browser is available. This means that neither recording nor inspection of the application's widget hierarchy is supported with autoIt.

			Be aware, that "autoIt" may be disliked by your IT department (for reasons unknown). You may try our lightweight [[Window Access Library]], which is similar in spirit, but does not need any special access rights or installation. However it does only provide a subset of autoIt's functionality.

	== Installation ==		== Installation ==

Cg: /* Installation */

2022-03-20T10:23:15Z

Installation

← Nächstältere Version		Version vom 20. März 2022, 10:23 Uhr
Zeile 27:		Zeile 27:
	C:\Program Files\AutoIt3\AutoItX\AutoItX3_x64.dll		C:\Program Files\AutoIt3\AutoItX\AutoItX3_x64.dll

	If this is in your path (try "<code>set</code>" on the "<code>cmd.com</code>" command line)~~, you are ready to use it~~. Otherwise, either change the path setting (and restart expecco so it sees it), or go to the expecco [[Settings_ProjectDLLPathSettings/en \| dll-mapping settings]], and add a corresponding entry to the mapping table:		If this is in your path you are ready to use it (try "<code>set</code>" on the "<code>cmd.com</code>" command line).

			Otherwise, either change the path setting (and restart expecco so it sees it), or go to the expecco [[Settings_ProjectDLLPathSettings/en \| dll-mapping settings]], and add a corresponding entry to the mapping table:

	[[Datei:DLL_AutoIt_Mapping.png\|600px]]		[[Datei:DLL_AutoIt_Mapping.png\|600px]]

Cg: /* Installation */

2022-03-20T10:22:26Z

Installation

← Nächstältere Version		Version vom 20. März 2022, 10:22 Uhr
Zeile 29:		Zeile 29:
	If this is in your path (try "<code>set</code>" on the "<code>cmd.com</code>" command line), you are ready to use it. Otherwise, either change the path setting (and restart expecco so it sees it), or go to the expecco [[Settings_ProjectDLLPathSettings/en \| dll-mapping settings]], and add a corresponding entry to the mapping table:		If this is in your path (try "<code>set</code>" on the "<code>cmd.com</code>" command line), you are ready to use it. Otherwise, either change the path setting (and restart expecco so it sees it), or go to the expecco [[Settings_ProjectDLLPathSettings/en \| dll-mapping settings]], and add a corresponding entry to the mapping table:

	[[Datei:DLL_AutoIt_Mapping.png\|~~400px~~]]		[[Datei:DLL_AutoIt_Mapping.png\|600px]]

	<p>		<p>

Cg: /* Installation */

2022-03-20T10:21:56Z

Installation

← Nächstältere Version		Version vom 20. März 2022, 10:21 Uhr
Zeile 22:		Zeile 22:
	Download the AutoIt package and install it with its default settings.		Download the AutoIt package and install it with its default settings.
	<br>Typically, the software is installed in "<code>C:\Program Files\AutoIt3</code>".		<br>Typically, the software is installed in "<code>C:\Program Files\AutoIt3</code>".
	<br>The only component needed by expecco is the AutoIt dll, which should be in		<br>The only component needed by expecco is the AutoIt dll, which should be in:
	C:\Program Files\AutoIt3\AutoItX\AutoItX3.dll		C:\Program Files\AutoIt3\AutoItX\AutoItX3.dll
	or:		or
	C:\Program Files\AutoIt3\AutoItX\AutoItX3_x64.dll		C:\Program Files\AutoIt3\AutoItX\AutoItX3_x64.dll

	If this is in your path (try "<code>set</code>" on the "<code>cmd.com</code>" command line), you are ready to use it. Otherwise, either change the path setting, or go to the expecco [[Settings_ProjectDLLPathSettings/en \| dll-mapping settings]], and add a corresponding entry to the mapping table:		If this is in your path (try "<code>set</code>" on the "<code>cmd.com</code>" command line), you are ready to use it. Otherwise, either change the path setting (and restart expecco so it sees it), or go to the expecco [[Settings_ProjectDLLPathSettings/en \| dll-mapping settings]], and add a corresponding entry to the mapping table:

	[[Datei:DLL_AutoIt_Mapping.png]]		[[Datei:DLL_AutoIt_Mapping.png\|400px]]

	<p>		<p>

Cg: /* Installation */

2022-03-20T10:20:55Z

Installation

← Nächstältere Version		Version vom 20. März 2022, 10:20 Uhr
Zeile 23:		Zeile 23:
	<br>Typically, the software is installed in "<code>C:\Program Files\AutoIt3</code>".		<br>Typically, the software is installed in "<code>C:\Program Files\AutoIt3</code>".
	<br>The only component needed by expecco is the AutoIt dll, which should be in		<br>The only component needed by expecco is the AutoIt dll, which should be in
	~~<code>~~C:\Program Files\AutoIt3\AutoItX\AutoItX3.dll~~</code>~~		C:\Program Files\AutoIt3\AutoItX\AutoItX3.dll
	or		or:
	~~<code>~~C:\Program Files\AutoIt3\AutoItX\AutoItX3_x64.dll~~</code>~~		C:\Program Files\AutoIt3\AutoItX\AutoItX3_x64.dll

	If this is in your path (try "<code>set</code>" on the "<code>cmd.com</code>" command line), you are ready to use it. Otherwise, either change the path setting, or go to the expecco [[Settings_ProjectDLLPathSettings/en \| dll-mapping settings]], and add a corresponding entry to the mapping table:		If this is in your path (try "<code>set</code>" on the "<code>cmd.com</code>" command line), you are ready to use it. Otherwise, either change the path setting, or go to the expecco [[Settings_ProjectDLLPathSettings/en \| dll-mapping settings]], and add a corresponding entry to the mapping table:

Cg: /* Installation */

2022-03-20T10:19:11Z

Installation

← Nächstältere Version		Version vom 20. März 2022, 10:19 Uhr
Zeile 24:		Zeile 24:
	<br>The only component needed by expecco is the AutoIt dll, which should be in		<br>The only component needed by expecco is the AutoIt dll, which should be in
	<code>C:\Program Files\AutoIt3\AutoItX\AutoItX3.dll</code>		<code>C:\Program Files\AutoIt3\AutoItX\AutoItX3.dll</code>
			or
			<code>C:\Program Files\AutoIt3\AutoItX\AutoItX3_x64.dll</code>

	If this is in your path (try "<code>set</code>" on the "<code>cmd.com</code>" command line), you are ready to use it. Otherwise, either change the path setting, or go to the expecco [[Settings_ProjectDLLPathSettings/en \| dll-mapping settings]], and add a corresponding entry to the mapping table:		If this is in your path (try "<code>set</code>" on the "<code>cmd.com</code>" command line), you are ready to use it. Otherwise, either change the path setting, or go to the expecco [[Settings_ProjectDLLPathSettings/en \| dll-mapping settings]], and add a corresponding entry to the mapping table:

Cg: /* Introduction */

2022-03-20T10:18:03Z

Introduction

← Nächstältere Version		Version vom 20. März 2022, 10:18 Uhr
Zeile 13:		Zeile 13:

	No attempt was made to support AutoIt's scripting facilities. These are better implemented using expecco's own mechanisms for looping, alternatives, assertions etc.		No attempt was made to support AutoIt's scripting facilities. These are better implemented using expecco's own mechanisms for looping, alternatives, assertions etc.

			Also, no integration to the expecco GUI browser is available. This means that neither recording nor inspection of the application's widget hierarchy is supported with autoIt.

	== Installation ==		== Installation ==

Cg: /* Applications and Windows Versions */

2019-08-15T09:17:04Z

Applications and Windows Versions

← Nächstältere Version		Version vom 15. August 2019, 09:17 Uhr
Zeile 89:		Zeile 89:
	=== Applications and Windows Versions ===		=== Applications and Windows Versions ===

	~~Notice that many~~ Microsoft applications may show different control ids in their components in different Windows versions and/or language settings. For example, the "<code>calculator.exe</code>" application looks similar in a German language setting to its English counterpart. However, the control keys are different. It is important to keep this in mind and prepare the test suite, to remain portable across different and also future Windows versions.		Many Microsoft applications may show different control ids in their components in different Windows versions and/or language settings. For example, the "<code>calculator.exe</code>" application looks similar in a German language setting to its English counterpart. However, the control keys are different. It is important to keep this in mind and prepare the test suite, to remain portable across different and also future Windows versions.
	A good strategy is to build an application specific control key library or specify the control keys in an environment. This can then be modified, or loaded depending on the OS version. We highly recommend the use of attachment files to keep that information separate from the actual test sequence.		A good strategy is to build an application specific control key library or specify the control keys in an environment. This can then be modified, or loaded depending on the OS version. We highly recommend the use of attachment files to keep that information separate from the actual test sequence.

Cg: /* Local vs. Remote Applications */

2019-08-15T09:16:41Z

Local vs. Remote Applications

← Nächstältere Version		Version vom 15. August 2019, 09:16 Uhr
Zeile 85:		Zeile 85:
	If you use "<code>localhost</code>" as destination parameter to the connect block, the AutoIt local interface (without remote proxy) will be used. In that case no autoitRemoteServer needs to be run on the local host. Otherwise the connect block try to connect to autoitRemoteServer on the specified host.<br/>		If you use "<code>localhost</code>" as destination parameter to the connect block, the AutoIt local interface (without remote proxy) will be used. In that case no autoitRemoteServer needs to be run on the local host. Otherwise the connect block try to connect to autoitRemoteServer on the specified host.<br/>

	Please note, that the autoitRemoteServer may provide only a reduced set of the AutoIt functions. ~~Please refer~~ to the Interface Plugin Library for more information.		Please note, that the autoitRemoteServer may provide only a reduced set of the AutoIt functions. Refer to the Interface Plugin Library for more information.

	=== Applications and Windows Versions ===		=== Applications and Windows Versions ===

Cg: /* Local vs. Remote Applications */

2019-08-15T09:16:25Z

Local vs. Remote Applications

← Nächstältere Version		Version vom 15. August 2019, 09:16 Uhr
Zeile 75:		Zeile 75:

	=== Local vs. Remote Applications ===		=== Local vs. Remote Applications ===
	You can access and control both local and remote applications via this plugin. When interfacing to a local application, expecco uses the AutoIt dll to directly interact with the tested application. To control remote applications, the AutoIt proxy "autoitRemoteServer.com" must be up and running on that host(s). This proxy implements a message-passing interface via a socket interface to forward AutoIt commands from the expecco-host to the application's host. The proxy must be started on the target host with:		You can access and control both local and remote applications via this plugin. When interfacing to a local application, expecco uses the AutoIt dll to directly interact with the tested application. To control remote applications, the AutoIt proxy "<code>autoitRemoteServer.com</code>" must be up and running on that host(s). This proxy implements a message-passing interface via a socket interface to forward AutoIt commands from the expecco-host to the application's host. The proxy must be started on the target host with:
	autoitRemoteServer.com hostnameOrIpAddress portNumber		autoitRemoteServer.com hostnameOrIpAddress portNumber

	Notice that the "autoitRemoteServer.com" possibly opens a security leak, as it allows for external programs to connect and control/manipulate the windows on the screen. Therefore, it is recommended to restrict the access and make sure that only the test-system on which expecco runs gains access to it. The parameter "''hostnameOrIpAddress''" restricts remote access to that single host. Use "localhost" or "127.0.0.0" if you want to deny any external access, and only allow the expecco which runs on the same host to connect to it. Otherwise specify your own hostname or IP address.		Notice that the "autoitRemoteServer.com" possibly opens a security leak, as it allows for external programs to connect and control/manipulate the windows on the screen. Therefore, it is recommended to restrict the access and make sure that only the test-system on which expecco runs gains access to it. The parameter "''hostnameOrIpAddress''" restricts remote access to that single host. Use "<code>localhost</code>" or "<code>127.0.0.0</code>" if you want to deny any external access, and only allow the expecco which runs on the same host to connect to it. Otherwise specify your own hostname or IP address.
	The "portNumber" parameter is optional. The default is 9998.<br/>		The "''portNumber''" parameter is optional. The default is <code>9998</code>.<br/>

	So, if the application to be tested executes on "hostA", and expecco on "hostE", open a command interface on "hostA" and enter "<code>autoitRemoteServer.com hostE</code>". Use "hostA" as the destination-parameter of the connect block.		So, if the application to be tested executes on "hostA", and expecco on "hostE", open a command interface on "hostA" and enter "<code>autoitRemoteServer.com hostE</code>". Use "hostA" as the destination-parameter of the connect block.

	If you use "localhost" as destination parameter to the connect block, the AutoIt local interface (without remote proxy) will be used. In that case no autoitRemoteServer needs to be run on the local host. Otherwise the connect block try to connect to autoitRemoteServer on the specified host.<br/>		If you use "<code>localhost</code>" as destination parameter to the connect block, the AutoIt local interface (without remote proxy) will be used. In that case no autoitRemoteServer needs to be run on the local host. Otherwise the connect block try to connect to autoitRemoteServer on the specified host.<br/>

	Please note, that the autoitRemoteServer may provide only a reduced set of the AutoIt functions. Please refer to the Interface Plugin Library for more information.		Please note, that the autoitRemoteServer may provide only a reduced set of the AutoIt functions. Please refer to the Interface Plugin Library for more information.