Executing the algoQA Generated Scripts on LamdaTest

Modified on Fri, 1 Aug at 2:41 PM

TABLE OF CONTENTS

1. Overview

2. Executing the scripts on LamdaTest

3. Triggering the Build in LamdaTest 

1. Overview

This article provides you the procedure on how to execute algoQA generated scripts on LamdaTest.

2. Executing the scripts on LamdaTest

Perform the following:

  1. Navigate to App Testing from the left panel.
  2. Click Android icon. 
  3. Click Upload button to upload your respective APK file >select the required device brand and device. 
  4. Click Start button to start the build.
  5. You will be connected to the selected device by launching the emulator where you can perform your testing. In this case, Louise Philippe App is considered.
  6.  Similarly, you can perform on iOS devices too by selecting the appropriate options in the preceding screen. 


3. Triggering the Build in LamdaTest 

Perform the following:

  1.  Navigate to App Automation from the left pane by selecting Automation, as shown:
  2. To run the build, follow the steps from step 4 to step 10 as described in the Lamdatest integration to execute mobile automation scripts article. When the build is triggered, system captures the live recording of the steps, as shown:
  3. You can perform the following while live recording the steps in LamdaTest: 
    • You can view your Networks Logs, App Logs, and Device Logs. 

    • You can also view XPaths for a particular UI element/control after selecting the UI Inspector feature.
    • With the device controls, you can change the keyboard language, the device orientation, put device to sleep mode, increase and decrease volume.
    • For more information on the preceding topics, refer to the topic in LamdaTest - Realtime Native Mobile App Testing.







Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article