Quamotion WebDriver Documentation

Transcription

1 Quamotion WebDriver Documentation Release 0.1 Quamotion Aug 17, 2018

2

3 Contents 1 How it works 3 2 Use the tools you re familiar with 5 3 Requirements 7 i

4 ii

5 Quamotion is a test automation framework for use with native, hybrid and mobile web apps. It automates ios and Android apps on real devices (ios, Android), simulators (ios) and emulators (Android), using the WebDriver protocol. Contents 1

6 2 Contents

7 CHAPTER 1 How it works Quamotion makes automated testing easy. We let you focus on testing your app, while we take care of the heavy lifting required to automate it. We don t require you to include a SDK or recompile your app; nor do you have to jailbreak your device. You know best how to do your job, so we let you use your favourite test practices, frameworks and tools. 3

8 4 Chapter 1. How it works

9 CHAPTER 2 Use the tools you re familiar with Quamotion allows you to use any language and any test framework to automate your mobile app. You can write tests using your favourite testing tools, and we expose the WebDriver API which allows you to use interact with your app from any programming language. 5

10 6 Chapter 2. Use the tools you re familiar with

11 CHAPTER 3 Requirements Quamotion works on: Windows 7 (64-bit) and above Ubuntu (64-bit) and above OS X (64-bit) and above and allows you to test: ios 8 and above (97+% of all ios devices) Android 4.1 and above (96+% of all Android devices) You don t need to install any platform-specific tools such as Xcode or the Android SDK. You can test ios devices using a Windows or Linux PC, even if you don t have a Mac. Getting Started Quamotion is a test automation framework for use with native, hybrid and mobile web apps. It automates ios and Android apps on real devices (ios, Android), simulators (ios) and emulators (Android), using the WebDriver protocol. Supported Platforms ios 8 and above (97+% of all ios devices) Android 4.1 and above (96+% of all Android devices) Why Quamotion? Quamotion makes testing mobile apps easy. We let you focus on testing your app, while we take care of the heavy lifting required to automate it. You don t have to recompile your app or modify it in any way: we automate your app using the built-in automation tools of each platform. You can write tests in any language or tool that supports WebDriver. That includes languages and scripting platforms such as Java, PowerShell and C#. You can use any testing framework that supports those languages. 7

12 Using the WebDriver protocol is using a single, free and open protocol for testing that has become a proposed W3C standard. This way, you avoid being locked in to vendor-specific languages. Requirements You ll need either a Mac, Linux or Windows PC: Mac OS X or higher (64-bit) Ubuntu or higher (64-bit) RedHat Enterprise Linux 7 or higher (64-bit), or compatible distribution such as CentOS. Windows 7 or higher (64-bit) From a hardware point of view, the minimum requirements to develop mobile test automation scripts are: An dual-core Intel i5 (Sandy Bridge or newer) or better processor 4 GB RAM 100 GB of free disk space on a SSD disk A display resolution of 1600 x 900 or better 1 available USB 2.0 port per device, providing at least 750 ma of power to the device Contact us for hardware specifications for servers running continuous tests. That s it! You don t need to install any other tool for you to get started. Install Quamotion OS X To install the Quamotion server, you first need install the latest version of OpenSSL. Let s do that using HomeBrew: brew update brew install openssl ln -s /usr/local/opt/openssl/lib/libcrypto dylib /usr/local/lib/ ln -s /usr/local/opt/openssl/lib/libssl dylib /usr/local/lib/ Next, you can download and install the Quamotion server: mkdir quamotion-webdriver cd quamotion-webdriver wget \char \discretionary{-}{}{}webdriver osx.10.10\unhbox\voidb@x\kern\ z@\char \discretionary{-}{}{}x64.tar.gz tar -xvzf quamotion-webdriver osx x64.tar.gz To start the Quamotion server, you can simply launch the Quamotion.WebDriver executable:./quamotion.webdriver The Quamotion server will now start. You can connect to the Quamotion server using any browser, by navigating to 8 Chapter 3. Requirements

13 Linux Ubuntu To install the Quamotion server, you first need install a couple of dependencies. You can install them using apt-get: sudo apt-get update sudo apt-get install -y libunwind8 libicu55 libc++-dev zlib1g Next, you can download and install the Quamotion server. For Ubuntu: mkdir quamotion-webdriver wget \char \discretionary{-}{}{}webdriver ubuntu.16.04\unhbox\voidb@x\kern\ z@\char \discretionary{-}{}{}x64.tar.gz tar -xvzf quamotion-webdriver ubuntu x64.tar.gz To start the Quamotion server, you can simply launch the Quamotion.WebDriver executable:./quamotion.webdriver RedHat and CentOS For RedHat or CentOS, we provide RPM packages for you. First, add our repository: yum install -y epel-release wget -nv -nc qmfrederik.repo -O /etc/yum.repos.d/quamotion.repo Then, download the latest RPM package and install it. wget \char \discretionary{-}{}{}webdriver rhel.7.0\unhbox\voidb@x\kern\ z@\char \discretionary{-}{}{}x64.rpm yum install quamotion-webdriver rhel.7.0-x64.rpm The Quamotion server will start automatically. You can connect to the Quamotion server using any browser, by navigating to Windows To install the Quamotion server: Download the latest version Extract the quamotion-webdriver win7-x64.zip file Double-click the Quamotion.WebDriver.exe file. The Quamotion server will now start. You can connect to the Quamotion server using any browser, by navigating to Use a trial license You can request and upload a trial license in the Quamotion Frontend Getting Started 9

14 Prerequisites Before you request a trial license you need to install and start the Quamotion WebDriver. Retrieve a trial license 1. Start a browser and navigate to 2. Click on Request Trial License 3. Fill in the from. Your machine identifier is pre-filled. 10 Chapter 3. Requirements

15 4. Press the Send Request button. 5. A mail is send with your license file attached. 6. Store the license file on your local hard-disk Upload the trial license 1. Start a browser and navigate to 2. Press the Update License button Getting Started 11

16 3. Press the Choose File button and select the saved license file. 4. Press the Update button. 5. Restart the Quamotion WebDriver Configure local devices USB Configuration We recommend you connect your mobile devices to your test server using a USB connection. In this case, we recommend you use: A dedicated PCIe USB 3.0 controller A powered USB 3.0 hub, where each port is capable of providing at least 900mA to each device simultaneously High quality USB cables WiFi configuration You can also connect to your mobile devices over WiFi. If you want to connect to mobile devices over WiFi, we recommend: You set up a dedicated WiFi network and access point for your mobile devices Your server connects to the WiFi access point over Ethernet Your server and devices are in the same subnet There is a ping latency of less than 5ms between the server and the devices Specific information on how to configure Andoid and ios devices can found in: Connect Android devices Quamotion can work with physical Android devices, such as tablets or phones, that you connect to your PC. To work with these devices, you need to connect them to your PC using a USB cable, and the devices need to be configured to work with the Android Debug Bridge. This article describes how you can connect an Android device to your PC for use with Quamotion 12 Chapter 3. Requirements

17 Configuring USB Debugging the Device For Quamotion to be able to communicate with your device, you need to configure USB Debugging on the device. To configure USB Debugging, follow these steps on the device: 1. On the Home screen, tap the Apps button 2. In the Apps screen, open the Settings app 3. In the Settings screen, in the System section, tap About 4. Tap Software Information 5. Tap the Build Number text at least 6 times, until the You are now a developer message appears. 6. Tap back until you reach the Settings screen and tap Developer Options, in the System section 7. Tap USB Debugging in the Debugging section. When asked to confirm, tap OK Connect the device to your PC To connect your device to your PC, follow these steps: 1. Connect your device to your PC using a USB cable. 2. If a window, Allow USB Debugging, appears on your device, tap Always allow from this computer and tap OK 3. Verify if the device appears in the devices page of the Quamotion frontend Prepare the device for automation It is advised enable the stay awake setting. This prevents the screen to be locked during a test run. 1. On the Home screen, tap the Apps button 2. In the Apps screen, open the Settings app 3. In the Settings screen, in the System section, tap Developer Options 4. Toggle the Stay awake setting (the screen will never sleep while charging) Lowering the the screen brightness optimises the battery life. 1. On the Home screen, tap the Apps button 2. In the Apps screen, open the Settings app 3. Tap Display in the Settings screen 4. Tap Brightness in the Screen section 5. Disable the Automatic brightness 6. Move the brightness slider to the minimum If possible disable the pin code 1. On the Home screen, tap the Apps button 2. In the Apps screen, open the Settings app 3. Tap on Screen lock (or security -> Screen lock on some devices) 4. Tap on Password and enter the pin code 3.1. Getting Started 13

18 5. Select None or Swipe if possible. Installing the USB Driver If your device does not appear when you run adb devices, your computer may be missing a driver for your device. If your device manufacturer provides you with a driver for your device, please install the driver from your device manufacturer. If not, you can attempt to install a generic Android device driver: 1. Open the Windows Device Manager 2. In the Device Manager, locate your Anroid device. Right-click your Android device and select Update Driver Software 3. Select Browse my computer for driver software 4. Select Let me pick from a list of device drivers on my computer 5. Select Show All Devices and click Next 6. Click Have Disk 7. Click Browse and navigate to to C:Program Files (x86)quamotionextadkextrasgoogleusb_driver 8. Select Android ADB Interface from the list of device types, and click Next 9. Click Yes to confirm the installation of the driver. 10. When asked Would you like to install this device software, click Install to confirm. 11. When the installation completes, click Close to close the window. To confirm the driver for your device has been installed properly, repeat the steps in the previous section. Connect ios devices Quamotion can work with physical ios devices, such as tablets or phones, that you connect to your PC. To work with these devices, you need to connect them to your PC using a USB cable. This article describes how you can connect an ios device to your PC for use with Quamotion Connect the device to your PC To connect your device to your PC, follow these steps: 1. Connect your device to your PC using a USB cable. 2. If a window, Trust This Computer?, appears on your device, tap Trust 3. Verify if the device appears in the devices page of the Quamotion frontend Prepare the device for automation For some features (Full Device Automation, popup handling) you need to enable the UI Automation setting on the device. This setting is only be visible after the first launch of a session. 1. On the Home screen, open the Settings app 14 Chapter 3. Requirements

19 2. Tap on the Developer setting. (this option only appears after you have launched a first session) 3. Toggle the Enable UI Automation setting It is advised disable the Auto Lock setting. This prevents the screen to be locked during a test run. Additionally you can lower the screen brightness to optimise the battery life. 1. On the Home screen, open the Settings app 2. Tap on the Display and Brightness setting. 3. Disable the Auto-Brightness setting and set the brightness slider to the minimum. 4. Tap on the Auto Lock setting 5. Select Never and go back to the Home screen. Disable the pin code 1. On the Home screen, open the Settings app 2. Tap on the Touch ID and Passcode setting. 3. Tap on the Turn Passcode Off setting If you want to test on ios devices, you also need to install the ios developer disks and configure a developer profile. Install the ios Developer Disk When Quamotion runs tests on an ios device, it uses some of the Apple Developer tools to perform key tasks. Examples of such tasks include installing or launching an application, and capturing screenshots. These tools are not installed on ios devices by default. They can be added to the ios device by mounting the developer disk. If you run your app on a device using XCode, XCode mounts the developer disk for you. Quamotion can mount the developer disk for you, but you need to install the ios Developer Disk on your PC before Quamotion can mount it. To install the ios Developer Disk on your PC, you need to download it from a Mac machine and copy it to your PC. Follow these steps: Downloading the ios Developer Disk from a Mac machine 1. On a Mac machine, make sure the latest version of XCode is installed 2. Navigate to the /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Devic and create a zip archive that contains the contents of this folder. 3. Copy this zip archive to your Windows PC. Installing the ios Developer Disk on your PC 1. On the PC where you have installed Quamotion, navigate to C:\Program Files (x86)\quamotion\automation\ios 2. Make a new folder called devimg. 3. Extract the content of the zip archive you ve just created on your Mac machine to this devimg folder Getting Started 15

