Rover Mobile

Overview

Rover 2.0 is a state-of-the-art service designed specifically for exploratory testing of mobile applications. It empowers testers to evaluate the functionality, usability, and performance of mobile apps across diverse platforms and devices. With its powerful features, Rover 2.0 offers a structured yet flexible approach to exploratory testing, enabling users to configure test sessions, execute comprehensive explorations, and generate actionable reports—all optimized for mobile testing.

Modern mobile applications demand rigorous testing to ensure seamless user experiences across varying devices, screen sizes, and operating systems. Rover 2.0 is purpose-built to tackle these challenges, making it an indispensable tool for testers and QA teams focused on delivering robust, high-quality mobile apps.

Key Features of Rover for Mobile Testing

• Customizable Mobile Test Sessions: Configure testing sessions tailored to the requirements of mobile apps, including native, hybrid, and web-based applications.

• Device and OS Coverage: Test applications on a wide range of devices, operating systems, and versions to ensure compatibility and consistency.

• Real-Time Exploration Tools: Capture findings, take screenshots, annotate issues, and document results during test execution without interrupting the workflow.

• Performance and Usability Checks: Assess how the app performs under different conditions, such as low battery, limited network connectivity, or high memory usage.

• Responsive Design Validation: Test the responsiveness of your app across various device orientations (portrait and landscape modes).

• Detailed Reporting: Generate reports that provide actionable insights, highlighting issues across different devices and platforms.

Purpose of This Guide

This guide aims to help you unlock the full potential of Rover 2.0 for mobile testing. It will walk you through the steps to:

1. Set Up Mobile Test Sessions: Learn how to configure your testing environment for a variety of mobile devices and platforms.

2. Navigate the Rover 2.0 Interface: Understand the tools and features specifically designed for mobile exploratory testing.

3. Perform Exploratory Testing: Explore your mobile application while capturing defects, taking notes, and documenting findings in real-time.

4. Generate and Analyze Reports: Extract actionable insights from the generated reports to enhance the quality of your mobile app.

5. Integrate with Existing Tools: Connect Rover 2.0 with popular bug trackers and project management tools to streamline workflows.

By the end of this guide, you will be equipped to perform comprehensive exploratory testing of mobile applications using Rover 2.0, ensuring your app meets the highest standards of quality and user satisfaction.

Problem-Solution-Fit

Testing mobile applications presents unique challenges, such as varying hardware, software, and user behavior patterns. Rover 2.0 addresses these challenges by offering:

• Ease of Use: An intuitive interface that supports efficient and creative exploratory testing.

• Broad Compatibility: Tools to test apps across multiple platforms, including Android and iOS.

• Real-Time Defect Tracking: Log issues instantly with detailed notes, screenshots, and recordings for faster resolution.

• Adaptability: Support for testing both mobile-native and cross-platform applications.

• Collaboration Tools: Share test findings and reports effortlessly with team members and stakeholders.

Prerequisites

• Access to Qyrus platform.

• A registered account with appropriate permissions.

Step-by-Step Guide

ANDROID

Android

Open Rover 2.0

Navigate to the Qyrus platform and select Rover 2.0

• Sign In to Qyrus Platform and click on the Rover 2.0 card.

• This will open the first page of the application.

Open Rover 2.0

Configuration

Select the Configuration Tab

• Click on the Configuration Tab on the top left as shown in the red box.

• This will open up the tab content as shown below.

Configuration

Select the Service Type

• From the service type, you could choose between Mobile or Web.

• For example, select "Mobile". (Note : Selecting "Web" will lead to setting up of different set of configurations)

Service Type

Select the Application Type

• Select the relevant application type.

• The options are Android and iOS. Check inside the yellow box shown in the image below.

• For example we select "Android"

Application Type

On selection of Application Type

• Once an application type is selected eg. Android.

• Projects and Devices Dropdown will appear.

• From this we are supposed to select a Project and a Device where the application is supposed to run.

