How tamizh138/automation-playground-selenium-appium works
Project type and purpose
• This is a multi-module automation framework template combining:
– A web-automation module (Selenium4 + BrowserStack)
– A mobile-automation module (Appium)
– A sample/demo application module (app)
• README confirms goals: provide a template for Selenium4, Appium, cloud execution, and beginner-friendly patterns (Page Object Model, driver abstraction).
File structure
• Top-level:
– settings.gradle.kts, gradle wrappers – multi-module Gradle build
– docs/ – Markdown design docs
– gradle.properties, libs.versions.toml – version management
• Sub-modules:
– WEBAutomation/ – src/main/java/com/refactorauto/pageobjects + src/test/java/com/refactorauto/tests → Selenium4 Page Objects, tests, driver/CloudProvider abstractions
– MobileAutomation/ – simple Java entry point under org.example.Main (Appium hooks go here)
– app/ – demo Java app under org.example.App (stand-in for SUT)
README for insights
• Mentions Selenium4, Appium, BrowserStack, CloudProvider strategy
• Links to detailed design docs under docs/ (Selenium4Framework.md, AppiumFramework.md)
Main components
a. Gradle Multi-module Build (root)
b. WEBAutomation module
• Page Objects layer (HomePage, LoginPage)
• Test layer (AbstractBaseTest, TestLoginActions, login.feature)
• Driver abstraction (DriverFactory, BrowserHandler, ChromeHandler, FireFoxHandler)
• CloudProvider strategy (CloudProviderInterface, BrowserStackProvider, LamdaTestProvider)
• Logging (log4j2.properties, TestStatusLogger)
c. MobileAutomation module
• Appium test harness (Main.java → orchestrates mobile sessions)
• Gradle scripts
d. Demo Application (app module)
• Application Under Test (App.java)
e. External Services
• Amazon.com (demo site)
• BrowserStack, LambdaTest (cloud execution platforms)
• Appium Server (for mobile device automation)
Relationships and interactions
• Tests (WEBAutomation, MobileAutomation) ←→ Gradle build orchestrates compile/test
• WEBAutomation tests → DriverFactory → BrowserHandler/CloudProvider → Browser instances on local or cloud
• MobileAutomation tests → Appium client libraries → Appium Server → Mobile device/emulator
• Tests read page objects, feature files; log results via TestStatusLogger
• Sample app/module is packaged/deployed if mobile tests target it; separate from web tests targeting Amazon.com
Architectural patterns and design principles
• Page Object Model for web tests (separate page locators & actions)
• Strategy Pattern for CloudProvider abstraction (interface + multiple implementations)
• Factory Pattern for driver selection (DriverFactory)
• Modularization via Gradle multi-module build
Relevant technologies/frameworks
• Selenium 4 (WebAutomation)
• Appium (MobileAutomation)
• JUnit/TestNG (test framework)
• Gradle Kotlin DSL (build scripts)
• BrowserStack, LambdaTest (cloud)
• log4j2 (logging)