Page Comparison

...

1. Do one of the following:

   1. To dry run a test case, click Settings > System Execution Profile.

   2. To execute a test suite using a custom execution profile:

      1. Click Execution > Execution Profile.

      2. Do one of the following:

         • Click New to create a custom execution profile.

         • Under the Edit column, click the Edit button for the custom execution profile that you want to use.
           Note: If your suite or test case executes on a web application too, configure the required settings. For more information, refer to Configuring the System Execution Profile Settings.

2. Click the Mobile tab.

3. From the Appium Options drop-down, select one of the following modes:

   1. Automatic: To allow QAS to communicate with the Appium server bundled with QAS.

   2. Custom: To allow QAS to communicate with another Appium server.
      Do one of the following:

      • To use the Appium server hosted on your computer, enter http://localhost:4723/wd/hub

      • To use the Appium server hosted on a remote computer, enter http://xyz:4723/wd/hub,where xyz denotes the IP address of the remote computer.

4. Set Execution Platform to Android.

5. (Mandatory) Enter the UDID of the device.

6. Select a mobile browser as Chrome or Browser.

7. If your Android app is hybrid or web, select the Execute on Mobile Web checkbox.

8. (Mandatory) Enter the Device Name of the Android real device or emulator.

9. From the Automation Name drop-down list, select any one of the following automation frameworks:

   • UIAutomator2 (Recommended)

   • Appium

   • Selendroid

   • Espresso

10. If your Android app is hybrid or web, under Edit Desired Capabilities, enter the following information:

    • platformVersion: Enter the platform version of the Android real device or emulator.

    • chromedriverExecutable: Enterthe absolute local path to the chrome driver executable (if Chromium embedder provides its own web driver, it should be used instead of the original chrome driver bundled with Appium).

      Example: chromedriverExecutable=/abs/path/to/webdriver

      Alternatively, if you have chosen Appium for execution, from the Appium UI, under the Advanced Settings, enter the chrome driver path.

    • NativeWebScreenshot: nativeWebScreenshot (Mandatory for hybrid applications): Select this check box, and set its value to True. This option ensures that during the execution when switching from native-context to web-context, the screenshots are displayed for the steps executed on web-context in the Execution Summary Report.

...