Skip to content

Getting Started with Mobile Apps Testing with Worksoft SaaS

Before reading this you might want to see:

Main Article


This article will help you with getting started with the Mobile Apps Testing with Worksoft SaaS.

Please find below the high level steps that you should follow for you to build automated tests, execute them in the Worksoft SaaS mobile testing cloud and to enjoy the rich analytics and reports that Worksoft SaaS offers to you on the test execution outcomes.
  1. Create and Configure a 'Product' within your Project to reflect your Native/Hybrid Mobile App. To learn more on how to accomplish this step, click here.

  2. There are there ways to access the Mobile App in Worksoft Saas.
    1. If your Native/Hybrid Mobile App needs to be accessed vis Secure Storage, upload the Application Binary into the Worksoft SaaS by choosing Secure Worksoft Storage Based Access option. For more information on how to upload your mobile apps, click here.

    2. If it is publicly accessible via URL, choose Public URL option and provide the URL.

    3. If it is accessible via a URL through secure tunnel (if app binary is hosted within your company's firewalls), you need to reach out to the Project Lead or Contact person from the Worksoft SaaS for setting up the tunnels. Once the tunnel is setup, you can choose Secure Tunnel Based Access option, provide the URL and select the Tunnel name. For more information about Secure Tunnel Access and set up a tunnel, click here.

  3. Build the automated 'Test Scripts' by launching the app in Appium Inspector. For details on how to develop your tests, click here.

  4. Once your test scripts are in your 'Test Script Library' within the Worksoft SaaS application. Parameterize them and bind them to user-defined variables, etc to prepare them for data-driven testing.

  5. Assemble Test Scenarios and Run Definitions using the Test Scripts. For data-driven testing configure how the data will get fed into the tests at run time (data files, user defined variables, through QaCONNECT, retrieved from databases using dbCONNECT, retrieved from web services using wsCONNECT, etc.,). Also create the appropriate testing contexts that cover the mobile real devices or emulators/simulators you want to cover in your  tests. You essentially follow the same exact steps to assemble and execute Test Scenarios and/or Run Definitions for mobile app testing that you use in the context of testing web apps.

  6. Execute the tests and review the various reports and access the rich analytics. The same exact transactional and test cycle level and project level analytical reports that you avail in the context of web apps testing are also available for you to enjoy for mobile app testing.

After reading this you might want to see:



Feedback and Knowledge Base