URL, Exploration Time, Session

Selecting Project and Device

• When a project and a device is selected.

• Example, Project : Rover Android Test, Device : Pixel 8

• The interactive screen appears to update with few more additional elements.

• You can select either of the two options for having an application run on the device eventually.

  • Install App: (When you have an apk file handy or already uploaded)

    • Select Application : Here you can select from the pre uploaded list of apks of the application.

    • Upload Application : Here you can choose from your files and upload an apk of the application

  • Launch App: (Directly launch the app using Package and Activity names)

    • Package Name : Takes a package name, eg. com.android.chrome. Basically the application.

    • Activity Name : Takes an activity name, eg. com.google.android.apps.chrome.Main . This is the type of activity to be carried out with the application.

URL, Exploration Time, Session

(i). Install App

• When Install App is selected

• Select or Upload an application

  • We either select an application if available or we upload an apk using the upload option given.

  • Let's select an application, Eg. Amazon Shopping_28.9.2.100_Apkpure.apk

Select Application

• Select an Activity for the Package

  • We either select an application if available or we upload an apk using the upload option given.

  • Let's select an application, Eg. Amazon Shopping_28.9.2.100_Apkpure.apk

Select Activity

(ii) Launch App

• Enter Package Name

  • The Package name of the application is to be input here. Eg. com.android.chrome etc.

• Enter Activity Name

  • Enter the activity name for the application, the kind of activity to be executed or explored in the application. Eg. com.google.android.apps.chrome.Main etc.

• Something like shown in the image below, orange arrows where 2 inputs are needed and the blue box suggesting where the "Launch App" was clicked in the first place.

Launch App

• Taking an example Package name and activity name, here how it would look,

Chrome Package and Activity

Option to give Customized Input

• Either you can choose to customize your exploration by giving some manual instructions.

• Or by default you can keep the exploration at auto ie, exploratory.

Customized Input

Click on the Submit button followed by Start Exploration Button

• Once Details in the configuration tab are filled we click on Submit button to first submit the package details and then we can click on the Start Exploration button.

• We click in order, first (1) Submit button, then (2) Start Exploration button.

• And as the name suggests, clicking on the start exploration button will start the exploration of the app.

Start Exploration

Live Activity

• Switch to Live Activity Tab.

• Here you can see live, how the app is getting explored.

• Starting which session creation notification, launching application notification, followed by actions taken and there respective descriptions. Also why that step is being taken.

• Check few screenshots of the exploration on live ctivity tab.

Live Activity

Live Activity

Live Activity

Live Activity

Activity Map

• On the Activity Map Page we can observe the graphs getting created. One mobile Screenshot connected to another.

Activity Map

Activity Map

Demo Video

• Watch the Demo Video Here.Your browser does not support the video tag.

Click Here if the video does not play

iOS

Open Rover 2.0

Navigate to the Qyrus platform and select Rover 2.0

• Sign In to Qyrus Platform and click on the Rover 2.0 card.

• This will open the first page of the application.

Open Rover 2.0

Configuration

Select the Configuration Tab

• Click on the Configuration Tab on the top left as shown in the red box.

• This will open up the tab content as shown below.

Configuration

Select the Service Type

• From the service type, you could choose between Mobile or Web.

• For example, select "Mobile". (Note : Selecting "Web" will lead to setting up of different set of configurations)

Service Type

Select the Application Type

• Select the relevant application type.

• The options are Android and iOS. Check inside the yellow box shown in the image below.

• For example we select "Android"

Application Type

On selection of Application Type

• Once an application type is selected eg. iOS.

• Projects and Devices Dropdown will appear.

• From this we are supposed to select a Project and a Device where the application is supposed to run. The device will be an iOS Device.

URL, Exploration Time, Session

Selecting Project and Device

• When a project and a device is selected.

• Example, Project : Dora_iOS, Device : iPhone 12

• The interactive screen appears to update with few more additional elements.