20 Configuring Developer Profiles If you want to test ios applications, you need to configure a developer profile. A developer profile is a file with the.developerprofile extension, which contains: An ios Code Signing Certificate, which is used to sign ios applications An ios Provisioning Profile, which allows you to install applications which are signed with your code signing certificate on a set of devices you ve registered with the portal. You need to use an ios Code Signing Certificate that is valid, and that allows you to run applications that have not yet been submitted to the app store on your ios device. Your developer profile must allow you to install apps your devices. Obtaining the ios Code Signing Certificate using XCode If you or a developer on your team already has an ios Code Signing Certificate, the easiest way for you to obtain the ios Code Signing Certificate is by exporting it from XCode. To do so, follow these steps: 1. On your Mac machine, open Xcode and click Xcode, Preferences In the Preferences window, choose Accounts 3. At the bottom of the Accounts window, click the gear icon, and choose Export Accounts 4. In the Save dialog, choose a file name and enter a password to protect the file. You will need this password later. 5. If a warning appears about Xcode exporting the private key, click Allow Obtaining the ios Code Signing Certificate using the Quamotion Command Line Utility If nobody on your team has an ios Code Signing Certificate, the easies way for you to obtain the ios Code Signing Certificate is to use the Quamotion Command Line Utility. To complete this step, you need to have an Apple Developer Account with an active subscription. You can find out more at the Apple Developer site. To do so, type the following command: Quamotion.CommandLine CreateDeveloperProfile -f {file} -a {accountname} -b {accountpassword} -p {password} where {file} is the name of the developer profile you want to create, for example, quamotion.developerprofile, {accountname} and {accountpassword} are the username and password you use to log on to the Apple Developer site, and {password} is the password you want to use to protect the developer profile. More information on how to manage ios Developer Profiles on Windows can be found on manage-developer-profile Installing the ios Code Signing Certificate in Quamotion 1. Copy the file you ve created in the previous step to the folder in which you ve installed the Quamotion Web- Driver. This can be on a different machine, and that machine can be a Mac, Linux or Windows machine. 2. Open the appsettings.json file 16 Chapter 3. Requirements

21 3. Change the value of the developerprofilepath property to the path of the developer profile. 4. Change teh value of the developerprofilepassword property to the password you ve used to protect the file. Getting Started with the Quamotion Frontend The Quamotion Frontend is a web based interface helping you to manage the quality of your applications. The Dashboard page provides an overwiew of the results from the test scripts you ve executed. The Apps page contain all applications and version you use to test. The Devices page shows all devices which are available for testing. The Spy page enables you to inspect the user interface of an application and provides the option to record a scenario from the device. To access the Quamotion Front-End: 1. Ensure that you are connected to the Quamotion machine as a normal user. 2. Start a browser and navigate to The following documents give more information on how to use each page. Manage your test results The Dashboard page reports the results of the test scripts you ve executed. 1. In the top navigation, click Dashboard. The Dashboard page opens Getting Started with the Quamotion Frontend 17

22 frontend/..-on-lab.png 2. The two top pie charts in the All Results section display the number of tests you ve executed, and the number of devices on which you ve executed those tests. 3. The Key Metrics section displays key metrics about your test campaign - such as the total device time, the number of devices and operating systems, and the size of the application under test. 4. The Failure Breakdown section displays the test results by operating system and manufacturer. 5. You can click any link the failure breakdown section to view more information about those failures. Click on any link in the operatig system section. 6. The Test Result Details page will appear. This page contains all tests you ve executed which match the criteria you ve specified. 18 Chapter 3. Requirements

23 frontend/..-on-lab-result-details.png 7. Click on any test in the test results list. 8. The test report appears. The test report contains a detailed view of all steps that have been executed in the test report, including screenshots Getting Started with the Quamotion Frontend 19

24 frontend/..-on-lab-report.png Manage your applications To access the apps page click on Apps in the top navigation. A list of all applications which are available for testing is shown. By default, this list is empty. 20 Chapter 3. Requirements

25 Add an application: 1. At the bottom of the page, click the New button. The New App dialog appears 2. Click the Choose File button, and select the application file (.apk or.ipa). 3. Click Add to add the application. The New App dialog closes, and the Apps screen becomes visible. The app is now listed in the list of available applications. Retrieve information about an application 1. Click on the app icon for which you want to retrieve information. 2. The dialog shows the unique identiefer and version number of this application. 3. Information about the embedded provioning profile is also shown in case of an ios application. Remove an application: 1. Click on the app icon you want to remove. 2. Click on Remove and confirm with Are you sure to remove this app. The dialog closes and the app is removed from the list of applications. Manage your devices To access the devices page, click on Devices in the top navigation. The devices page shows a list of all ios and Android devices which are available for testing. If no ios or Android devices are connected to your PC using an USB cable, this list is empty Getting Started with the Quamotion Frontend 21

26 The Devices page will automatically update when you connect or disconnect a device (android or ios) to your PC via usb. Click on a device icon to retrieve more information about the device (device identifier, installed operating system,...) A list of the installed applications is also displayed. On android you can import an application from the device into the app repository. Open the screenshotfeed for a device 1. Click on the device icon for which you want to open the screenshotfeed 2. Click on Remote screen. The screenshotfeed opens in a new window. Open the System Log from a device 1. Click on the device icon for which you want to open the System log 2. Click on System Log. The System Log opens in a new window. On ios the syslog and on Android the logcat information is displayed in real time. Create your script with the Quamotion Spy To access the Spy page, click on Spy in the top navigation. 22 Chapter 3. Requirements

27 The Spy page helps to inspect the user interface of an application. When spying you ll be able to inspect the individual objects of the application s UI. You can later use these objects in your automation scripts. Create a Spy Session To inspect an application it is nessesary to launch the application on a device (i.e. create a session). 1. Select the right platform (Android or ios). 2. Select the application you want to automate. Only applications corresponding to the selected platform will be displayed. 3. Select the device on which you want to run the application. Only devices corresponding to the selected platform will be displayed. 4. Click Start to start a session. A dialog appears showing the progress of starting the session. The dialog disapears once the application is launched and the application is ready to be inspected. Both the screenshotfeed and the spy tools appear. Hint: you can collapse the settings pane with the arrow in the upper left corner. Spy on a paricular object in the screen Once the session is started you are able to spy on each object in the screen. 1. Click on an object in the screenshotfeed Getting Started with the Quamotion Frontend 23

28 2. The object will be highlighted in a red rectangle. The Spy tab provides more information about the selected object. the Selected object suggests a xpath which you can use to identify the object. the Object hierarchy dispays a tree view with all user interface objects of your application which are related to the object you ve just selected. Hint: there is also an option to show the full object hierarchy by clicking on the full tree button Review the properties of a paricular object in the screen Properties of the selected object are listed in the Properties tab. 24 Chapter 3. Requirements

29 You can use the text box to filter the properties which are being displayd. e.g. type access in the text box. and only properties related to accessibility are being displayed. Use the Code Generator to compose a script The Code Generator assists in automating your test scenarios. A script is suggested based on a sequence of actions and validation steps. The steps can be added manually or can be recorded from the device. The Code Generator tab shows all actions and validation steps added since the last page load. By default, this list is empty. Suggested scripts are made available in different languages on the Code tab Getting Started with the Quamotion Frontend 25

30 Add an action manually 1. Select the action or validation step you want to add. The list of available actions is a subset of the possibilies offered in the different clients. Consult the PowerShell Reference to see all possibilies. 2. Press Add 3. Fill the arguments if nessesary. Available elements in the frontend: Removes the corresponding step Drag this step to another place Collapse the arguments of the corresponding step Edit the arguments of the corresponding step Executes the corresponding step Use the suggested xpath as value of this argument Locate the xpath in the current screen Record actions 1. Press the Record button 2. Perform actions on the device. Click, enter text, back actions are autotmatically added to the list. Each step can be edited, removed or reordered. View the suggested code Code is suggested for the actions and validation steps in the Code Generator. Multiple languages can be selected. The suggested code can be pasted and edited in the appropriate editor. 26 Chapter 3. Requirements

31 Quamotion WebDriver Clients There are multiple client libraries available: Quamotion PowerShell Client Because PowerShell is a scripted language, and not a compiled language, it is easier to create and edit scripts as you go. However, all the scripts you re about the write in PowerShell could easily be written in Java or C#. The Quamotion PowerShell Client is included in the Quamotion WebDriver package. Installing PowerShell Make sure you have the latest PowerShell installed on your machine. We recommend to install PowerShell 5 or higher. Windows You can find installers for the most recent PowerShell on Select you operating system and download / install the most resent PowerShell. On Windows you can use the Shell or the PowerShell editor. To launch the editor 1. Click on Windows Start 2. Launch Windows PowerShell ISE application. MacOs Install PowerShell for MacOS if you want to create scripts using MacOS:.. code-block:: bash wget 0-alpha.9.pkg sudo installer -pkg powershell alpha.9.pkg -target / 3.3. Quamotion WebDriver Clients 27

32 Linux Install PowerShell for Linux if you want to create scripts on Linux: For Ubuntu: wget powershell_6.0.0-alpha.9-1ubuntu _amd64.deb sudo dpkg -i powershell_6.0.0-alpha.9-1ubuntu _amd64.deb For RedHat or CentOS: sudo yum install alpha.9/powershell-6.0.0_alpha.9-1.el7.centos.x86_64.rpm Automate with PowerShell To load the Quamotion WebDriver PowerShell module you can use the Import-Module function. Add this line at the start of your script. Import-Module "path-to-quamotion-webdriver\wdclient.psm1" If needed modify the execution policy for PowerShell. Please find more information about this function on https: //technet.microsoft.com/en-us/library/ee aspx Set-ExecutionPolicy Unrestricted Quamotion C# Client This document describes how to create a NUnit test in C# to automate your tests. Create a new NUnit project To create a new NUnit project, follow these steps: 1. Open Visual Studio by clicking Start, typing Visual Studio and hitting ENTER. 2. When Visual Studio has opened, click File, New, Project 3. Under Templates, Visual C#, Windows, select Class Library. 4. Select.NET Framework as the target framework. 5. Provide a name for your project, such as AcquaintanceTest and click OK to create your project. 28 Chapter 3. Requirements

33 You ve now created your first test project! Add the required dependencies to your project Before you can write mobile tests, you need to add some required dependencies to your project. In Visual Studio, dependencies are imported as NuGet packages. To create a mobile test with Quamotion and NUnit, you need to add the quamotion-webdriver-client, NUnit and NUnit3TestAdapter packages. To add the Quamotion and NUnit NuGet packages: 1. In the Solution Explorer, right-click the AcquaintanceTest project and select Manage NuGet packages. 2. In the NuGet: Acquaintance Test window, Click Browse, select Include prerelease and search for quamotionwebdriver-client Quamotion WebDriver Clients 29

34 3. Click the quamotion-webdriver-client NuGet package and click Install. 4. In the Review Changes screen, review the changes and click OK. 30 Chapter 3. Requirements

35 5. In the NuGet: Acquaintance Test window, Click Browse and search for NUnit. 6. Click the NUnit NuGet package and click Install. 7. In the Review Changes window, review the changes and click OK. 8. In the NuGet: Acquaintance Test window, Click Browse and search for NUnit3TestAdapter. 9. Click the NUnit3TestAdapter NuGet package and click Install. 10. In the Review Changes window, review the changes and click OK. 11. You can now close the NuGet: AcquaintanceTest window. Add a test which launches the ios Acquaint app (using NUNIT) NUnit tests allow you to write [SetUp] methods, which are executed before your tests launch. You ll use the [SetUp] method to create a new session, which will start the Acquaint app on your device. To create a new session, you create a new instance of the AppDriver class. To create a new instance of this class, you need to provide an AppCapabilities object which specifies which application you want to start, and on which device you want to start the application. Once you ve created a [SetUp] method, you also need to make sure your session is closed when your test completes. You can do this by adding an [TearDown] method, which runs ater your test has completed. In this [TearDown] method, you ll stop the application on the device by removing the session you ve created in the [SetUp] method. You can do so by calling the Quit() method on the AppDriver class. 1. Rename the Class1 class to AcquaintTest. public class AcquintantTest { } 2. To indicate the test is a NUnit test, add the [TestFixture] attribute to the test. [TestFixture] public class AcquintantTest 3.3. Quamotion WebDriver Clients 31

36 { } 3. Add the code which will initialize your session. You ll also add a variable which stores the current session: [TestFixture] public class AcquintantTest { private AppDriver driver; [SetUp] public void SetUp() { AppCapabilities capabilities = new AppCapabilities( deviceid: "221373bf136e8e8962fe978e74f4c92af330c6ba", appid: "demo.quamotion.acquaint", appversion: "1.51", clearapplicationsettings: false); } } this.driver = new AppDriver(capabilities); this.driver.waituntilready(); 4. Add the code which removes your session. [TestFixture] public class AcquintantTest { private AppDriver driver; [..] } [TearDown] public void TearDown() { this.driver.close(); } 5. Add a placeholder for the test you ll write in the next task [TestFixture] public class AcquintantTest { [..] } [Test] public void EditAcquaintanceTest() { } You can test the test scripts 1. In the Solution Explorer, right click the AcquaintanceTest project and select Build. 2. Click Test, Windows, Test Explorer. The Test Explorer pane will appear 32 Chapter 3. Requirements

