How kaushd/appiummobiletest works
Main Components
• Client (Test Scripts) – In this project, the test scripts are located primarily in the “src/test/java” directory. These represent the entry point where tests are written, including Page Objects (under the pages folder) and various TestNG test classes.
• Appium 2 Server – Though not part of the codebase, the framework uses Appium as the automation hub. It manages sessions and communicates with mobile drivers.
• Drivers – These are external installable packages (e.g., UIAutomator2 for Android, XCUITest for iOS) that Appium uses to interact with the underlying mobile OS frameworks.
• Device Under Test – This represents the physical devices, emulators, or simulators where the mobile app is executed. Again, this is an external component in the ecosystem.
Relationships and Interactions
• You might also include a configuration/utility component that represents support files (e.g., “global.properties”, “chaintest.properties”, and other configuration files in the resources folder) that help manage the framework’s settings.
Architectural Patterns and Technologies
• That the project follows a layered architecture where the test scripts (client) layer interfaces with an external Appium 2 server.
• That this is a TDD approach using TestNG for testing, and the use of Maven for dependency and build management.
• If desired, mention in an annotation that page objects (e.g., files under src/test/java/pages) are part of the abstraction for UI elements.