↓Skip to main content

Mitrinic

578 words·3 mins
NICK
Author
NICK

Role: Automation QA
Domain: Mobile Automation

                           - Stack -

Python3, Android SDK, Appium, Selenium, SQL, Jenkins, Swagger

                       - Project Overview -

The smartphone manufacturers like Samsung, Xiaomi, and Google Pixel provide remote device management. The project involved developing a products for this Android remote device management.
Samsung offers its Knox Guard for device management, providing robust security and remote device control capabilities. For Xiaomi, a similar feature comes under its MDM (Mobile Device Management) systems integrated with MIUI Enterprise solutions, which focus on device protection and fleet management features. Google Pixel devices utilize Android Enterprise, offering a suite of management tools like device policy controls and security mechanisms.

Here are three key features:

  1. Fraud and Theft Protection: allows administrators to remotely lock devices and restrict usage in case of suspected fraud or if a device is reported lost or stolen. This feature helps reduce financial risks by preventing unauthorized use.
  2. Customizable Lock and Message Settings: Administrators can customize the lock screen messages to display relevant information for users, such as instructions for device or contacting support.
  3. Remote Management and Monitoring: Through a centralized dashboard, administrators can monitor device status, enforce different policies, and manage the devices efficiently, all while ensuring that corporate data remains secure.

A security solutions designed to protect devices from misuse or unauthorized access. Each of these platforms is geared toward enterprise mobility and robust device control, especially in corporate settings.

                      - Responsibilities -

List of my responsibilities in a clear, task-oriented format:

  1. Android Devices Configuration for Automation Purposes.
  • Ensuring compatibility with test requirements.
  • Setting up Jenkins jobs for the Android builds.
  • Handling multiple device settings.
  1. Automated Test Cases Within The Project Framework for Web GUI.
  • Automating test cases.
  • Integrating the tests into a CI/CD pipeline.
  1. E2E Automated Tests Against Android Devices.
  • Setting up test cases to cover different device states.
  • Utilizing Behavior-Driven Development (BDD) and incorporating Gherkin syntax into tests to improve client undertanding.
                   - Challenges & Solutions -

Automating end-to-end (E2E) scenarios, such as managing device settings and interacting with multiple applications, was challenging and required scripting. To handle device-level commands and specific automation needs, the Android’s tools was leveraged.

Also there is a wide range of Android devices with different manufacturers, models, screen sizes, OS versions, and custom modifications. Ensuring that the product functions seamlessly across all these variations is complex.
Testing was prioritized on the most popular devices and operating system versions, guided by target market analytics, to maximize compatibility and efficiency.

                   - Reflections & Takeaways -
  1. Complex Automation Handling:

  • Reflection: Automating interactions across multiple applications and device settings proved to be more complex than anticipated. Managing device-level behaviors required understanding of Android systems and robust scripting capabilities.

  • Takeaway: Breaking down these complex tasks into smaller, manageable steps and leveraging ADB commands efficiently can simplify automation. Early investment in understanding device architecture pays off during test script development.

  1. Device and OS Fragmentation:

  • Reflection: Prioritizing the right devices and operating systems for testing was crucial, as the Android ecosystem is highly fragmented. Analytics-based decisions helped streamline testing efforts.

  • Takeaway: Continuous monitoring of market trends is essential. It is helpful to maintain a flexible testing strategy to accommodate updates in popular devices and new OS releases.

  1. Team Collaboration and Knowledge Sharing:

  • Reflection: Working on a project with complex automation challenges underscored the importance of collaboration and knowledge sharing among QA and development teams.

  • Takeaway: Regular knowledge-sharing sessions and well-documented processes can significantly improve team productivity and skill sets, leading to more robust solutions.