37 3. Right click the EditAcquaintanceTest test and click Run. It may take a few seconds, the but Acquaint application will launch on your device and will then close. Quamotion Java Client Quamotion provides a Java library as an extension of the selenium Java library. This document describes how to write your tests as JUnit tests. Create a new JUnit project To create a new JUnit project in IntelliJ: 1. Start IntelliJ 2. Click File, New and Project 3. Select Maven, and set the Project SDK to at least Complete the GroupId, ArtificatId and Version fields. 5. Complete the Project Name and Location fields Add the required dependencies to your project As a next step, add the required dependencies to your project. 1. In the Dependencies, add the following code between the <project> and </project> tags: <dependencies> <dependency> <groupid>junit</groupid> <artifactid>junit</artifactid> <version>4.12</version> </dependency> <dependency> <groupid>org.seleniumhq.selenium</groupid> 3.3. Quamotion WebDriver Clients 33

38 <artifactid>selenium-java</artifactid> <version>2.53.0</version> </dependency> </dependencies> 2. IntelliJ will ask you to import the changes in the Maven project. Click Import Changes. Add the Quamotion library to your project Add the QuamotionDriver.Java library to your project. This library will allow you to automate ios and Android applications from within your Maven project. 1. Right-click your project and select Open Module Settings 2. Click Libraries 3. Click the plus (+) icon to add a library 4. Select Java 5. Add the QuamotionDriver.Java.jar file, which is available for download at windows.net/download/quamotiondriver.java-0.2.jar 6. Click OK 7. Click OK. Write your tests JUnit tests allow you to methods, which are executed before your test launch. Use method to create a new session, which will start the application on your device. To create a new session, you create a new instance of the AppDriver class. To create a new instance of this class, you need to provide an AppCapabilities object which specifies which application you want to start, and on which device you want to start the application. Once you ve created method, you also need to make sure your session is closed when your test completes. You can do this by adding method, which runs after your test has completed. In method, 34 Chapter 3. Requirements

39 you ll stop the application on the device by removing the session you ve created in method. You can do so by calling the quit() method on the AppDriver class. 1. Right-click a package and select New and Java Class 2. Provide a name for your test, such as AcquaintTest 3. Add the code which will initialize your session: AppDriver driver = public void setup2() throws Exception { AppCapabilities capabilities = new AppCapabilities("deviceId", "AppId", "AppVersion"); capabilities.reusesession(true); driver = new AppDriver(capabilities); driver.waituntilready(); } 4. Add the code which will clean up your public void teardown() { driver.quit(); } 5. Add public void FirstTest() throws IOException { } Quamotion Python Client We refer to for more information about how to use the Quamotion WebDriver Python client.s Quamotion PowerShell reference This page contains an overview of all functions in the Quamotion PowerShell library Accept-Alert Commands This page contains details on Accept-Alert commands. Accept-Alert NAME Accept-Alert SYNOPSIS Accepts the visible alert window. SYNTAX Accept-Alert [[-sessionid] <String>] [<CommonParameters>] 3.4. Quamotion PowerShell reference 35

40 DESCRIPTION Accepts the visible alert window. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Accept-Alert REMARKS To see the examples, type: get-help Accept-Alert -examples. For more information, type: get-help Accept-Alert -detailed. For technical information, type: get-help Accept-Alert -full. Add-App Commands This page contains details on Add-App commands. Add-App NAME Add-App SYNOPSIS Adds an application to the application repository SYNTAX Add-App [[-path] <String>] [<CommonParameters>] DESCRIPTION Adds an application to the application repository PARAMETERS -path <String> <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Add-App -path c:appsquamotion.apk REMARKS To see the examples, type: get-help Add-App -examples. For more information, type: get-help Add-App -detailed. For technical information, type: get-help Add-App -full. Clear-Text Commands This page contains details on Clear-Text commands. Clear-Text NAME Clear-Text SYNOPSIS Clears the active text element SYNTAX Clear-Text [[-sessionid] <String>] [<CommonParameters>] DESCRIPTION Clears the active text element PARAMETERS 36 Chapter 3. Requirements

41 -sessionid <String> (Optional) The identifier of the session to route the command to. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Clear-Text REMARKS To see the examples, type: get-help Clear-Text -examples. For more information, type: get-help Clear-Text -detailed. For technical information, type: get-help Clear-Text -full. Click-AlertButton Commands This page contains details on Click-AlertButton commands. Click-AlertButton NAME Click-AlertButton SYNOPSIS Clicks on an alert button. SYNTAX Click-AlertButton [-sessionid <String>] [-button] <String> [<CommonParameters>] DESCRIPTION Clicks on an alert button. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. -button <String> The name of the button to click <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Click-AlertButton -button Ok REMARKS To see the examples, type: get-help Click-AlertButton -examples. For more information, type: gethelp Click-AlertButton -detailed. For technical information, type: get-help Click-AlertButton -full. Click-Coordinate Commands This page contains details on Click-Coordinate commands. Click-Coordinate NAME Click-Coordinate SYNOPSIS Performs a click on a coordinate. SYNTAX Click-Coordinate [-sessionid <String>] [-x] <Int32> [-y] <Int32> [<CommonParameters>] DESCRIPTION Performs a click on a coordinate. The coordinate is measured from the top left corner of the screen. PARAMETERS 3.4. Quamotion PowerShell reference 37

