Real-Time Testing allows you to perform live-interactive cross browser testing of your website and web apps in the TestMu AI test cloud on over 3000+ real browsers and browser versions running on various operating systems.
Introduction to the video
How to perform Real-Time Testing on Real Devices
Demonstration Of Real-Time App Testing on real devices
Features of the Control Bar on the TestMu AI Platform
Demonstration Of Real-Time Browser Testing on real devices
Conclusion
This video was recorded before LambdaTest became TestMu AI, so the speaker uses the LambdaTest name.
Hey, what's up, everybody? My name is Moss, and in this video, I'm going to demonstrate how to perform real-time app and browser-based testing on real devices hosted on the LambdaTest platform. Among other benefits, testing on a real device is an ideal choice if your mobile or web application is resource intensive and requires a physical device to run optimally. Let's take a closer look at real-time testing on real devices.
Okay, so the first thing that I want to do is navigate to lambdatest.com, and once I'm there, I'm going to navigate to my LambdaTest dashboard here up in the top right. And if I wasn't logged in, I would want to log in first, and then I could navigate to the LambdaTest dashboard.
And once I'm taken to the dashboard, I'm going to expand this sidebar menu, and then under Real Time Testing, we have Real Device Testing. And if I expand this dropdown menu, you can see real-time testing on real devices and App Automation testing on real devices, and in this video, we are going to cover real-time testing on real devices, so I'm going to go ahead and select Real Time.
Real-time testing is separated into real-time app testing and real-time browser-based testing. Let's first demonstrate real-time app testing, and then we'll explore browser-based testing. And if you notice the message here, it says "Test your app on blazing fast real devices," and this is in contrast, if I expand this sidebar menu, to the Real Time Testing feature, in which we're performing real-time testing on our web application or mobile application, but on simulators and emulators. And in this case, under the Real Device feature, we are performing that testing on physical devices.
The first step is to select our operating system, either Android or iOS. Notice that as I select the operating system, the list of possible device configurations is automatically updated on the right-hand side. After selecting the desired operating system, I can then specify how to install the application. My first option is to install the application via the Google Play Store for Android devices or the App Store or TestFlight for iOS devices. If I were to select the Google Play Store for installation, the Google Play Store will open immediately after the test session begins.
My second option would be to upload the application from my local machine or specify a source URL where the application can be downloaded from when the test session begins. If I've previously uploaded an application, it will appear in this list for 60 days after upload. In this case, I am not going to upload an application or specify a source URL, and instead will use this sample application that is provided by LambdaTest. To use this application, I'm going to select it.
After selecting our application, we can then select a specific brand and device configuration for this test session, and as you can see, we can select from a large array of various brands as well as specific devices and operating systems. Similar to Android devices, we can perform device configuration for iOS devices as well. Under Device Type, we can select either iPhone or iPad, and then we can select the specific device and operating system version. For this test session, I'll use an Android device. Now that I've selected my desired device configuration, I can begin the test session simply by pressing Start.
After starting a session, a fresh real device matching our device configuration is allocated. It is important to note that every time we start a test session, we are provided a device that has been essentially wiped clean of its data from any prior sessions, so you can be sure that when your test session has completed, the data on the device will be deleted. As you can see, once we've connected to the real device, our sample application is automatically started, and we can begin our manual testing of this mobile application.
On the left-hand side, we have a control bar that allows us to perform various actions, and the control bar can be collapsed or moved to a different location on the screen. The first option in the control bar allows us to perform several actions. From here, we can install a new application by uploading it from our local machine, specifying a source URL, or selecting a mobile application that was previously uploaded from this list. The next action allows us to kill our mobile application. Additionally, we can also uninstall our application.
The next option in the control bar allows us to change the device configuration. If I select Switch, it will take me to a screen where I can select a new device configuration, including a completely different brand, device, and operating system version. Doing so will create a new test session.
If, during our manual testing, we identify a bug in our mobile application, we can utilize the Mark as Bug functionality to create a screenshot and save it. From this page, we can highlight where the bug is located in the screenshot using the annotations on the left-hand side menu. Once we've annotated the screenshot, we have several options. First, I can download the screenshot to my local machine using this down arrow.
I can also utilize the Mark as Bug feature, which will share the screenshot with external tools that I've integrated with my account. In my case, I haven't integrated any external tools with my LambdaTest account, so when I select the Mark as Bug button, it should prompt me to integrate an external tool. And as you can see, I can share this screenshot with tools like Slack and Jira, and if I select More Integrations, it will take me to a page showing the full list of possible tools that you can integrate your LambdaTest account with.
In this video, I'm not going to utilize one of the external tool integrations, and instead I'll create an issue in LambdaTest Issue Tracker. Using this form, I can assign this issue to myself or someone on my team. I can also specify the type of issue as well as the priority of the issue, and finally, I can provide a summary and description of the issue. Once I select Create Issue, it will create a new issue in LambdaTest Issue Tracker with this screenshot attached. Rather than creating a new issue for this screenshot, I can choose to save the screenshot, which will associate it with this test session.
In addition to taking screenshots, I can also record the current test session using the Video feature. All I have to do is select Video to begin recording the test session. When I'm ready to finish recording, I simply need to select the Video button again to stop the recording. Screenshots that have been saved and recordings can be found in the Gallery. Here you can see the screenshot that I previously created, and I can download the screenshot from here. And from the Videos tab, I can see all of my saved videos, and similar to screenshots, I can also download saved recordings from here.
Below the Gallery, we have App Logs. When I select App Logs, it will allow me to view various logs from the device and our mobile application. From this dropdown, we can select to view all device logs or just the logs from our sample application. In addition, we can also filter on the log level, and if needed, I can download the logs to my local machine, pause the logs, or clear the logs. And to close the App Logs, I can simply select App Logs again.
In addition to App Logs, I can also modify the IP geolocation of the device using the Change Geolocation button. From here, I can either use the country dropdown menu to select the desired country, or I can use GPS geolocation to set the location. Under Geolocation, we have Device Controls. Device Controls allows us to do things like change the language from this dropdown menu. Additionally, we can control the volume of the device, as well as utilize the home button. I can also rotate the device orientation.
One thing that's important to note is that if I have a web application in addition to my mobile application, I can also test the web version of my application in the real-time app testing session by navigating to the browser and then to my web application.
Under Device Controls, we have the Settings option. The Settings option allows us to perform network throttling, as well as associate this test session with a specific project. Currently, there is no network throttling, but if I select this dropdown menu, I can select a new network profile that will allow me to test my mobile application under different network conditions. We can even test within different bandwidths of a network profile, such as Fast 3G and Slow 3G.
Finally, when we've completed manual testing of our mobile application, we can end the test session using the End Session button. Once we've ended our test session, we can access the issue that was created in the LambdaTest Issue Tracker by navigating to the left-hand side menu and then to Issue Tracker. As you can see, we can review the issue that was created during our test session and update details of the issue, such as the status, priority, etc. We can also see the screenshot that was associated with this issue. I'm going to navigate back to the Real Device page.
Now that I've demonstrated real-time app testing on real devices, let's take a look at real-time browser-based testing on real devices. To do so, I'm going to select the Browser Testing tab. The first field that you see here is where I'll enter a target URL for manual testing. For this demo, I'll use lambdatest.com. If the site wasn't publicly available and we needed to perform manual testing on a site hosted on our local machine, we could utilize the Lambda Tunnel client program, which is a program that allows the LambdaTest platform to connect to a site hosted locally on your machine.
In this video, I'm not going to demonstrate testing of locally hosted sites, but it's important to note that that functionality is available, and if I did have a tunnel running locally on my machine, I would select that tunnel from this dropdown. Similar to app testing, we would then select our desired device configuration, starting with the operating system, either iOS or Android. In addition to the brand and specific device and operating system version, we can also select what browser we would like to use.
Next to the operating system selection, you may have also noticed this third selection called History. Using the History tab, I can actually start a new test session using the device configuration of a previous test session. I can also favorite a test session configuration, which will move it to the Favorites tab. I've entered a target URL and selected a desired device configuration. I can begin the session.
As you can see, when the test session begins, we're taken to our target URL, and we can begin our manual testing. You'll notice that on the left-hand side, the control bar has many of the same options that are available during real-time app testing. Let's walk through the features that are different from real-time app testing in the control bar. Instead of App Logs, we can utilize DevTools. DevTools allows us to do things like inspect elements of our website, access the console, and monitor things like network traffic, performance, etc. To close DevTools, I simply need to select the DevTools button again.
The other difference is the ability to change the language under the Device Controls menu, but you can still adjust volume on the device, rotate the device's orientation, and navigate to the home screen. Once I'm finished performing manual testing on my website, I can end the test session using the End Session button. I hope you've enjoyed this demonstration of real-time app and browser-based testing on real devices hosted on the LambdaTest platform. Thanks for watching, and I will see you in the next video.