• You can select either of the two options for having an application run on the device eventually.

  • Install App: (When you have an ipa file handy or already uploaded)

    • Select Application : Here you can select from the pre uploaded list of ipas of the application.

    • Upload Application : Here you can choose from your files and upload an ipa of the application

  • Launch App: (Directly launch the app using Package and Activity names)

    • Bundle ID : A Bundle ID is to be provided. A bundle ID in iOS is a unique identifier assigned to every iOS application. It is used to distinguish one app from another within the Apple ecosystem.

URL, Exploration Time, Session

(i). Install App

• When Install App is selected

• Select an application

  • We either select an application if available or we upload an ipa using the upload option given.

  • Let's select an application, Eg. calculator-1.ipa

Select Application

• Upload an ipa (application)

  • We either select an application if available or we upload an ipa using the upload option given. Here we upload.

  • Let's upload an application, Eg. calculator-1.ipa

Upload ipa

(ii) Launch App

• Enter Bundle ID

  • The Bundle ID of the application is to be input here. Eg. com.apple.mobilesafari etc.

• Something like shown in the image below, when "Launch App" is selected. .

Launch App

• Taking an example Bundle ID, here is how it would look,

real bundle id

Option to give Customized Input

• Either you can choose to customize your exploration by giving some manual instructions.

• Or by default you can keep the exploration at auto ie, exploratory.

• In case of customized input, the exploration might follow the instructions given and additionally it might explore even after accomplishment of the custom instructions, for atleast 10 minutes.

• Example, let's say we have out safari application, and the custom instruction that dictate the exploration include eg., Go to Search BOx and Search for Qyrus Company (See inside Red box the custom instructions sthat is written in the image below)

Customized Input

Click on the Submit button followed by Start Exploration Button

• Once Details in the configuration tab are filled we click on Submit button to first submit the Bundle ID precisely, and then we can click on the Start Exploration button which appears after clicking the Submit button.

• We click in order, first (1) Submit button, then (2) Start Exploration button.

• And as the name suggests, clicking on the start exploration button will start the exploration of the application. The yellow arrow shows the Submit button and the red arrow shows the Start Exploration button, in the image below.

Start Exploration

Live Activity

• Switch to Live Activity Tab.

• Here you can see live, how the app is getting explored.

• Starting with session creation notification, launching application notification (check the red box in the image below).

Live Activity

• It shows what is the objective it is going to achieve. In the red box in the the image below, see an example objective.

Live Activity

• Now see the steps that it thinks it should follow in order to achieve the objective.

• And also see the right split of the screen, which shows what is happening on the device, meaning how the exploration is happening.

Live Activity

• For example, see a successful sear it made in the search box, searching for Qyrus Company

• Also for every step it takes, there will be action and deatils regarding that step.

Live Activity

Activity Map

• On the Activity Map Page we can observe the graphs getting created. One mobile Screenshot connected to another.

• Red box shows we are in Activity Map tab.

• Yellow box shows the area where the map of the activity is shown.

Demo Video

• Watch the Demo Video Here.

Your browser does not support the video tag.

Click Here if the video does not play

Use Cases

• Exploratory Testing: Perform exploratory testing on mobile applications to uncover edge cases, usability issues, and functionality gaps across various devices and platforms.

• Test Case Generation: Automatically generate test cases and scripts from exploration data, helping ensure comprehensive test coverage for mobile apps.

• Activity Tracking: Monitor and analyze testing activities with detailed activity maps and reports, offering insights into app performance, user experience, and defects specific to mobile environments.

FAQs

Q. What is Rover 2.0?

Rover 2.0 is a state-of-the-art service designed for exploratory testing of mobile applications. It allows testers to evaluate the functionality, usability, and performance of mobile apps across diverse platforms and devices, ensuring high-quality user experiences.

Q. What platforms and devices does Rover 2.0 support?