42 -sessionid <String> (Optional) The identifier of the session to route the command to. -x <Int32> x coordinate of the start point relative from the element -y <Int32> y coordinate of the start point relative from the element s.example Click-Coordinate -x 100 -y 100 <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( REMARKS To see the examples, type: get-help Click-Coordinate -examples. For more information, type: gethelp Click-Coordinate -detailed. For technical information, type: get-help Click-Coordinate -full. Click-Element Commands This page contains details on Click-Element commands. Click-Element NAME Click-Element SYNOPSIS Clicks on the first element whose locator matches the given value. SYNTAX Click-Element [-sessionid <String>] -xpath <String> [<CommonParameters>] Click-Element [-sessionid <String>] -marked <String> [<CommonParameters>] Click-Element [-sessionid <String>] -elementid <String> [<CommonParameters>] DESCRIPTION Clicks on the first element whose locator matches the given value. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. -elementid <String> -xpath <String> The xpath used to locate elements. -marked <String> The marked attribute value used to locate elements. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Click-Element -xpath *[@marked= login ] Click-Element -marked login Click-Element -class UIView REMARKS To see the examples, type: get-help Click-Element -examples. For more information, type: get-help Click-Element -detailed. For technical information, type: get-help Click-Element -full. Close-Window Commands This page contains details on Close-Window commands. 38 Chapter 3. Requirements

43 Close-Window NAME Close-Window SYNOPSIS Close the current window. SYNTAX Close-Window [[-sessionid] <String>] [<CommonParameters>] DESCRIPTION Close the current window. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Close-Window REMARKS To see the examples, type: get-help Close-Window -examples. For more information, type: get-help Close-Window -detailed. For technical information, type: get-help Close-Window -full. ConnectTo-Quamotion Commands This page contains details on ConnectTo-Quamotion commands. ConnectTo-Quamotion NAME ConnectTo-Quamotion SYNOPSIS Connects to a remote WebDriver instance. SYNTAX ConnectTo-Quamotion [[-at] <String>] [<CommonParameters>] DESCRIPTION Connects to a remote WebDriver instance. The commands are forwared to the given remote url. PARAMETERS -at <String> The url of the remote WebDriver instance. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>ConnectTo-Quamotion -at REMARKS To see the examples, type: get-help ConnectTo-Quamotion -examples. For more information, type: get-help ConnectTo-Quamotion -detailed. For technical information, type: get-help ConnectTo-Quamotion -full. Delete-AppSettings Commands This page contains details on Delete-AppSettings commands Quamotion PowerShell reference 39

44 Delete-AppSettings NAME Delete-AppSettings SYNOPSIS Deletes the application settings of an installed application. SYNTAX Delete-AppSettings [-deviceid] <String> [-appid] <String> [<CommonParameters>] DESCRIPTION Deletes the application settings of an installed application. PARAMETERS -deviceid <String> The device identifier -appid <String> The application identifier <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Delete-AppSettings -appid demo.quamotion.acquaint -deviceid $iphone6 REMARKS To see the examples, type: get-help Delete-AppSettings -examples. For more information, type: gethelp Delete-AppSettings -detailed. For technical information, type: get-help Delete-AppSettings -full. Dismiss-Keyboard Commands This page contains details on Dismiss-Keyboard commands. Dismiss-Keyboard NAME Dismiss-Keyboard SYNOPSIS Dismisses an open keyboard SYNTAX Dismiss-Keyboard [[-sessionid] <String>] [<CommonParameters>] DESCRIPTION Dismisses an open keyboard PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Dismiss-Keyboard REMARKS To see the examples, type: get-help Dismiss-Keyboard -examples. For more information, type: gethelp Dismiss-Keyboard -detailed. For technical information, type: get-help Dismiss-Keyboard -full. Enable-LocationServices Commands This page contains details on Enable-LocationServices commands. 40 Chapter 3. Requirements

45 Enable-LocationServices NAME Enable-LocationServices SYNTAX Enable-LocationServices [-deviceid] <string> [-locationservices] <string[]> [<CommonParameters>] PARAMETERS -deviceid <string> -locationservices <string[]> <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( ALIASES None REMARKS None Enter-Text Commands This page contains details on Enter-Text commands. Enter-Text NAME Enter-Text SYNOPSIS Send a sequence of key strokes to the active element. SYNTAX Enter-Text [-sessionid <String>] [-text] <String> [<CommonParameters>] DESCRIPTION Send a sequence of key strokes to the active element. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. -text <String> The keys sequence to be sent. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Enter-Text Quamotion REMARKS To see the examples, type: get-help Enter-Text -examples. For more information, type: get-help Enter-Text -detailed. For technical information, type: get-help Enter-Text -full. Find-Element Commands This page contains details on Find-Element commands. Find-Element NAME Find-Element SYNOPSIS Search for an element whose xpath matches the given value Quamotion PowerShell reference 41

46 SYNTAX Find-Element [-sessionid <String>] [-xpath] <String> [-ignorevisibility <Boolean>] [-parentelement <String>] [<CommonParameters>] DESCRIPTION Search for an element whose xpath attribute matches the given value. Returns: the first element whose xpath attribute matches the given value. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. -xpath <String> The xpath used to locate elements. -ignorevisibility <Boolean> (Optional) indicates whether non visible elements should be taken into account. -parentelement <String> (Optional) limits the search to only descendants of this element. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Find-Element -xpath *[@marked= login ] REMARKS To see the examples, type: get-help Find-Element -examples. For more information, type: get-help Find-Element -detailed. For technical information, type: get-help Find-Element -full. Find-ElementByCoordinate Commands This page contains details on Find-ElementByCoordinate commands. Find-ElementByCoordinate NAME Find-ElementByCoordinate SYNOPSIS Search for the top element in the current window on position (x, y). SYNTAX Find-ElementByCoordinate [-sessionid <String>] [-x] <Int32> [-y] <Int32> [<CommonParameters>] DESCRIPTION Search for the top element in the current window on position (x, y). The coordinates are expressed in pixels and measured from the top left corner. Returns: the element on position (x, y) PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. -x <Int32> The x coordinate -y <Int32> the y coordinate <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Find-ElementByCoordinate -x 200 -y 500 REMARKS To see the examples, type: get-help Find-ElementByCoordinate -examples. For more information, type: get-help Find-ElementByCoordinate -detailed. For technical information, type: get-help Find- ElementByCoordinate -full. 42 Chapter 3. Requirements

47 Find-ElementById Commands This page contains details on Find-ElementById commands. Find-ElementById NAME Find-ElementById SYNOPSIS Search for a element whose identifier matches the given value. SYNTAX Find-ElementById [-sessionid <String>] [-id] <String> [<CommonParameters>] DESCRIPTION Search for element whose identifier attribute matches the given value. Returns: the first element whose identifier attribute matches the given value. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. -id <String> The indentifier of the element to search. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Find-ElementById -id REMARKS To see the examples, type: get-help Find-ElementById -examples. For more information, type: gethelp Find-ElementById -detailed. For technical information, type: get-help Find-ElementById -full. Find-ElementFlex Commands This page contains details on Find-ElementFlex commands. Find-ElementFlex NAME Find-ElementFlex SYNOPSIS Searches for an element matching a given locator value. SYNTAX Find-ElementFlex [-sessionid <String>] -class <String> [<CommonParameters>] Find-ElementFlex [-sessionid <String>] -xpath <String> [<CommonParameters>] Find-ElementFlex [-sessionid <String>] -marked <String> [<CommonParameters>] DESCRIPTION Searches for an element matching the locator value. Returns: the first element matching the locator value. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. -xpath <String> (xpath locator) The value for the xpath locator -class <String> (class locator) The value for the class locator -marked <String> (Marked locator) The value for the marked locator 3.4. Quamotion PowerShell reference 43

48 <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Find-ElementFlex -marked Login Find-ElementFlex -xpath *[@marked= Login ] Find-ElementFlex -class UIView REMARKS To see the examples, type: get-help Find-ElementFlex -examples. For more information, type: gethelp Find-ElementFlex -detailed. For technical information, type: get-help Find-ElementFlex -full. Find-Elements Commands This page contains details on Find-Elements commands. Find-Elements NAME Find-Elements SYNOPSIS Search for all elements whose xpath matches the given value. SYNTAX Find-Elements [-sessionid <String>] [-xpath] <String> [-ignorevisibility <Boolean>] [-parentelement <String>] [<CommonParameters>] DESCRIPTION Search for all elements whose xpath attribute matches the given value. Returns: all elements whose xpath attribute matches the given value. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. -xpath <String> The xpath used to locate elements. -ignorevisibility <Boolean> (Optional) indicates whether non visible elements should be taken into account. -parentelement <String> (Optional) limits the search to only descendants of this element. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Find-Elements -xpath *[@marked= login ] REMARKS To see the examples, type: get-help Find-Elements -examples. For more information, type: get-help Find-Elements -detailed. For technical information, type: get-help Find-Elements -full. Find-ElementsById Commands This page contains details on Find-ElementsById commands. Find-ElementsById NAME Find-ElementsById SYNOPSIS Search for all elements whose identifier matches the given value. 44 Chapter 3. Requirements

49 SYNTAX Find-ElementsById [-sessionid <String>] [-id] <String> [<CommonParameters>] DESCRIPTION Search for all elements whose identifier attribute matches the given value. Returns: all elements whose identifier attribute matches the given value. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. -id <String> The indentifier of the element to search. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Find-ElementsById -id REMARKS To see the examples, type: get-help Find-ElementsById -examples. For more information, type: gethelp Find-ElementsById -detailed. For technical information, type: get-help Find-ElementsById -full. Flick-Coordinate Commands This page contains details on Flick-Coordinate commands. Flick-Coordinate NAME Flick-Coordinate SYNOPSIS Performs a flick based on coordinates. SYNTAX Flick-Coordinate [[-sessionid] <String>] [-elementid] <Int32> [-x] <Int32> [-y] <Int32> [-xoffset] <Int32> [-yoffset] <Int32> [-speed] <Int32> [<CommonParameters>] DESCRIPTION Performs a flick based on coordinates. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. -elementid <Int32> The identifier of the element. -x <Int32> x coordinate of the start point relative from the element -y <Int32> y coordinate of the start point relative from the element -xoffset <Int32> the horizontal distance to flick -yoffset <Int32> -speed <Int32> the speed of the flick movement <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Flick-Coordinate -elementid x 100 -y 100 -xoffset 0 -yoffset -300 REMARKS To see the examples, type: get-help Flick-Coordinate -examples. For more information, type: gethelp Flick-Coordinate -detailed. For technical information, type: get-help Flick-Coordinate -full Quamotion PowerShell reference 45

50 Flick-Element Commands This page contains details on Flick-Element commands. Flick-Element NAME Flick-Element SYNOPSIS Performs a flick on an element. SYNTAX Flick-Element [-sessionid <String>] -xpath <String> -xoffset <Int32> -yoffset <Int32> -speed <Int32> [<CommonParameters>] Flick-Element [-sessionid <String>] -marked <String> -xoffset <Int32> -yoffset <Int32> -speed <Int32> [<CommonParameters>] Flick-Element [-sessionid <String>] -elementid <String> -xoffset <Int32> -yoffset <Int32> -speed <Int32> [<CommonParameters>] DESCRIPTION Performs a flick on an element identified by one of the available locators. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. -elementid <String> (id locator) The identifier of the element. -xpath <String> (xpath locator) The xpath of the element -marked <String> (marked locator) The marked expression of the element -xoffset <Int32> the horizontal distance to flick -yoffset <Int32> the vertical distance to flick -speed <Int32> the speed of the flick movement <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Flick-Element -marked login -xoffset 0 -yoffset -300 REMARKS To see the examples, type: get-help Flick-Element -examples. For more information, type: get-help Flick-Element -detailed. For technical information, type: get-help Flick-Element -full. Get-AlertButtons Commands This page contains details on Get-AlertButtons commands. Get-AlertButtons NAME Get-AlertButtons SYNOPSIS Gets all buttons of the visible alert window. SYNTAX Get-AlertButtons [[-sessionid] <String>] [<CommonParameters>] DESCRIPTION Gets all buttons of the visible alert window. Returns: all available button names. 46 Chapter 3. Requirements

51 PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Get-AlertButtons REMARKS To see the examples, type: get-help Get-AlertButtons -examples. For more information, type: gethelp Get-AlertButtons -detailed. For technical information, type: get-help Get-AlertButtons -full. Get-AlertText Commands This page contains details on Get-AlertText commands. Get-AlertText NAME Get-AlertText SYNOPSIS Gets the text displayed on the alert window. SYNTAX Get-AlertText [[-sessionid] <String>] [<CommonParameters>] DESCRIPTION Gets the text displayed on the alert window. Returns: the displayed alert window text PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Get-AlertText REMARKS To see the examples, type: get-help Get-AlertText -examples. For more information, type: get-help Get-AlertText -detailed. For technical information, type: get-help Get-AlertText -full. Get-App Commands This page contains details on Get-App commands. Get-App NAME Get-App SYNOPSIS Gets all applications in the application repository. SYNTAX Get-App [<CommonParameters>] DESCRIPTION Gets all applications in the application repository. PARAMETERS 3.4. Quamotion PowerShell reference 47

52 <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Get-App REMARKS To see the examples, type: get-help Get-App -examples. For more information, type: get-help Get- App -detailed. For technical information, type: get-help Get-App -full. Get-BatteryInfo Commands This page contains details on Get-BatteryInfo commands. Get-BatteryInfo NAME Get-BatteryInfo SYNOPSIS Gets the battery info of a device. SYNTAX Get-BatteryInfo [-deviceid] <String> [<CommonParameters>] DESCRIPTION Gets the battery info of a device. Returns: the battery info of a device. PARAMETERS -deviceid <String> The device identifier. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Get-BatteryInfo -deviceid $iphone6 REMARKS To see the examples, type: get-help Get-BatteryInfo -examples. For more information, type: get-help Get-BatteryInfo -detailed. For technical information, type: get-help Get-BatteryInfo -full. Get-CurrentSessionId Commands This page contains details on Get-CurrentSessionId commands. Get-CurrentSessionId NAME Get-CurrentSessionId SYNOPSIS Gets the current session identifier. SYNTAX Get-CurrentSessionId [<CommonParameters>] DESCRIPTION Gets the current session identifier. Returns: the current session identifiers PARAMETERS <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( 48 Chapter 3. Requirements

53 EXAMPLE 1 PS C:>Get-CurrentSessionId REMARKS To see the examples, type: get-help Get-CurrentSessionId -examples. For more information, type: get-help Get-CurrentSessionId -detailed. For technical information, type: get-help Get-CurrentSessionId -full. Get-Device Commands This page contains details on Get-Device commands. Get-Device NAME Get-Device SYNOPSIS Gets all available devices. SYNTAX Get-Device [<CommonParameters>] DESCRIPTION Gets all available devices PARAMETERS <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Get-Device REMARKS To see the examples, type: get-help Get-Device -examples. For more information, type: get-help Get-Device -detailed. For technical information, type: get-help Get-Device -full. Get-DiskInfo Commands This page contains details on Get-DiskInfo commands. Get-DiskInfo NAME Get-DiskInfo SYNOPSIS Gets the disk info of a device. SYNTAX Get-DiskInfo [-deviceid] <String> [<CommonParameters>] DESCRIPTION Gets the disk info of a device. Returns: the disk info of a device. PARAMETERS -deviceid <String> The device identifier. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Get-DiskInfo -deviceid $iphone Quamotion PowerShell reference 49

54 REMARKS To see the examples, type: get-help Get-DiskInfo -examples. For more information, type: get-help Get-DiskInfo -detailed. For technical information, type: get-help Get-DiskInfo -full. Get-ElementProperties Commands This page contains details on Get-ElementProperties commands. Get-ElementProperties NAME Get-ElementProperties SYNOPSIS Gets all property names of an element. SYNTAX Get-ElementProperties [-sessionid <String>] [-elementid] <String> [<CommonParameters>] DESCRIPTION Gets all property names of an element. Returns: all property names of an element. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. -elementid <String> The identifier of the element to query. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Get-ElementProperties Find-Element login Get-ElementProperties REMARKS To see the examples, type: get-help Get-ElementProperties -examples. For more information, type: get-help Get-ElementProperties -detailed. For technical information, type: get-help Get-ElementProperties -full. Get-ElementProperty Commands This page contains details on Get-ElementProperty commands. Get-ElementProperty NAME Get-ElementProperty SYNOPSIS Gets the value of an element property. SYNTAX Get-ElementProperty [-sessionid <String>] [-elementid] <String> [-property] <String> [<CommonParameters>] DESCRIPTION Gets the value of an element property. Returns: the value of the property PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. -elementid <String> The identifier of the element to query. -property <String> The property name to query. 50 Chapter 3. Requirements

55 <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Get-ElementProperty Text Find-Element login Get-ElementProperty Text REMARKS To see the examples, type: get-help Get-ElementProperty -examples. For more information, type: get-help Get-ElementProperty -detailed. For technical information, type: get-help Get-ElementProperty - full. Get-ElementRectangle Commands This page contains details on Get-ElementRectangle commands. Get-ElementRectangle NAME Get-ElementRectangle SYNOPSIS Gets the bounds of an element. SYNTAX Get-ElementRectangle [-sessionid <String>] [-elementid] <String> [<CommonParameters>] DESCRIPTION Gets the bounds of an element. Returns: a rectangle reprenting the outer bounds of an element. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. -elementid <String> The identifier of the element to query. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Find-Element login Get-ElementRectangle REMARKS To see the examples, type: get-help Get-ElementRectangle -examples. For more information, type: get-help Get-ElementRectangle -detailed. For technical information, type: get-help Get-ElementRectangle -full. Get-ElementText Commands This page contains details on Get-ElementText commands. Get-ElementText NAME Get-ElementText SYNOPSIS Gets the text value of an element. SYNTAX Get-ElementText [-sessionid <String>] [-elementid] <String> [<CommonParameters>] DESCRIPTION Gets the text value of an element. Returns: the text value of an element Quamotion PowerShell reference 51

56 PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. -elementid <String> The identifier of the element to query. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Find-Element login Get-ElementText REMARKS To see the examples, type: get-help Get-ElementText -examples. For more information, type: gethelp Get-ElementText -detailed. For technical information, type: get-help Get-ElementText -full. Get-InstalledApp Commands This page contains details on Get-InstalledApp commands. Get-InstalledApp NAME Get-InstalledApp SYNOPSIS Gets all installed applications on the device. SYNTAX Get-InstalledApp [-deviceid] <String> [<CommonParameters>] DESCRIPTION Gets all installed applications on the device. PARAMETERS -deviceid <String> The identifier of the device. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Get-InstalledApp -deviceid $iphone6 REMARKS To see the examples, type: get-help Get-InstalledApp -examples. For more information, type: gethelp Get-InstalledApp -detailed. For technical information, type: get-help Get-InstalledApp -full. Get-MapBounds Commands This page contains details on Get-MapBounds commands. Get-MapBounds NAME Get-MapBounds SYNTAX Get-MapBounds [[-sessionid] <string>] PARAMETERS -sessionid <string> ALIASES None 52 Chapter 3. Requirements

57 REMARKS None Get-MapCenter Commands This page contains details on Get-MapCenter commands. Get-MapCenter NAME Get-MapCenter SYNTAX Get-MapCenter [[-sessionid] <string>] PARAMETERS -sessionid <string> ALIASES None REMARKS None Get-MapMarkers Commands This page contains details on Get-MapMarkers commands. Get-MapMarkers NAME Get-MapMarkers SYNTAX Get-MapMarkers [[-sessionid] <string>] PARAMETERS -sessionid <string> ALIASES None REMARKS None Get-MapZoom Commands This page contains details on Get-MapZoom commands. Get-MapZoom NAME Get-MapZoom SYNTAX Get-MapZoom [[-sessionid] <string>] PARAMETERS -sessionid <string> ALIASES None REMARKS None Get-Orientation Commands This page contains details on Get-Orientation commands Quamotion PowerShell reference 53

58 Get-Orientation NAME Get-Orientation SYNOPSIS Gets the orientiation of a device. SYNTAX Get-Orientation [[-sessionid] <String>] [<CommonParameters>] DESCRIPTION Gets the orientiation of the device used in a session. Returns: the orientation of the device. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Get-Orientation REMARKS To see the examples, type: get-help Get-Orientation -examples. For more information, type: get-help Get-Orientation -detailed. For technical information, type: get-help Get-Orientation -full. Get-Screenshot Commands This page contains details on Get-Screenshot commands. Get-Screenshot NAME Get-Screenshot SYNOPSIS Takes a screenshot of the device used in the given session. SYNTAX Get-Screenshot [[-sessionid] <String>] [[-filepath] <String>] [<CommonParameters>] DESCRIPTION Takes a screenshot of the device used in the given session. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. -filepath <String> The file path used to store the screenshot. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Get-Screenshot -filepath c:tempscreenhot.jpg REMARKS To see the examples, type: get-help Get-Screenshot -examples. For more information, type: get-help Get-Screenshot -detailed. For technical information, type: get-help Get-Screenshot -full. Get-Sessions Commands This page contains details on Get-Sessions commands. 54 Chapter 3. Requirements

59 Get-Sessions NAME Get-Sessions SYNOPSIS Gets all active session SYNTAX Get-Sessions [<CommonParameters>] DESCRIPTION Gets all active sessions Returns: all active sessions PARAMETERS <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Get-Sessions REMARKS To see the examples, type: get-help Get-Sessions -examples. For more information, type: get-help Get-Sessions -detailed. For technical information, type: get-help Get-Sessions -full. Get-Source Commands This page contains details on Get-Source commands. Get-Source NAME Get-Source SYNOPSIS Get the current page source. SYNTAX Get-Source [[-sessionid] <String>] [<CommonParameters>] DESCRIPTION Get the current page source. Returns: the current page source. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Get-Source REMARKS To see the examples, type: get-help Get-Source -examples. For more information, type: get-help Get-Source -detailed. For technical information, type: get-help Get-Source -full. Get-Url Commands This page contains details on Get-Url commands Quamotion PowerShell reference 55

60 Get-Url NAME Get-Url SYNOPSIS Retrieve the URL of the current page. SYNTAX Get-Url [[-sessionid] <String>] [<CommonParameters>] DESCRIPTION Retrieve the URL of the current page. Returns: the current url. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Get-Url REMARKS To see the examples, type: get-help Get-Url -examples. For more information, type: get-help Get-Url -detailed. For technical information, type: get-help Get-Url -full. Get-WindowHandle Commands This page contains details on Get-WindowHandle commands. Get-WindowHandle NAME Get-WindowHandle SYNOPSIS Retrieve the current window handle. SYNTAX Get-WindowHandle [[-sessionid] <String>] [<CommonParameters>] DESCRIPTION Retrieve the current window handle. Returns: The current window handle. NoSuchWindow - If the currently selected window has been closed. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Get-WindowHandle REMARKS To see the examples, type: get-help Get-WindowHandle -examples. For more information, type: get-help Get-WindowHandle -detailed. For technical information, type: get-help Get-WindowHandle -full. Get-WindowHandles Commands This page contains details on Get-WindowHandles commands. 56 Chapter 3. Requirements

61 Get-WindowHandles NAME Get-WindowHandles SYNOPSIS Retrieve the list of all window handles available to the session. SYNTAX Get-WindowHandles [[-sessionid] <String>] [<CommonParameters>] DESCRIPTION Retrieve the list of all window handles available to the session. Returns: A list of window handles. The order in which the window handles are returned is arbitrary. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Get-WindowHandles REMARKS To see the examples, type: get-help Get-WindowHandles -examples. For more information, type: get-help Get-WindowHandles -detailed. For technical information, type: get-help Get-WindowHandles - full. Go-Back Commands This page contains details on Go-Back commands. Go-Back NAME Go-Back SYNOPSIS Go back, if possible. SYNTAX Go-Back [[-sessionid] <String>] [<CommonParameters>] DESCRIPTION Go back, if possible. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Go-Back REMARKS To see the examples, type: get-help Go-Back -examples. For more information, type: get-help Go- Back -detailed. For technical information, type: get-help Go-Back -full. Install-App Commands This page contains details on Install-App commands Quamotion PowerShell reference 57

62 Install-App NAME Install-App SYNTAX Install-App [-deviceid] <string> [-appid] <string> [[-appversion] <string>] [<CommonParameters>] PARAMETERS -appid <string> -appversion <string> -deviceid <string> <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( ALIASES None REMARKS None Invoke-WebDriverRestMethod Commands This page contains details on Invoke-WebDriverRestMethod commands. Invoke-WebDriverRestMethod NAME Invoke-WebDriverRestMethod SYNTAX Invoke-WebDriverRestMethod PARAMETERS None ALIASES None REMARKS None Invoke-WebDriverWebRequest Commands This page contains details on Invoke-WebDriverWebRequest commands. Invoke-WebDriverWebRequest NAME Invoke-WebDriverWebRequest SYNTAX Invoke-WebDriverWebRequest PARAMETERS None ALIASES None REMARKS None Is-Displayed Commands This page contains details on Is-Displayed commands. 58 Chapter 3. Requirements

63 Is-Displayed NAME Is-Displayed SYNOPSIS Tests whether the element is visible. SYNTAX Is-Displayed [-sessionid <String>] [-elementid] <String> [<CommonParameters>] DESCRIPTION Tests whether the element is visible. $true or $false depending of the visibility of the element. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. -elementid <String> The identifier element. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Is-Displayed -elementid $loginbutton REMARKS To see the examples, type: get-help Is-Displayed -examples. For more information, type: get-help Is-Displayed -detailed. For technical information, type: get-help Is-Displayed -full. LongClick-Element Commands This page contains details on LongClick-Element commands. LongClick-Element NAME LongClick-Element SYNOPSIS Performs a long click on the first element whose locator matches the given value. SYNTAX LongClick-Element [-sessionid <String>] [-elementid] <String> [<CommonParameters>] DESCRIPTION Performs a long click on the first element whose locator matches the given value. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. -elementid <String> The identifier of the element to click. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Find-Element -marked Login LongClick-Element REMARKS To see the examples, type: get-help LongClick-Element -examples. For more information, type: gethelp LongClick-Element -detailed. For technical information, type: get-help LongClick-Element -full. Navigate-To Commands This page contains details on Navigate-To commands Quamotion PowerShell reference 59

64 Navigate-To NAME Navigate-To SYNOPSIS Navigate to a new URL. SYNTAX Navigate-To [-sessionid <String>] [-url] <String> [<CommonParameters>] DESCRIPTION Navigate to a new URL. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. -url <String> The URL to navigate to. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Navigate-To -url REMARKS To see the examples, type: get-help Navigate-To -examples. For more information, type: get-help Navigate-To -detailed. For technical information, type: get-help Navigate-To -full. New-DeveloperProfile Commands This page contains details on New-DeveloperProfile commands. New-DeveloperProfile NAME New-DeveloperProfile SYNTAX New-DeveloperProfile [[-accountname] <string>] [[-accountpassword] <string>] [[-password] <string>] [[-outfile] <string>] PARAMETERS -accountname <string> -accountpassword <string> -outfile <string> -password <string> ALIASES None REMARKS None New-Session Commands This page contains details on New-Session commands. New-Session NAME New-Session SYNOPSIS Create a new session. 60 Chapter 3. Requirements

65 SYNTAX New-Session [[-appversion] <String>] [[-clearappsettings] <Boolean>] [[-reinstallapplication] <Boolean>] [[-reuseexistingsession] <Boolean>] [<CommonParameters>] DESCRIPTION Create a new session. The session will install and launch the application on the device. PARAMETERS -appversion <String> The version of the application to be used. The version can be queried by perfoming the Get-App commmand or by clicking on the application in the frontend. -clearappsettings <Boolean> Indicates whether the application settions should be cleared before installing the application. -reinstallapplication <Boolean> Indicates whether the application should reinstalled. -reuseexistingsession <Boolean> Indicates whether an existing session should be reused. A session is only reused when the appid, appversion and deviceid are equal <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>New-Session -appid demo.quamotion.acquaint -appversion deviceid $iphone6 - reuseexistingsession $true REMARKS To see the examples, type: get-help New-Session -examples. For more information, type: get-help New-Session -detailed. For technical information, type: get-help New-Session -full. New-WebSession Commands This page contains details on New-WebSession commands. New-WebSession NAME New-WebSession SYNTAX New-WebSession [-deviceid] <string> [[-clearappsettings] <bool>] [<CommonParameters>] PARAMETERS -clearappsettings <bool> -deviceid <string> <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( ALIASES None REMARKS None Reboot-Device Commands This page contains details on Reboot-Device commands Quamotion PowerShell reference 61

66 Reboot-Device NAME Reboot-Device SYNOPSIS Reboots a device. SYNTAX Reboot-Device [-deviceid] <String> [<CommonParameters>] DESCRIPTION Reboots a device. PARAMETERS -deviceid <String> The device identifier <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Reboot-Device -deviceid $iphone6 REMARKS To see the examples, type: get-help Reboot-Device -examples. For more information, type: get-help Reboot-Device -detailed. For technical information, type: get-help Reboot-Device -full. Remove-Session Commands This page contains details on Remove-Session commands. Remove-Session NAME Remove-Session SYNOPSIS Removes a session SYNTAX Remove-Session [[-sessionid] <String>] [<CommonParameters>] DESCRIPTION Removes a session. The application is closed. PARAMETERS -sessionid <String> (Optional) The identifier of the session to be used. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Remove-Session REMARKS To see the examples, type: get-help Remove-Session -examples. For more information, type: gethelp Remove-Session -detailed. For technical information, type: get-help Remove-Session -full. Report-Status Commands This page contains details on Report-Status commands. 62 Chapter 3. Requirements

67 Report-Status NAME Report-Status SYNOPSIS Report a status message. SYNTAX Report-Status [[-sessionid] <String>] [-success] <Boolean> [-message] <String> [<CommonParameters>] DESCRIPTION Report a status message. The message will appear in the test-log. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. -success <Boolean> Indicates whether the status is success or failure -message <String> The message. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>report_status -success $false Something went wrong REMARKS To see the examples, type: get-help Report-Status -examples. For more information, type: get-help Report-Status -detailed. For technical information, type: get-help Report-Status -full. Rethrow-Exception Commands This page contains details on Rethrow-Exception commands. Rethrow-Exception NAME Rethrow-Exception SYNTAX Rethrow-Exception [[-ex] <Object>] PARAMETERS -ex <Object> ALIASES None REMARKS None ScrollDown-To Commands This page contains details on ScrollDown-To commands. ScrollDown-To NAME ScrollDown-To SYNOPSIS Scrolls down until an element with a matching xpath is visible SYNTAX ScrollDown-To [[-sessionid] <String>] [[-elementid] <String>] [[-xpath] <String>] [[-scrolltimeout] <Int32>] [<CommonParameters>] DESCRIPTION Scrolls down until an element with a matching xpath is visible 3.4. Quamotion PowerShell reference 63

68 PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. -elementid <String> The identifier of the scroll view. -xpath <String> (marked locator) The value for the marked locator -scrolltimeout <Int32> <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>ScrollDown-To -elementid $scrollview -xpath *[@marked= John ] REMARKS To see the examples, type: get-help ScrollDown-To -examples. For more information, type: get-help ScrollDown-To -detailed. For technical information, type: get-help ScrollDown-To -full. Scroll-To Commands This page contains details on Scroll-To commands. Scroll-To NAME Scroll-To SYNOPSIS Scrolls until an element with a matching locator value is visible SYNTAX Scroll-To [[-sessionid] <String>] [[-elementid] <String>] [[-marked] <String>] [[-xpath] <String>] [<CommonParameters>] DESCRIPTION Scrolls until an element with a matching locator value is visible. Note that the element should already be loaded. Please use the ScollDown-To or ScrollUp-To commands if the application generates the list dynamically. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. -elementid <String> The identifier of the scroll view. -marked <String> (marked locator) The value for the marked locator -xpath <String> (xpath locator) The value for the xpath locator <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Scroll-To -elementid $scrollview -marked John REMARKS To see the examples, type: get-help Scroll-To -examples. For more information, type: get-help Scroll-To -detailed. For technical information, type: get-help Scroll-To -full. ScrollUp-To Commands This page contains details on ScrollUp-To commands. 64 Chapter 3. Requirements

69 ScrollUp-To NAME ScrollUp-To SYNOPSIS Scrolls up until an element with a matching xpath is visible SYNTAX ScrollUp-To [[-sessionid] <String>] [[-elementid] <String>] [[-xpath] <String>] [[-scrolltimeout] <Int32>] [<CommonParameters>] DESCRIPTION Scrolls up until an element with a matching xpath is visible PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. -elementid <String> The identifier of the scroll view. -xpath <String> (marked locator) The value for the marked locator -scrolltimeout <Int32> <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>ScrollUp-To -elementid $scrollview -xpath *[@marked= John ] REMARKS To see the examples, type: get-help ScrollUp-To -examples. For more information, type: get-help ScrollUp-To -detailed. For technical information, type: get-help ScrollUp-To -full. Set-CurrentSessionId Commands This page contains details on Set-CurrentSessionId commands. Set-CurrentSessionId NAME Set-CurrentSessionId SYNOPSIS Sets the current session identifier. SYNTAX Set-CurrentSessionId [-sessionid] <String> [<CommonParameters>] DESCRIPTION Sets the current session identifier. PARAMETERS -sessionid <String> The identifier of the session to be used. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Set-CurrentSessionId -sessionid e68ef189-cd1b-4def-a1e2-1b4e1f1526df REMARKS To see the examples, type: get-help Set-CurrentSessionId -examples. For more information, type: get-help Set-CurrentSessionId -detailed. For technical information, type: get-help Set-CurrentSessionId - full Quamotion PowerShell reference 65

70 Set-MapCenter Commands This page contains details on Set-MapCenter commands. Set-MapCenter NAME Set-MapCenter SYNTAX Set-MapCenter [-latitude] <double> [-longitude] <double> [-sessionid <string>] [<CommonParameters>] PARAMETERS -latitude <double> -longitude <double> -sessionid <string> <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( ALIASES None REMARKS None Set-MapZoom Commands This page contains details on Set-MapZoom commands. Set-MapZoom NAME Set-MapZoom SYNTAX Set-MapZoom [-level] <int> [-sessionid <string>] [<CommonParameters>] PARAMETERS -level <int> -sessionid <string> <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( ALIASES None REMARKS None Set-Timeout Commands This page contains details on Set-Timeout commands. Set-Timeout NAME Set-Timeout SYNOPSIS Set the amount of time, in milliseconds, are permitted to run before they are aborted and a timeout error is returned to the client. SYNTAX Set-Timeout [-sessionid <String>] [-time] <String> [<CommonParameters>] 66 Chapter 3. Requirements

71 DESCRIPTION Set the amount of time, in milliseconds, are permitted to run before they are aborted and a timeout error is returned to the client. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. -time <String> The amount of time to wait, in milliseconds. This value has a lower bound of 0. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Set-Timeout -time 3000 REMARKS To see the examples, type: get-help Set-Timeout -examples. For more information, type: get-help Set-Timeout -detailed. For technical information, type: get-help Set-Timeout -full. Set-Value Commands This page contains details on Set-Value commands. Set-Value NAME Set-Value SYNTAX Set-Value [[-sessionid] <string>] [[-elementid] <string>] [[-value] <string>] PARAMETERS -elementid <string> -sessionid <string> -value <string> ALIASES None REMARKS None Set-Window Commands This page contains details on Set-Window commands. Set-Window NAME Set-Window SYNOPSIS Change focus to another window. SYNTAX Set-Window [-sessionid <String>] [-windowname] <String> [<CommonParameters>] DESCRIPTION Change focus to another window. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. -windowname <String> The window to change focus to Quamotion PowerShell reference 67

72 <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Set-Window Native REMARKS To see the examples, type: get-help Set-Window -examples. For more information, type: get-help Set-Window -detailed. For technical information, type: get-help Set-Window -full. Submit-Element Commands This page contains details on Submit-Element commands. Submit-Element NAME Submit-Element SYNTAX Submit-Element -xpath <string> [-sessionid <string>] [<CommonParameters>] Submit-Element [-sessionid <string>] [<CommonParameters>] Submit-Element -elementid <string> [-sessionid <string>] [<CommonParameters>] PARAMETERS -elementid <string> -sessionid <string> -xpath <string> <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( ALIASES None REMARKS None Test-Element Commands This page contains details on Test-Element commands. Test-Element NAME Test-Element SYNOPSIS Tests whether an element exist matching the given xpath SYNTAX Test-Element [-sessionid <String>] [-xpath] <String> [-ignorevisibility <Boolean>] [<CommonParameters>] DESCRIPTION Tests whether an element exist matching the given xpath Returns: $true or $false depending on the existens of the element. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. -xpath <String> The xpath for which to test the element. 68 Chapter 3. Requirements

73 -ignorevisibility <Boolean> (Optional) indicates whether non visible elements should be taken into account. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Test-Element -xpath *[@marked= login ] REMARKS To see the examples, type: get-help Test-Element -examples. For more information, type: get-help Test-Element -detailed. For technical information, type: get-help Test-Element -full. Uninstall-App Commands This page contains details on Uninstall-App commands. Uninstall-App NAME Uninstall-App SYNOPSIS Uninstalls an application from a device. SYNTAX Uninstall-App [-deviceid] <String> [-appid] <String> [<CommonParameters>] DESCRIPTION Uninstalls an application from a device. PARAMETERS -deviceid <String> The identifier of the device. -appid <String> The identifier of the application. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Uninstall-App -deviceid $iphone6 -appid demo.quamotion.acquaint REMARKS To see the examples, type: get-help Uninstall-App -examples. For more information, type: get-help Uninstall-App -detailed. For technical information, type: get-help Uninstall-App -full. Wait-ForElement Commands This page contains details on Wait-ForElement commands. Wait-ForElement NAME Wait-ForElement SYNOPSIS Waits for an element whose locater matches the given value. SYNTAX Wait-ForElement [-sessionid <String>] -marked <String> [<CommonParameters>] Wait-ForElement [-sessionid <String>] -xpath <String> [<CommonParameters>] Wait-ForElement [-sessionid <String>] -class <String> [<CommonParameters>] 3.4. Quamotion PowerShell reference 69

74 DESCRIPTION Waits for an element whose locator matches the given value. PARAMETERS -sessionid <String> (Optional) The identifier of the session to route the command to. -xpath <String> The xpath used to locate elements. -class <String> The class attribute value used to locate elements. -marked <String> The marked attribute value used to locate elements. <CommonParameters> This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, Error- Variable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_commonparameters ( EXAMPLE 1 PS C:>Wait-ForElement -xpath *[@marked= login ] Wait-ForElement -marked login Wait-ForElement -class UIView REMARKS To see the examples, type: get-help Wait-ForElement -examples. For more information, type: gethelp Wait-ForElement -detailed. For technical information, type: get-help Wait-ForElement -full. Quamotion Hands-on Labs Our Hands-on Labs provide an easy, no-cost way to evaluate the features and functionality of Quamotion. By following any of our Hands-on Labs, you ll implement a real-life scenario in mobile test automation using Quamotion. Practice makes perfect, so get ready to complete our Hands-on Labs! Mobile Test Automation with Quamotion Contents Mobile Test Automation with Quamotion About This Lab * Lab Objectives * Technologies * Audience * Feedback Getting Started * Connect to the Lab Environment * Open the Lab Environment Excercise 1 - Explore the Quamotion User interface * Scenario * Task 1 - Applications in Quamotion * Task 2 - Devices in Quamotion 70 Chapter 3. Requirements

75 * Task 3 - Spying the user interface of an application * Task 4 - Using the Mobile App Quality Dashboard Excercise 2 - Automate the ios Acquaint app * Scenario * Task 1 - Explore the Acquaint application * Task 2 - Create a script which launches the application * Task 3 - Automate the Acquaint setup * Task 4 - Open acquaintance details * Task 5 - Edit acquaintance details * Review Excercise 2 - Automate the Android Acquaint app * Scenario * Task 1 - Install the Acquaint application on your device * Task 2 - Explore the Android Acquaint application * Task 3 - Create a script which launches the application * Task 4 - Automate the Acquaint setup * Task 5 - Open acquaintance details * Task 6 - Edit acquaintance details * Review Summary About This Lab Estimated time to complete this lab: 60 minutes You can review the latest version of this lab on-line at Lab Objectives This lab provides an end-to-end tour of the Quamotion Webdriver. You will start with a brief exploration of the Quamotion UI, and then move on to an introduction on mobile test automation. You will learn how to install a mobile app on a mobile device. Next, you will learn how to inspect the user interface of a mobile app and to automate individual user interactions with that mobile app. You will then use that knowledge to automate a full end-to-end scenario. Finally, you ll learn how use the mobile quality dashboard to assess the quality of your mobile app on different devices and platforms. After completing this lab, you will be better able to: Use the Quamotion user interface Identify the elements that make up the user interface of a mobile app Automate user interactions with the mobile app 3.5. Quamotion Hands-on Labs 71

76 Create mobile test automation scripts Run mobile test automation scripts Assess the quality of your mobile app Technologies In this hands on lab, you ll use the following technologies: Quamotion for Windows PowerShell Audience This hands on lab targets the following audience: Test automation engineers Feedback We welcome your feedback on this lab! If you ve found an issue, have questions or just got stuck while executing this lab, you can leave your feedback: With the Quamotion team at the Quamotion booth In the Disqus section at the on-line version of this lab On the GitHub site at Getting Started Connect to the Lab Environment Ensure you are logged on to the Quamotion machine as a normal user. Open the Lab Environment 1. Make sure you have the latest version of the demo application available. In this lab, we ll use the Acquaint app. The table below lists the download links for the Acquaint app. Download the Acquaint app and save the files on the lab machine. Android ios Make sure at least an ios device (such as an iphone) and an Android device (such as a Google Nexus device) are connected to the lab machine. Verify the devices are connected to the lab machine using an USB cable. 3. If the Quamotion software is not already running, start it by launching Quamotion.WebDriver.exe. Leave the main executable running in the background. 4. To begin the lab, on the lab machine, start a browser, such as Google Chrome, and navigate to the Quamotion user interface at 72 Chapter 3. Requirements

77 Excercise 1 - Explore the Quamotion User interface Estimated time to complete this excercise: 15 minutes Scenario In this introduction to the Quamotion User Interface, you will open the Quamotion user Interface and explore the different components of the user interface. You will see that Quamotion provides you a single entry point to manage your apps, your devices and the results of your test campaigns. Task 1 - Applications in Quamotion In this task, you will access the Apps page, add the Acquaint application and list all applications which are available for testing. 1. Ensure that you are connected to the Quamotion machine as a normal user. 2. Start a browser and navigate to 3. In the top navigation, click Apps. 4. You will now see a list of all applications which are available for testing. By default, this list is empty. 5. At the bottom of the page, click the New button. The New App dialog appears 6. Click the Choose File button, and select the acquaint-ios-151.ipa file which you ve downloaded earlier. 7. Click Add to add the application. 8. The New App dialog closes, and the Apps screen becomes visible. The Acquaint app is now listed in the list of available applications. 9. Click on the Acquaint app. A dialog box opens with additional information about the app. You can also download the app, or delete the app, from within this dialog box Quamotion Hands-on Labs 73

78 Task 2 - Devices in Quamotion In this task, you will access the Devices page, connect and disconnect a device to your PC, and notice how the Devices page automatically refreshes. 1. In the top navigation, click Devices. 2. You will see a list of all ios and Android devices which are available for testing. If no ios or Android devices are devices to your PC using an USB cable, this list is empty. 3. Connect an ios device to your PC. The Devices page will automatically update, and list the new ios device which you have connected. 4. Click on the ios device you have connected. A dialog appears, which shows additional information about your device. 5. Unplug the USB cable of your ios device from your PC. The device is removed from the Devices screen. Task 3 - Spying the user interface of an application In this task, you ll use the Spy page to spy on the user interface of an application. When spying you ll be able to inspect the individual elements of the application s UI. You can later use these elements in your automation scripts. You ll see how to write automation scripts in a next excercise. 1. In the top navigation, click Spy. The Spy page opens. 74 Chapter 3. Requirements

79 2. The Spy page allows you to launch an app on a device, and inspect the user interface of that app. To launch the app, you ll first need to specify which app you want to run, and on which device you want to run it. In the Platform dropdown, select ios, in the App dropdown, select Acquaint N, and in the Device dropdown, select your ios device. 3. After a couple of seconds, the screen of your device will be mirrored in your browser. 4. Click Start to install and launch your application on the device. Wait for your application to launch. 5. You can now inspect the user interface of your app. Click any element in the user interface. The element will be highlighted in a red rectangle Quamotion Hands-on Labs 75

80 6. Review the contents in the lower right of your browser window. You ll see a tree view, which represents all user interface elements of your application which are related to the element you ve just selected. The tree view contains the XPath expression which you can use to identify the element and, where available, the ID, text or accessibility label of the element. 7. Review the contents in the upper right of your browser window. You ll see a table, which contains additional information about the element you ve just selected. You ll see the XPath you can use to identify the element, as well as some additional information, such as the class name, ID and rectangle. 8. Click on the Play icon. Additional properties of the element which you ve selected are now displayed. You can use the text box to filter the properties which are being displayd. Type access in the text box. Now only properties related to accessibility are being displayed. 76 Chapter 3. Requirements

81 Task 4 - Using the Mobile App Quality Dashboard In this task, you ll use the Dashboard app to view the results of the test scripts you ve executed. 1. In the top navigation, click Dashboard. The Dashboard page opens. 2. The two top pie charts in the All Results section display the number of tests you ve executed, and the number of devices on which you ve executed those tests Quamotion Hands-on Labs 77

82 3. The Key Metrics section displays key metrics about your test campaign - such as the total device time, the number of devices and operating systems, and the size of the application under test. 4. The Failure Breakdown section displays the test results by operating system, form factor and manufacturer. 5. You can click any link the failure breakdown section to view more information about those failures. Click on any link in the operatig system section. 6. The Test Result Details page will appear. This page contains all tests you ve executed which match the criteria you ve specified. 7. Click on any test in the test results list. 8. The test report appears. The test report contains a detailed view of all steps that have been executed in the test report, including screenshots. 78 Chapter 3. Requirements

83 Excercise 2 - Automate the ios Acquaint app Estimated time to complete this excercise: 30 minutes Scenario In this scenario, you ll automate the ios version of the Acquaint application. The Acquaint app is a simple list of contacts, each of which can be viewed in a detail screen and modified in an edit screen. It runs on ios 9 and above. You will learn how to: Create a mobile test automation script Automatically launch an application on a mobile device Automate user interactions, such as scrolling, tapping and typing text Analyze the test results Task 1 - Explore the Acquaint application You ll first explore the Acquaint application. You will now manually execute the scenario you will later automate. 1. On your ios device, if it is not already active, launch the Acquaint app. The Acquaint app was installed previously on your device when you launched the spy. 2. If you are requested to connect to a data source, enter the value `UseLocalDataSource as the data source and continue to the next page. 3. In the list of acquaintances, scroll down until you find Green, Monica. Tap Green, Monica. 4. The details page for Monica Green will now open, including a mapp which visualizes her address. Tap the pencil icon in the upper right corner of the device to edit her details. 5. Scroll down until you find the ZIP field in the contact details. 6. Tap the zip code. The on screen keyboard of your device will now appear. Enter a new zip code, for example, , which is the zip code for Stockholm. 7. Tap the save icon in the upper right corner of the app to save your changes. Make sure the zip code is displayed correctly. 8. Tap List to go back to the main screen. Task 2 - Create a script which launches the application In this task, you ll create your first mobile test automation script. There are plug-ins for Quamotion that allow you to write tests in Java, C# or PowerShell. In this task, you ll use PowerShell. Because PowerShell is a scripted language, and not a compiled language, it is easier to create and edit scripts as you go. However, all the scripts you re about the write in PowerShell could easily be written in Java or C#. If you re using the Quamotion machine, PowerShell is already installed. PowerShell is also available on Windows by default. If you re using Linux or macos, download PowerShell from Because Quamotion is based on the WebDriver protocol, it also implements most of the concepts of WebDriver. One fundamental concept in WebDriver is the notion of a session. You can think of a session as a test run. In the context of Quamotion, a session is an application running on a device Quamotion Hands-on Labs 79

84 When you start a new test script, the first step is usually to create a session. You can do so using the New-Session command. When starting a session, you specify the application you want to launch (by its unique ID and version number) and the device on which you want to launch the application (by its serial number). You can use the portal to get the unique ID and version number of the mobile app and the serial number of the device, or you can use the Get-App and Get-Device commands in PowerShell. 1. As a first step, open PowerShell. Click Start, type PowerShell and hit ENTER. The PowerShell console will now open. 2. Next, you ll need to import the Quamotion module into your PowerShell session. Assuming you ve installed the Quamotion software to C:\Quamotion, type the following command and hit ENTER: PS> Import-Module C:\Quamotion\wdclient.psm1 3. To get the application ID and version number of the Acquaint app, run the Get-App command: PS> Get-App AppId : demo.quamotion.acquaint DisplayName : Acquaint N (1.51) Version : 1.51 VersionDisplayName : 1.51 SupportedConfigurations [..]} TestServerVersion : 4. Note that the application ID is demo.quamotion.acquaint and the version number is To get the unique ID of your device, run the Get-Device command: PS> Get-Device configuration [..]} devicerotation : None manufacturer : Apple model : iphone6,2 name : iphone providerid : 61fee b09-9d8a d30ec9 resolution y=0; width=640; height=1136} serialnumber : bf136e8e8962fe978e74f4c92af330c6ba state : Started type : Physical uniqueid : bf136e8e8962fe978e74f4c92af330c6ba viewport y=0; width=640; height=1136} devicemodel 6. A lot of information about your device is provided to you. Write down the unique ID, bf136e8e8962fe978e74f4c92af330c6ba in this case. Note: Because the unique ID uniquely identifies the device, you may obtain a different unique ID with your ios device. 80 Chapter 3. Requirements

85 7. To start a new session on the device, run New-Session command. Specify the unique ID of your device using the -deviceid parameter and the ID and version of your app using the appid and appversion parameters, respectively. Because the Acquaint app stores the secret key you ve used, you may want to reinstall the application on the device every time you create a new session. This way, you re sure your application starts in a clean state, every time you run a test. Finally, because only one app can run on a device at the same time, you may want to remove any previous session. You can do so using the Get-Sessions Remove-Session command PS> Get-Sessions Remove-Session PS> New-Session -deviceid bf136e8e8962fe978e74f4c92af330c6ba -appid demo.quamotion.acquaint -appversion reinstallapp $true The session b59649cb b-923c-8384b4fcd6f3 is Deploying: [..] The session b59649cb b-923c-8384b4fcd6f3 is Deploying: [..] The session b59649cb b-923c-8384b4fcd6f3 is Deploying: [..] Task 3 - Automate the Acquaint setup The first time you launch Acquaint, it will ask you to configure a unique passphrase. In this task, you ll write a script which enters the unique passphrase and then taps Continue. To automate gestures on controls, such as tapping, you can use PowerShell functions like Click-Element. When automating a gesture, you need to instruct Quamotion on which user interface element you want your script to perform the gesture. There are various ways to identify an control. You can identify a control by the text it displays, its accessibility label or its unique ID (if one is assigned to the control by the application s developers). Alternatively, you can also specify the control s class name or provide an XPath expression which uniquely identifies the control. To retrieve the class name or XPath expression, you can use the Spy window you ve explored in the previous excercise. To type text, you can use the Enter-Text PowerShell function. In this case, we want to enter text in the text box which displays the text Enter a unique phrase. You can pass the -marked parameter to the Click-Element function to instruct the Click-Element function to click on that control Quamotion Hands-on Labs 81

86 1. To simulate a tap on the text box which displays the text Enter a unique phrase, enter the following command in PowerShell: PS> Click-Element -marked "Enter a unique phrase" 2. The on-screen keyboard will now appear Type Enter-Text "UseLocalDataSource" to simulate the user typing the UseLocalDataSource text PS> Enter-Text "UseLocalDataSource" 3. Finally, you can simulate a tap on the Continue button by using the Click-Element method. PS> Click-Element -marked "Continue" The application will now launch the Acquaintances screen. Task 4 - Open acquaintance details In this task, you ll open the details page for an acquaintance. You ll use an acquaince with a last name which starts with T requiring you write a script which scrolls down to that acquaintance in the contact list. To scroll down to an element, use the Scroll-To method. However, you need to specify which scroll view you want to scroll in. To obtain a reference to the scroll view, you can use the Get-Element function. Because scroll views on ios implement the UITableView class, you can search by class. 1. To scroll down to the Thornton, Vanessa contact, run the following code: PS> $scrollview = Find-ElementFlex -class "UITableView" PS> Scroll-To -elementid $scrollview -marked "Thornton, Vanessa" The application will now scroll down the main scroll view, until the Thornton, Vanessa acquaintance is visible. 82 Chapter 3. Requirements

87 Quamotion WebDriver Documentation, Release To open the details for Vanessa, use the Click-Element function: PS> Click-Element -marked "Thornton, Vanessa" Vanessa s contact details will appear. Task 5 - Edit acquaintance details Once you ve opened the contact card for Vanessa, you ll want to automate a tap on the edit icon, represented by the pencil, in the upper right of the screen. Because this icon does not contain any visual text, you cannot use the Click-Element function with the -marked parameter like we ve done previously. Instead, you ll need to open the Spy. 1. In your browser, navigate to the Spy page. 2. Select the ios platform, the Acquaint app and your device. Because you ve already opened a session for the Acquaint app on your device, you ll also need to check the Reuse an existing session if available check box. 3. Click Start to start the spy. 4. In the mirror of your devices screen in your browser, click the pencil icon. 5. Note how the details section also displays the unique ID of the edit icon. 6. Now you know the unique ID of the edit icon is edit, you can use the Click-Element method to automate a click: PS> Click-Element -marked "edit" The edit screen will apear Quamotion Hands-on Labs 83

88 7. To update the zip code, you ll first need to scroll down to the ZIP entry. You can use the same technique you ve learned in the previous step: PS> $scrollview = Find-ElementFlex -class "UITableView" PS> Scroll-To -elementid $scrollview -marked "ZIP" 8. To edit the zip code, similate a tap on the current zip code (94070): PS> Click-Element -marked "94070" 9. Clear the text, enter a new zip value and dismiss the keyboard to stop editing: PS> Clear-Text PS> Enter-Text PS> Dismiss-Keyboard 10. Finally, navigate back to the main list of acquaintances by tapping Details and List: PS> Click-Element -marked "Details" PS> Click-Element -marked "List" Review In this task, you ve used PowerShell and the Spy to automate a scenario in the Acquaint app. You ve written the following PowerShell script which sets up Acquaint and edits the contact details of an acquaintance: Import-Module C:\Quamotion\wdclient.psm1 # Kill any sessions which are still running Get-Sessions Remove-Session # Launch the application on the device New-Session -deviceid bf136e8e8962fe978e74f4c92af330c6ba -appid demo.quamotion.acquaint -appversion reinstallapp $true # Set up Acquaint: provide a passphrase and tap Continue Click-Element -marked "Enter a unique phrase" Enter-Text "UseLocalDataSource" Click-Element -marked "Continue" # Open the details for Vanessa Thornton $scrollview = Find-ElementFlex -class "UITableView" Scroll-To -elementid $scrollview -marked "Thornton, Vanessa" Click-Element -marked "Thornton, Vanessa" # Click the edit button Click-Element -marked "edit" # Scroll to the ZIP field $scrollview = Find-ElementFlex -class "UITableView" Scroll-To -elementid $scrollview -marked "ZIP" # Change the Zip code 84 Chapter 3. Requirements

89 Click-Element -marked "94070" Clear-Text Enter-Text "100 44" Dismiss-Keyboard # Go back to the main acquaintances list Click-Element -marked "Details" Click-Element -marked "List" Excercise 2 - Automate the Android Acquaint app Estimated time to complete this excercise: 30 minutes Scenario In this scenario, you ll automate the Android version of the Acquaint application. The Acquaint app is a simple list of contacts, each of which can be viewed in a detail screen and modified in an edit screen. It runs on Android 4 and above. You will learn how to: Create a mobile test automation script Automatically launch an application on a mobile device Automate user interactions, such as scrolling, tapping and typing text Analyze the test results Task 1 - Install the Acquaint application on your device Connect your Android device to your PC. In the previous excercise, the Acquaint application was installed on your device the first time you launched the Spy. In this excercise, you ll upload and install the Acquaint app on the Android device using PowerShell. To upload an application to Quamotion, you can use the Add-App function. It takes one parameter, the full path to the application. To install an application, you can use the Install-App function. This function takes three parameters, the ID of the device on which you want to install the app, the app ID and app version. 1. Open PowerShell. Click Start, type PowerShell and hit ENTER. THe PowerShell console will now open. 2. Import the Quamotion module in your PowerShell session. Assuming you ve installed Quamotion to C:\Quamotion, type the following command and hit ENTER: PS> Import-Module C:\Quamotion\wdclient.psm1 3. To add the Acquaint app, type the following command and hit ENTER. If you have downloaded the Acquaint application to a different location than C:\Quamotion, make sure to specify the correct path. PS> Add-App C:\Quamotion\demo.quamotion.acquaint.apk AppId : demo.quamotion.acquaint DisplayName : Acquaint N (1.51) Version : 151 VersionDisplayName : Quamotion Hands-on Labs 85

90 SupportedConfigurations TestServerVersion : The Add-App command provides you with information about the app you ve just uploaded. For example, we now know that the app ID is demo.quamotion.acquaint, and the Version is To install the Acquaint app on your device, you ll first need to get the unique ID of your Android device. You can use the Get-Device command to do that: PS> Get-Device configuration devicerotation : None manufacturer : asus model : K013 name : K013 providerid : ef64b429-9c24-4d4d-a926-5ed446028c05 resolution y=0; width=800; height=1280} serialnumber : EAOKCY state : Started type : Physical uniqueid : EAOKCY viewport y=0; width=800; height=1280} devicemodel 5. You are now ready to install the Acquaint app on your device. Use the Install-App command and specify the App ID, App Version and Device Unique ID values you ve obtained in the previous steps: PS> Install-App -deviceid EAOKCY appid demo.quamotion.acquaint -appversion 151 StatusCode : 200 [..] 6. The Acquaint N app is now installed on your Android device. You can manually launch the Android N application by clicking its application icon. Task 2 - Explore the Android Acquaint application In the previous task, you ve launched the Acquaint application on your Android device. In this task, you ll manually explore the Acquaint application. Once you ve completed this task, you are ready to automate the Acquaint application in the next task. 1. If you are requested to connect to a data source, enter the value `UseLocalDataSource as the data source and continue to the next page. 2. In the list of acquaintances, scroll down until you find Green, Monica. Tap Green, Monica. 3. The details page for Monica Green will now open, including a mapp which visualizes her address. Tap the pencil icon in the upper right corner of the device to edit her details. 4. Scroll down until you find the ZIP field in the contact details. 5. Tap the zip code. The on screen keyboard of your device will now appear. Enter a new zip code, for example, , which is the zip code for Stockholm. 86 Chapter 3. Requirements

91 6. Tap the save icon in the upper right corner of the app to save your changes. Make sure the zip code is displayed correctly. 7. Tap List to go back to the main screen. Task 3 - Create a script which launches the application In this task, you ll use PowerShell to create a script which launches the Acquaint application, just like you ve done in the previous excercise. You ll learn how to implement the same scenario in Java and C# in the following excercises. 1. To start a new session on the device, run the New-Session command. Specify the unique ID of your device, the ID of your app and the version of your App using the -deviceid, -appid and -appversion parameters. You ve obtained these values in the first task of this excercise. PS> Get-Sessions Remove-Session PS> New-Session -deviceid EAOKCY appid demo.quamotion.acquaint -appversion 151 -reinstallapp $true The session 030cbe05-c2e5-49be-aaa0-a3a3f12b0436 is Deploying: [..] Task 4 - Automate the Acquaint setup The first time you launch Acquaint, you ll be asked to provide a unique passphrase. In this task, you ll write a a script which types in the unique passphrase and then taps Continue. Just like ios, you can use the Click-Element and Enter-Text functions to automate these actions. 1. To simulate a tap on the text box which displays the Enter a unique phrase, execute the following PowerShell command: PS> Click-Element -marked "Enter a unique phrase" 2. The on-screen keyboard will now appear, indicating your application is ready to receive keyboard input. Enter the following command to simulate the user typing the UseLocalDataSource text. PS> Enter-Text "UseLocalDataSource" 3.5. Quamotion Hands-on Labs 87

92 3. Finally, you can simulate the user tapping the Continue button: PS> Click-Element -marked "Continue" The Acquaintances screen will now load: Task 5 - Open acquaintance details In this task, you ll open the details page for an acquaintance. You ll use an acquaintance with a last name which starts with T requiring you to write a script which scrolls down to that acquaintance in the contact list. Like on ios, you can use the Scroll-To method to scroll down to an element. You need to specify a reference to the scroll view you want to scroll in. To obtain a reference to the scroll view, you can use the Get-Element function. On 88 Chapter 3. Requirements

93 Android, scroll views inherit from the SwipeRefreshLayout class. 1. To scroll down to the Thornton, Vanessa contact, run the following code: PS> $scrollview = Find-ElementFlex -class "SwipeRefreshLayout" PS> ScrollDown-To -elementid $scrollview -xpath "//*[@marked='thornton, Vanessa']" 2. To open the details for Vanessa, use the Click-Element function: PS> Click-Element -marked "Thornton, Vanessa" Vanessa s contact details will appear Task 6 - Edit acquaintance details Once you ve opened the contact card for Vanessa, you ll want to automate a tap on the edit icon, represented by the pencil in the upper right corner of the screen. Because this icon does not contain any visual text, you cannot use the Click-Element function with the -marked parameter like we ve done previously. Instead, you ll need to open the Spy. 1. In your browser, navigate to the Spy page. 2. Select the Android platform, the Acquaint N app and your device. Because you ve already opened a session for the Acquaint app on your device, you ll also need to check the Reuse an existing session if available check box. 3. Click Start to start the spy. 4. In the mirror of your device screen in your browser, click the pencil icon. 5. Note how the details section also displays the unique ID of the edit icon. 6. Now you know the unique ID of edit icon is acquaintanceeditbutton, you can use the Click-Element method to automate a click: 3.5. Quamotion Hands-on Labs 89

94 PS> Click-Element -marked "acquaintanceeditbutton" The edit screen will appear. 7. To update the zip code, you ll first need to scroll down to the ZIP entry. You can use the same technique you ve learned in a previous step; but not that this time, you ll have to use the LinearLayout[@marked='acquaintanceEditContentLayout'] XPath expression to find the scroll container: PS> $scrollview = Find-Element -xpath "LinearLayout[@marked='acquaintanceEditContentLayout']" PS> Scroll-To -elementid $scrollview -marked "ZIP" 8. To edit the zip code, simulate a tap on the current zip code (94070): PS> Click-Element -marked "94070" 9. To clear the text, enter a new zip value and dismiss the keyboard to stop editing: PS> Clear-Text PS> Enter-Text "100 44" PS> Dismiss-Keyboard 10. Finally, navigate back to the main list of acquaintances by tapping the back arrow. Use the Spy to obtain the ID of the back button, which is ImageButton[1]: PS> Click-Element -xpath "ImageButton[1]" PS> Click-Element -xpath "ImageButton[1]" Review In this task, you ve used PowerShell and the Spy to automate a scenario in the Acquaint app. You ve written the following PowerShell script which sets up Acquaint and edits the contact details of an acquaintance: Import-Module C:\Quamotion\wdclient.psm1 # Kill any sessions which are still running Get-Sessions Remove-Session # Launch the application on the device New-Session -deviceid EAOKCY appid demo.quamotion.acquaint -appversion 151 -reinstallapp $true # Set up Acquaint: provide a passphrase and tap Continue Click-Element -marked "Enter a unique phrase" Enter-Text "UseLocalDataSource" Click-Element -marked "Continue" # Open the details for Vanessa Thornton $scrollview = Find-ElementFlex -class "SwipeRefreshLayout" ScrollDown-To -elementid $scrollview -xpath "//*[@marked='thornton, Vanessa']" Click-Element -marked "Thornton, Vanessa" 90 Chapter 3. Requirements

95 # Click the edit button Click-Element -marked "acquaintanceeditbutton" # Scroll to the ZIP field $scrollview = Find-Element -xpath LinearLayout[@marked='acquaintanceEditContentLayout'] Scroll-To -elementid $scrollview -marked "ZIP" # Change the Zip code Click-Element -marked "94070" Clear-Text Enter-Text "100 44" Dismiss-Keyboard # Go back to the main acquaintances list Click-Element -xpath "ImageButton[1]" Click-Element -xpath "ImageButton[1]" Summary In this hands-on lab, you were introduced to Quamotion, with emphasis on how to write an automated mobile test. Specifically, you learned to: Manage applications and devices Inspect the user interface of a mobile application Use the Mobile App Quality dashboard Automate an ios application using PowerShell Automate an Android application using PowerShell How To... Ready to get started with Quamotion but wondering how to complete specific tasks? We ve prepared how-to documents which will help you be up and running instantly! Run Mobile UI Tests in TeamCity In this How-To, we ll configure TeamCity so that it automatically runs mobile UI tests as part of a TeamCity build. We re assuming you re writing your test cases in PowerShell using Pester, and you re using Git to store your test scripts, but the same setup will also work for other combinations. Overview You ll create a new TeamCity project which will execute mobile UI tests and reports the results to TeamCity. You ll configure a build phase which executs the mobile tests and save the results to an.xml file. Then, you ll configure the build features so that TeamCity is able to read the test results in that file. You ll need the following components to get started with Quamotion and TeamCity: 3.6. How To... 91

96 1. A server on which Quamotion is running. If you re using the cloud scale out, we host this server for you. If you re hosting Quamotion on premises, you ll need to install Quamotion on a server in your network. If you only have one TeamCity agent, you can install Quamotion on your TeamCity agent; otherwise, you ll need a dedicated machine. 2. A set of test cases which you want to run as part of your TeamCity build. For example, you can write these tests as JUnit, Cucumber or Pester (PowerShell) tests. In this how-to guide, we re using Pester tests. 3. A repository in which you want to store your tests. You can choose to store your tests in the same repository as your source code, or you can store it in a seperate repository. In this walkthrough, we ll use a dedicated repository, hosted on GitHub. 4. A TeamCity installation with at least one agent. Creating the TeamCity project Follow these steps to create a new TeamCity project: 1. Open TeamCity and log in using an account with administrative credentials. 2. Click Administration to open the TeamCity administration. 3. Click the Create project dropdown button to create a new project, and select Pointing to repository url. 4. Provide the information about the GitHub repository in which you re storing your tests, and click Proceed. 5. Confirm the project name and build configuration name and click Proceed. Configuring the build steps Follow these steps to specify the build steps for your TeamCity project. You ll configure TeamCity build so that the build executes the mobile UI tests, and saves the results in an.xml file. 1. Although TeamCity automatically detects some build steps, these build steps do not fully support runing mobile UI tests. Click Build Steps in the left-hand menu to go to the Build Steps window. 92 Chapter 3. Requirements

97 2. Click Add build step to create a new build step 3. Select PowerShell as the runner type, and specify Source Code as the Script option. 4. Use this script as the PowerShell script content. This script will run the Pester tests and save the test results in a.xml file, which TeamCity can then use to analyze the test results. Import-Module Pester Invoke-Pester -OutputFile results.xml -OutputFormat NUnitXml 5. Click Save to save the build step. Configuring the Build Features Follow these steps to specify the Build Features for your TeamCity project. You ll configure the features so that TeamCity is able to import the test results. 1. Click the Build Features link in the left-hand menu. 2. Click the Add build feature button 3. Select XML report processing option. 4. Set the Report Type to NUnit and enter results.xml in the Monitoring Rules text box. 5. Click Save That s it! You have now successfully configured your first test project. Running your TeamCity build To run your build, go back to the TeamCity home package and select your project. Then, click the Run button and wait while your build is executing. Once your test has completed, you ll find an overview of the tests which have passed and failed, integrated in TeamCity. You can click on the test results link to get more information about the test results How To... 93

98 24/7 Mobile Application Monitoring with Quamotion You can use Quamotion, together with monitoring software, to continuously monitor the performance of mobile applications. Let s imagine that you have a consumer application, and you want to measure how long it takes to launch the application and sign into the application in different cities, and using different network operations. You may want to obtain graphics like the one below, which shows the timings of the Launch and Sign In operations for different geographical locations, over time: In that scenario, you can create a single script (using PowerShell or another scripting language), which automates these actions and records the time it takes to execute every step. You can deploy Quamotion to a server in different physical locations, to which you connect physical mobile devices connected to various mobile networks. Next, you enhance your script so that it reports back the timings to a montoring solution, such as Graphite, or Microsoft System Center Operations Manager. Finally, you configure your server to launch your Quamotion scripts on a schedule - for example, every 5 minutes. In this How-To guide, we ll walk you through the steps required to setup such a configuration using Quamotion and Graphite Overview You ll need to deploy at least the following components: 1. A data warehouse, to which you submit the measuruments and which stores the data. In this example, we will use Graphite as the data warehouse 2. A test script repository in which you store your test scripts. For example, you can use GitHub as your repository. 3. A scheduler which runs your Quamotion scripts on a schedule. For example, you can use a CRON script to run your scripts every 15 minutes. 4. A Quamotion server to which your mobile devices are connected. 94 Chapter 3. Requirements