How jardevson/appiumrobot works
Project type and purpose
• This is a mobile test‑automation framework using Robot Framework and Appium.
• The README title “AppiumRobot” and presence of an APK under resources/app/app.apk confirm it’s built to drive automated UI tests against an Android application.
• The CI workflows reference BrowserStack and a generic CI pipeline, indicating automated cross‑device test execution.
File structure
• Top‑level files:
• .env.example – environment variables for credentials, endpoints, BrowserStack keys, etc.
• requirements.txt – Python dependencies (Appium‑Python‑Client, Robot Framework, etc.)
• base.resource – shared Robot resource (likely global variables or settings).
• resources/ directory:
• app/ – contains the mobile .apk under test.
• libs/ – Python or Robot keyword libraries (e.g., DotEnv.py for loading environment variables).
• locators/ – YAML files defining element locator maps for each screen (homeLocators.yaml, signInLocator.yaml, etc.).
• pages/ – Robot resource files representing page‑object definitions (homePage.resource, searchPage.resource, etc.).
• utils/ – generic Robot resource files for common operations (customKeywords.resource, openApp.resource).
• tests/ – Robot test suites (.robot files) that implement test cases, each importing resources and calling keywords.
• .github/workflows/ – CI pipelines for local CI runs and BrowserStack integration (ci.yml, browserstack.yml).
README for additional insights
• README is minimal but the project name confirms Appium + Robot Framework.
Elements
– Tests → Resources → Appium → Devices
– CI Server → triggers Test Runner
– Test Runner → loads .env → libs
– CI Server → BrowserStack → Devices
– Blue for Robot Framework artifacts (tests, resources)
– Green for infrastructure (Appium, devices, BrowserStack)
– Orange for config/data (APK, YAML, .env)
Detail
• CI workflows launching either local Appium or BrowserStack sessions.
• Both normal test execution and CI‑driven runs.