Rover 2.0 supports testing on a wide range of devices and operating systems, including Android and iOS. It is compatible with various device models, screen sizes, and OS versions, ensuring comprehensive coverage for mobile app testing.

Q. Can Rover 2.0 be used for both native and hybrid mobile apps?

Yes, Rover 2.0 is designed to test both native and hybrid mobile applications. It provides tools to configure test sessions, execute explorations, and generate detailed reports for all types of mobile apps, ensuring compatibility and performance across platforms.

Additional FAQs for Rover 2.0

Question	Answer
Q. What kind of APKs and IPAs can I test with Rover 2.0?	Rover relies on Appium under the hood to capture screenshots, inspect UI trees, and drive interactions. For this to work, the build you upload must be debuggable/instrumented: • Android: the APK should be signed with a debug or internally-signed key and built with android:debuggable="true". • iOS: the IPA should be an adhoc or dev-signed build that permits the accessibility services Appium uses. Production-signed, encrypted, or obfuscated builds (e.g., Play Store release builds with debuggable=false, IPAs signed for the App Store) can’t expose the view hierarchy, so Rover will refuse to start the session.
Q. Do I need to disable ProGuard or other obfuscation tools?	You don’t have to disable them entirely, but obfuscation must not block Appium’s accessibility APIs. In practice that means: • Ensure resource IDs and accessibility labels remain intact. • Keep ProGuard/R8 mapping files handy; they’ll help you trace obfuscated class names that Rover surfaces in its defect logs.
Q. How does “Custom Instruction” mode work?	Add a high-level scenario in plain language (e.g., “Sign in, search for a product, add it to cart”). Rover follows that instruction set first. Once the objective is achieved—or time runs out—it reverts to autonomous exploration so you still get broad surface coverage.
Q. What happens if I give no instructions?	Rover starts on the launch page, creates its own exploration plan, and executes it. When that plan finishes and time permits, it dynamically crafts a new plan from the current screen, iterating until the session ends.
Q. How long will a session run?	By default, 10 minutes. The limit is there solely for demo convenience; enterprise customers can request longer or variable session lengths via Qyrus support.
Q. Why can two sessions on the same app look different?	Rover’s decisions come from a large-language-model “brain.” Like a human tester, it weighs what it sees on-screen and chooses the next best action—so the exact path can vary with each run. Small context shifts (updated build, different device, new login cookie, or even phrasing changes in your custom instructions) nudge the model toward different, but still valid, routes. This slight unpredictability is intentional: it uncovers fresh edge cases instead of replaying the exact same steps every time. For critical flows you want covered every run, add them as Custom Instructions.
Q. Can I monitor progress while the test is running?	Yes. The Live Activity tab streams: • Current objective and next planned action • Real-time device video • Step-by-step rationale (“why I’m doing this”) to keep the human tester in the loop.
Q. Does Rover pause automatically when it hits a critical failure?	It logs the failure, captures a screenshot, and continues exploring unless the crash makes the app unresponsive. This ensures the session time is used efficiently and unrelated areas are still covered.
Q. How is the Activity Map useful?	The map visualizes the navigation graph Rover discovered—screens as nodes, actions as edges—letting you spot dead ends, missing links, or unintuitive flows at a glance. You can export the map in PNG or JSON for documentation or further automation.
Q. What device/OS versions are available?	The Qyrus device farm spans popular Android versions from 8.0 (API 26) to the latest release and iOS versions from 14 onward, across phones and tablets. Enterprise plans can request niche devices or OS betas.
Q. Is my application data safe?	All uploaded builds are stored in an encrypted bucket scoped to your Qyrus tenancy. Sessions run in isolated device simulators or physical devices wiped after each test. Logs and screenshots inherit the same tenancy isolation.
Q. What’s on the roadmap for Rover 2.0?	Near-term items include richer analytics (heatmaps, gesture frequency), deeper accessibility checks, and longer “follow-up” sessions that build on a saved Activity Map. Reach out via the Qyrus support portal to influence priorities.