Mobile Testing Plugin/en - Versionsgeschichte

Matilk: /* Windows */ new supplement

2025-02-17T09:42:58Z

Windows: new supplement

← Nächstältere Version		Version vom 17. Februar 2025, 09:42 Uhr
Zeile 35:		Zeile 35:
	== Windows ==		== Windows ==
	The easiest way is to install everything from our Mobile Testing Supplement. However, newer versions do not contain a JDK anymore due to a change in Oracle's license terms, so you have to install it additionally. Of course, you are free to install Appium directly to use the version you want. However, to then be able to start an Appium server with expecco, a suitable batch file must be available and specified in the [[Mobile_Testing_Plugin/en#Plugin_Configuration\|settings]]. However, connections can also be established to other running Appium servers.		The easiest way is to install everything from our Mobile Testing Supplement. However, newer versions do not contain a JDK anymore due to a change in Oracle's license terms, so you have to install it additionally. Of course, you are free to install Appium directly to use the version you want. However, to then be able to start an Appium server with expecco, a suitable batch file must be available and specified in the [[Mobile_Testing_Plugin/en#Plugin_Configuration\|settings]]. However, connections can also be established to other running Appium servers.
	*'''expecco 24.1''': [https://download.exept.de/transfer/h-expecco-24.1.0/MobileTestingSupplement.exe Mobile Testing Supplement 1.13.3.3]		*'''expecco 24.2''': [https://download.exept.de/transfer/h-expecco-24.2.0/MobileTestingSupplement.exe Mobile Testing Supplement 2.0.1.1]
			:Migration to Appium 2. The Appium server starts as default without the path ''wd/hub/''.
			:Appium 2.11.0
			:Node 20.9.0
			:adb 1.0.41 from platform-tools 35.0.1
			*expecco 24.1: [https://download.exept.de/transfer/h-expecco-24.1.0/MobileTestingSupplement.exe Mobile Testing Supplement 1.13.3.3]
	:Same versions as in the predecessor, but with updated chromedriver versions		:Same versions as in the predecessor, but with updated chromedriver versions
	*expecco 23.2: [https://download.exept.de/transfer/h-expecco-23.2.0/MobileTestingSupplement.exe Mobile Testing Supplement 1.13.3.2]		*expecco 23.2: [https://download.exept.de/transfer/h-expecco-23.2.0/MobileTestingSupplement.exe Mobile Testing Supplement 1.13.3.2]

Matilk: /* Windows */

2024-07-24T14:27:38Z

Windows

← Nächstältere Version		Version vom 24. Juli 2024, 14:27 Uhr
Zeile 45:		Zeile 45:
	:Node 14.17.5		:Node 14.17.5
	:adb 1.0.41 from platform-tools 33.0.2		:adb 1.0.41 from platform-tools 33.0.2
	:''* We added the capability'' ~~startChromedriverTimeout~~ ''to Appium, to get a timeout earlier, if Chromedriver cannot be initialized. (see [[#startChromedriverTimeout\|Problems and Solutions]])''		:''* We added the capability'' chromedriverStartTimeout ''to Appium, to get a timeout earlier, if Chromedriver cannot be initialized. (see [[#startChromedriverTimeout\|Problems and Solutions]])''
	*expecco 21.2: [https://download.exept.de/transfer/h-expecco-21.2.0/MobileTestingSupplement.exe Mobile Testing Supplement 1.12.0.0]		*expecco 21.2: [https://download.exept.de/transfer/h-expecco-21.2.0/MobileTestingSupplement.exe Mobile Testing Supplement 1.12.0.0]
	:Contains Appium version 1.22.0, Node still is version 12.13.1.		:Contains Appium version 1.22.0, Node still is version 12.13.1.

Matilk: /* Problems and Solutions */ org.openqa.selenium.StaleElementReferenceException

2024-07-23T09:48:46Z

Problems and Solutions: org.openqa.selenium.StaleElementReferenceException

← Nächstältere Version		Version vom 23. Juli 2024, 09:48 Uhr
Zeile 700:		Zeile 700:
	== Invisible UI Elements ==		== Invisible UI Elements ==
	Note that the [[#Recorder\|Recorder]] also considers items that you cannot see on the screen. Therefore, turn on element highlighting or use the follow mouse function and the element tree in the GUI browser to determine if the correct element is used. It can happen, that invisible elements are in front of other elements and cover them, so that the desired element cannot be selected in the recorder. See section [[#Hide_elements\|Hide elements]] for a solution to this.		Note that the [[#Recorder\|Recorder]] also considers items that you cannot see on the screen. Therefore, turn on element highlighting or use the follow mouse function and the element tree in the GUI browser to determine if the correct element is used. It can happen, that invisible elements are in front of other elements and cover them, so that the desired element cannot be selected in the recorder. See section [[#Hide_elements\|Hide elements]] for a solution to this.

			==''org.openqa.selenium.StaleElementReferenceException''==
			The error <code>org.openqa.selenium.StaleElementReferenceException</code> occurs whenever an element is used that is no longer there. If that happens during your test and the element should have been there, try using the locator (xPath) instead to fetch the element again.

			In some cases this error can also occur even if you already use a locator at the action block. This is because the locator is always resolved first and the corresponding element is fetched and the action is then executed with this element. If the app refreshes the element exactly between the resolving and fetching part and the execution, creating a new element, this error occurs. If it happens at a specific point in your test, your best option is to catch the error and retry.

	== iOS: Cable not certified ==		== iOS: Cable not certified ==

Matilk: /* Windows */ new supplement

2024-07-11T09:37:37Z

Windows: new supplement

← Nächstältere Version		Version vom 11. Juli 2024, 09:37 Uhr
Zeile 35:		Zeile 35:
	== Windows ==		== Windows ==
	The easiest way is to install everything from our Mobile Testing Supplement. However, newer versions do not contain a JDK anymore due to a change in Oracle's license terms, so you have to install it additionally. Of course, you are free to install Appium directly to use the version you want. However, to then be able to start an Appium server with expecco, a suitable batch file must be available and specified in the [[Mobile_Testing_Plugin/en#Plugin_Configuration\|settings]]. However, connections can also be established to other running Appium servers.		The easiest way is to install everything from our Mobile Testing Supplement. However, newer versions do not contain a JDK anymore due to a change in Oracle's license terms, so you have to install it additionally. Of course, you are free to install Appium directly to use the version you want. However, to then be able to start an Appium server with expecco, a suitable batch file must be available and specified in the [[Mobile_Testing_Plugin/en#Plugin_Configuration\|settings]]. However, connections can also be established to other running Appium servers.
	*'''expecco 23.2''': [https://download.exept.de/transfer/h-expecco-23.2.0/MobileTestingSupplement.exe Mobile Testing Supplement 1.13.3.2]		*'''expecco 24.1''': [https://download.exept.de/transfer/h-expecco-24.1.0/MobileTestingSupplement.exe Mobile Testing Supplement 1.13.3.3]
			:Same versions as in the predecessor, but with updated chromedriver versions
			*expecco 23.2: [https://download.exept.de/transfer/h-expecco-23.2.0/MobileTestingSupplement.exe Mobile Testing Supplement 1.13.3.2]
	:Same versions as in the predecessor, but with updated chromedriver versions		:Same versions as in the predecessor, but with updated chromedriver versions
	*expecco 23.1: [https://download.exept.de/transfer/h-expecco-23.1.0/MobileTestingSupplement.exe Mobile Testing Supplement 1.13.3.1]		*expecco 23.1: [https://download.exept.de/transfer/h-expecco-23.1.0/MobileTestingSupplement.exe Mobile Testing Supplement 1.13.3.1]

Cg: /* Introduction */

2024-06-27T15:50:15Z

Introduction

← Nächstältere Version		Version vom 27. Juni 2024, 15:50 Uhr
Zeile 2:		Zeile 2:

	= Introduction =		= Introduction =
	~~With the~~ ''Mobile Testing Plugin'' ~~applications~~ ~~can~~ be ~~tested~~ on Android and iOS devices. This includes both real and emulated devices. It does not matter whether real mobile devices or emulated devices are used. The plugin can (and usually is) used in conjunction with the [[Expecco_GUI_Tests_Extension_Reference\|GUI-Browser]], which supports the creation of tests. It can also be used to record test procedures.		The ''Mobile Testing Plugin'' adds mechanisms to test and automate Android and iOS devices. This includes both real and emulated devices - it does not matter whether real mobile devices or emulated devices are used. The plugin can (and usually is) used in conjunction with the [[Expecco_GUI_Tests_Extension_Reference\|GUI-Browser]], which supports the creation of tests. It can also be used to record test procedures.

	[http://appium.io/ Appium] is used to connect to the devices. Appium is a free open source framework for testing and automating mobile applications.		[http://appium.io/ Appium] is used to connect to the devices. Appium is a free open source framework for testing and automating mobile applications.

Matilk: /* Windows */ new supplement version

2023-12-22T09:42:59Z

Windows: new supplement version

← Nächstältere Version		Version vom 22. Dezember 2023, 09:42 Uhr
Zeile 35:		Zeile 35:
	== Windows ==		== Windows ==
	The easiest way is to install everything from our Mobile Testing Supplement. However, newer versions do not contain a JDK anymore due to a change in Oracle's license terms, so you have to install it additionally. Of course, you are free to install Appium directly to use the version you want. However, to then be able to start an Appium server with expecco, a suitable batch file must be available and specified in the [[Mobile_Testing_Plugin/en#Plugin_Configuration\|settings]]. However, connections can also be established to other running Appium servers.		The easiest way is to install everything from our Mobile Testing Supplement. However, newer versions do not contain a JDK anymore due to a change in Oracle's license terms, so you have to install it additionally. Of course, you are free to install Appium directly to use the version you want. However, to then be able to start an Appium server with expecco, a suitable batch file must be available and specified in the [[Mobile_Testing_Plugin/en#Plugin_Configuration\|settings]]. However, connections can also be established to other running Appium servers.
	*'''expecco 23.1''': [https://download.exept.de/transfer/h-expecco-23.1.0/MobileTestingSupplement.exe Mobile Testing Supplement 1.13.3.1]		*'''expecco 23.2''': [https://download.exept.de/transfer/h-expecco-23.2.0/MobileTestingSupplement.exe Mobile Testing Supplement 1.13.3.2]
			:Same versions as in the predecessor, but with updated chromedriver versions
			*expecco 23.1: [https://download.exept.de/transfer/h-expecco-23.1.0/MobileTestingSupplement.exe Mobile Testing Supplement 1.13.3.1]
	:Same versions as in the predecessor, but the installer now allows to add Appium to the Autostart.		:Same versions as in the predecessor, but the installer now allows to add Appium to the Autostart.
	*expecco 22.2 and 22.1: [https://download.exept.de/transfer/h-expecco-22.1.0/MobileTestingSupplement.exe Mobile Testing Supplement 1.13.2.0]		*expecco 22.2 and 22.1: [https://download.exept.de/transfer/h-expecco-22.1.0/MobileTestingSupplement.exe Mobile Testing Supplement 1.13.2.0]

Matilk: /* Signing WebDriverAgent */ wdaLaunchTimeout

2023-11-30T11:57:56Z

Signing WebDriverAgent: wdaLaunchTimeout

← Nächstältere Version		Version vom 30. November 2023, 11:57 Uhr
Zeile 234:		Zeile 234:

	Read also the documentation of Appium on [https://github.com/appium/appium-xcuitest-driver/blob/master/docs/real-device-config.md Setting up tests with iOS devices]. Refer to the [https://support.apple.com/en-us/HT204460 Apple documentation] for details on installing and trusting of apps.		Read also the documentation of Appium on [https://github.com/appium/appium-xcuitest-driver/blob/master/docs/real-device-config.md Setting up tests with iOS devices]. Refer to the [https://support.apple.com/en-us/HT204460 Apple documentation] for details on installing and trusting of apps.

			Once the WebDriverAgent is installed on the device, it will be reused for later connections und connecting should work faster. The signed version is then already on your Mac as well and doesn't have to be built again. This should speed up the connect with other devices as well. If you know, that the connect has to build and sign the WebDriverAgent first, it is advisable to set the capability ''wdaLaunchTimeout''. This timeout specifies how long Appium waits for the WebDriverAgents to start up on the device and is per default set to 60000 ms. Building often takes a little longer than one minute, so the connect attempt will be canceled. A value of 120000 will be more reliable here.

	== Plugin Configuration ==		== Plugin Configuration ==

Matilk: /* Problems and Solutions */ first iOS connect

2023-11-30T11:45:33Z

Problems and Solutions: first iOS connect

← Nächstältere Version		Version vom 30. November 2023, 11:45 Uhr
Zeile 703:		Zeile 703:
	== iOS: .ipa cannot be installed ==		== iOS: .ipa cannot be installed ==
	Note that on iOS simulators no ''.ipa'' files can be installed but only ''.app'' files.		Note that on iOS simulators no ''.ipa'' files can be installed but only ''.app'' files.

			==iOS: First Connect is not working==
			If there is not already a signed build of the WebDriverAgent on your Mac, it has to be created during the first connect. Usually, this can take a little longer than one minute. Per default Appium uses a timeout of 60000 ms to wait for the WebDriverAgent to start on the device, so the connect will be canceled in that case. You can set this timeout with the capability ''wdaLaunchTimeout'', e.g. to ''120000''.

			Moreover, the signing settings have to be correct. In our experience, the most reliable solution is to set automatic signing in the WebDriverAgent Xcode project an selecting the team there. See the explanation in section [[#Signing_WebDriverAgent\|Signing WebDriverAgent]] for that. In this case you should '''not''' use the capabilities ''xcodeConfigFile'' resp. ''xcodeOrgId'' and ''xcodeSigningId'', as they could cause a conflict. Caution: If you have set a Team ID in the Mobile Testing settings, expecco will automatically set this as ''xcodeOrgId''!

			Pay attention to your device during the first connect. You might have to agree to the installation by entering your password. On the Mac you might need to enter the password to allow access to the key chain for signing, often several times.

	== Android: Device not visible in the connect editor ==		== Android: Device not visible in the connect editor ==

Matilk: Link to German version

2023-09-01T12:19:57Z

Link to German version

← Nächstältere Version		Version vom 1. September 2023, 12:19 Uhr
Zeile 1:		Zeile 1:
			[[Mobile_Testing_Plugin\|Deutsche Version]] \| '''English Version'''

	= Introduction =		= Introduction =
	With the ''Mobile Testing Plugin'' applications can be tested on Android and iOS devices. This includes both real and emulated devices. It does not matter whether real mobile devices or emulated devices are used. The plugin can (and usually is) used in conjunction with the [[Expecco_GUI_Tests_Extension_Reference\|GUI-Browser]], which supports the creation of tests. It can also be used to record test procedures.		With the ''Mobile Testing Plugin'' applications can be tested on Android and iOS devices. This includes both real and emulated devices. It does not matter whether real mobile devices or emulated devices are used. The plugin can (and usually is) used in conjunction with the [[Expecco_GUI_Tests_Extension_Reference\|GUI-Browser]], which supports the creation of tests. It can also be used to record test procedures.

Matilk: /* Windows */ new supplement version

2023-06-22T09:33:53Z

Windows: new supplement version

← Nächstältere Version		Version vom 22. Juni 2023, 09:33 Uhr
Zeile 33:		Zeile 33:
	== Windows ==		== Windows ==
	The easiest way is to install everything from our Mobile Testing Supplement. However, newer versions do not contain a JDK anymore due to a change in Oracle's license terms, so you have to install it additionally. Of course, you are free to install Appium directly to use the version you want. However, to then be able to start an Appium server with expecco, a suitable batch file must be available and specified in the [[Mobile_Testing_Plugin/en#Plugin_Configuration\|settings]]. However, connections can also be established to other running Appium servers.		The easiest way is to install everything from our Mobile Testing Supplement. However, newer versions do not contain a JDK anymore due to a change in Oracle's license terms, so you have to install it additionally. Of course, you are free to install Appium directly to use the version you want. However, to then be able to start an Appium server with expecco, a suitable batch file must be available and specified in the [[Mobile_Testing_Plugin/en#Plugin_Configuration\|settings]]. However, connections can also be established to other running Appium servers.
	*'''expecco 22.1''': [https://download.exept.de/transfer/h-expecco-22.1.0/MobileTestingSupplement.exe Mobile Testing Supplement 1.13.2.0]		*'''expecco 23.1''': [https://download.exept.de/transfer/h-expecco-23.1.0/MobileTestingSupplement.exe Mobile Testing Supplement 1.13.3.1]
			:Same versions as in the predecessor, but the installer now allows to add Appium to the Autostart.
			*expecco 22.2 and 22.1: [https://download.exept.de/transfer/h-expecco-22.1.0/MobileTestingSupplement.exe Mobile Testing Supplement 1.13.2.0]
	:Appium 1.22.3*		:Appium 1.22.3*
	:Node 14.17.5		:Node 14.17.5