Mobile Testing with Appium

The Ocaramba.Tests.Appium project provides the implementation and configuration required for automated mobile testing using the Appium framework. It specifically demonstrates Android automation using the UiAutomator2 driver, handling native app interactions, complex gestures like scrolling via AndroidUIAutomator, and context switching for Hybrid applications (WebView).

Solution Structure and Dependencies

The Appium test project is built on top of OcarambaLite and utilizes the Page Object Model (POM) defined in Ocaramba.Tests.PageObjects.

Project Configuration

The project targets net8.0 Ocaramba.Tests.Appium/Ocaramba.Tests.Appium.csproj4 and includes essential mobile automation libraries:

• Appium.WebDriver (8.1.0): Core library for Appium server communication Ocaramba.Tests.Appium/Ocaramba.Tests.Appium.csproj12
• Selenium.Support & WebDriver: Used for standard element interactions and waits Ocaramba.Tests.Appium/Ocaramba.Tests.Appium.csproj14-23
• NUnit (4.4.0): The test runner used for mobile test execution Ocaramba.Tests.Appium/Ocaramba.Tests.Appium.csproj19-21

Mobile Test Data Flow

The following diagram illustrates how Ocaramba initializes the mobile driver and interacts with the Appium server to control an Android device or emulator.

Mobile Driver Initialization Flow

Sources: Ocaramba.Tests.Appium/UnitTest1.cs11-12 Ocaramba.Tests.Appium/AppiumSamplePage.cs13 Ocaramba.Tests.Appium/Ocaramba.Tests.Appium.csproj12 Ocaramba.Tests.Appium/appsettings.json34-37

Implementation Details

Page Objects: AppiumSamplePage

The AppiumSamplePage class demonstrates how to define mobile-specific locators using AccessibilityId and standard Selenium By selectors.

• Locators: Uses ElementLocator with Locator.AccessibilityId for cross-platform mobile identification Ocaramba.Tests.Appium/AppiumSamplePage.cs15-16
• Wait Mechanisms: Employs WebDriverWait with ExpectedConditions.ElementToBeClickable to handle mobile UI latency Ocaramba.Tests.Appium/AppiumSamplePage.cs44-47
• WebView Interaction: Includes methods to fetch text from within a web context using CSS selectors after a context switch Ocaramba.Tests.Appium/AppiumSamplePage.cs57-61

Test Logic and Context Switching

The AppiumAndroidTests class contains logic for navigating native Android menus and switching to WebView contexts.

• Scrolling: Utilizes MobileBy.AndroidUIAutomator to perform complex UI actions like scrollIntoView within a UiScrollable container Ocaramba.Tests.Appium/UnitTest1.cs20-25
• Context Switching:
  • DriverContext.SwitchToWebView(): Transitions the driver focus from the native application to the embedded Chrome WebView Ocaramba.Tests.Appium/UnitTest1.cs37
  • DriverContext.SwitchToNative(): Transitions focus back to the native Android OS layer Ocaramba.Tests.Appium/UnitTest1.cs39

Code Entity Mapping

This diagram maps the natural language actions to specific code entities and locator types within the Appium project.

Mobile Action to Code Mapping

Sources: Ocaramba.Tests.Appium/AppiumSamplePage.cs15-16 Ocaramba.Tests.Appium/UnitTest1.cs20-21 Ocaramba.Tests.Appium/UnitTest1.cs37 Ocaramba.Tests.Appium/UnitTest1.cs11 OcarambaLite/Locator.cs71-72

Environment Setup and CI/CD

Android Emulator Pipeline

Ocaramba uses GitHub Actions to run mobile tests. The pipeline handles the setup of the Android environment and the Appium server.

• ChromeDriver Setup: The setup_chromedriver.sh script is included to ensure the version of ChromeDriver matches the WebView version in the emulator Ocaramba.Tests.Appium/setup_chromedriver.sh1-16 It detects the version via adb shell dumpsys Ocaramba.Tests.Appium/setup_chromedriver.sh3 and downloads the matching driver from Google Chrome Labs Ocaramba.Tests.Appium/setup_chromedriver.sh7-13
• Configuration: Environment-specific settings are managed via appsettings.json and appsettings.Linux.json. Key parameters include:
  • AppiumPlatformName: Set to "Android" Ocaramba.Tests.Appium/appsettings.json32
  • AppiumAutomationName: Set to "UiAutomator2" Ocaramba.Tests.Appium/appsettings.json38
  • AppiumAppPath: Points to the location of ApiDemos-debug.apk Ocaramba.Tests.Appium/appsettings.json34
  • chromedriverExecutable: Path to the downloaded driver for WebView testing Ocaramba.Tests.Appium/appsettings.json39

Locator Translation

The LocatorExtensions.ToBy() method bridges Ocaramba's ElementLocator to Appium's MobileBy types.

Locator Enum	Translated To	Usage Scenario
AccessibilityId	MobileBy.AccessibilityId	content-desc on Android OcarambaLite/Extensions/LocatorExtensions.cs72-74
AndroidUIAutomator	MobileBy.AndroidUIAutomator	Complex selectors like UiSelector().text("Login") OcarambaLite/Extensions/LocatorExtensions.cs75-77
IOSNsPredicate	MobileBy.IosNSPredicate	iOS specific filtering OcarambaLite/Extensions/LocatorExtensions.cs78-80
AppiumId	MobileBy.Id	Native element IDs OcarambaLite/Extensions/LocatorExtensions.cs84-85
AppiumClassName	MobileBy.ClassName	Mobile class name selectors OcarambaLite/Extensions/LocatorExtensions.cs86-87

Sources: Ocaramba.Tests.Appium/Ocaramba.Tests.Appium.csproj1-54 Ocaramba.Tests.Appium/AppiumSamplePage.cs1-65 Ocaramba.Tests.Appium/UnitTest1.cs1-47 OcarambaLite/Extensions/LocatorExtensions.cs72-96 Ocaramba.Tests.Appium/setup_chromedriver.sh1-16 OcarambaLite/Locator.cs71-78