Understand Mobile Testing | Zoho QEngine Help

Understand Mobile Testing

1.  Overview 

Zoho QEngine provides the versatility to formulate test cases for diverse platforms using the Platform Switch option. Users have the flexibility to select their desired testing platform—be it Web browser, mobile (Android and iOS ), or API. In this document, we will learn about mobile testing.
 
Mobile testing is crucial for delivering high-quality mobile applications that can provide a seamless user experience across different devices and platforms. With the growing use of mobile devices for various purposes, mobile testing has become increasingly important for users to ensure that their mobicle applications meet their needs and are free from errors and defects. For example, the testing process involves validating that the app functions seamlessly across various mobile devices, operating systems (iOS and Android), and different versions of those operating systems.
 
Zoho QEngine facilitates two dedicated platforms for mobile testing, one each for Android and iOS. The Android platform is likely designed to accommodate the unique characteristics of Android devices and applications. This includes handling different devices, their varying screen sizes, and interactions specific to the android ecosystem. The iOS platform, on the other hand, is likely optimized for testing applications developed for iPhones, iPads, and other iOS devices. This involves considerations for Apple's design principles, device variations, and the latest iOS updates. Users can switch between the platforms based on their testing requirements.
  
Effortlessly create test cases using the available tasks that are compatible with both iOS and Android requirements. You have the flexibility to conduct testing on both real and virtual devices. To initiate the process of creating your Android or iOS test cases, simply set up your devices with your local agent.

2.  Test Case Creation 

Testers can utilize the two methods offered by Zoho QEngine for seamlessly creating test cases:

 

  • Recording test cases

  • Writing test cases using editor or builder mode

 

Recording test cases


The recorder simplifies test case creation using its ability to capture user interactions such as taps, swipes, and inputs from your mobile applications. It transforms these recorded interactions into a script, providing an automated and efficient method for generating test scenarios without writing scripts manually.
 
For example, a mobile app development company has built a new fitness app that tracks the user's daily exercise routine, diet plan, and weight loss progress. The company wants to ensure that they have properly tested the app on all devices and operating systems for both iOS and Android platforms. Zoho QEngine can assist in fulfilling their testing needs, ensuring the proper functionality of the fitness app across devices and operating systems.

 

To learn more about how recorded test cases are created for Android and iOS, refer to the Create Android or iOS Test Cases using Recorder page.

 

Let's understand some of the advantages of recorded test cases over creating test cases manually.
  • Faster test case creation: Recording test cases automates the process, saving time and effort compared to manually writing each test step. Testers can quickly capture interactions, reducing the overall testing time.
  • Easily captures interacted elements: They capture all the interacted elements and save them along with their corresponding page names automatically.
  • Device flexibility: These test cases offer the flexibility essential for comprehensive testing, covering various screen sizes, resolutions, and device configurations.
  • Provides preview of the interactions: They capture all the interactions to give testers a preview of what is being tested, as they can see the exact steps and inputs used in the test case.
  • Avoid scripting errors: Recording ensures test cases across devices and environments capture the interactions as they are from the tested workflow.
  • Tasks available within the recorder: Selected tasks such as "Assertion", "Wait", and so on can be performed on the elements interacted on the recording screen or window.

3. Writing test cases using editor or builder mode 

Zoho QEngine's test case editor is specifically designed to accommodate user preferences. They have the choice to either record or write test cases manually using the editor or builder mode.
 
To learn more about how test cases are created for Android and iOS platforms using builder and editor modes, refer to the Create Android or iOS Test Cases using Editor or Builder mode document.

4. Key mobile testing features in Zoho QEngine: 

  • Auto-completion 
    The auto-completion feature helps with writing test cases. It auto-suggests all the interacted elements, tasksand saved variables. It also includes functions that are saved within the same module as the test case.

  • Save in Editor
    The editor catches incorrect/missing arguments in tasks and inconsistencies within test cases. Warnings are issued if any attempts to save test cases are made without addressing these discrepancies.

  • Manual view 
    Manual view offers a platform for conducting manual testing that requires human intervention. Within this view, users have access to a text editor where they can input pre-conditions, steps, and expected outcomes. Additionally, users can attach relevant files about their test cases.

  • Versioning
    Maintain versions for every test case created, allowing users to compare and restore previous versions.

  • Refer elements 
    Get instant access to all elements created using the Refer Elements option. Review, copy, and add new elements, if necessary.

  • Mobile Inspector 
    Inspects element locators that are otherwise challenging to retrieve. Accurate locators are required to improve the testing accuracy and efficiency of the created test cases. 

5.  Mobile testing best practices  

  • Utilize variables to avoid repeatedly entering values that are found in input fields of a form, such as name, username, date, and the like.
  • Avoid hard coding locators in your test cases. Instead, use the recorder to save all the locators as elements. These recorded locators are saved along with their page name for maintenance and better debugging.
  • Repetitive actions performed within a mobile application can be replaced with functions in a test script.
  • The test case should be associated with the right module. For example, an ecommerce application contains distinct modules like Product Search, Checkout, and User Profile. If test cases for verifying payment functionality are associated with the "User Profile" module, crucial issues related to payment processing might be missed. However, linking these test cases to the correct "Checkout" module ensures targeted and effective testing, guaranteeing a smoother and more reliable payment experience for users.

6.  Related Links