Nathan:Welcome to the HeadSpin platform. We have test devices in more than 50+ locations worldwide. And from the consolation of your browser you can use real Android and iOS devices on bearer meshing for example for my account.

I hold a wealth of devices to choose from.

In Asia-Pacific, Europe, Middle East, Africa, Latin America, and North America using devices is real simple and straightforward. Simply click on your location of interest and take a twist in that area. For example, I ’ ll select this nexus 5X on the AT & amp; T LTE meshwork and now I ’ m really.

That being said any interactions I have with device get render to touch events and as you can see it ’ s buttery smooth. We get it very bare to interact with the device and all device operation.

For example, I can install an APK well by dragging and dropping to upload. As you can see by only just dragging and dropping my APK, I was capable to establish it and invoke it on this Android device.

In addition to remote control you can also run automation test on your devices and we endorse a variety of mechanization frameworks such as Appium, Espresso, XCUItest and more.

In this demonstration, I ’ ll on this gimmick with the help of Appium desktop. When you ’ re running an mechanization test on a twist you put it and read-only mode so it ’ s reserved for you and you can view what ’ s happening on the device and the case for Appium, the server logs side by side. In this case, I ’ m launching the application that I just install on this gimmick, Firefox Focus.

And that being said, now I have access to the full Appium desktop Inspector and I can actually part recording my interaction with this gimmick and countenance Appium to generate the examination for me.

Ilya: That ’ s right Nathan.

As you can see it ’ s very easy to create these Appium tests or any other tests. And now let ’ s talking about the CI/CD integration.

So, what you ’ re seem at hither is a great fascia where every one of these data point represents a habitus. And every time there ’ s a new build generated it have pushed to these real devices and the test are execute in order. And what we ’ re doing here on that Firefox…what we ’ re perform here on that Mozilla coating fundamentally profile every single build you can see exactly how long each of the examination runs and we can do this to create this trend chart showing build over build, how the speed of each test changes as different codification is added or modified. What we see here for exemplar is there is a lag where this scenario went from 5.3 seconds to 6 minute. This being a developer puppet we can simply compare this upload against the currently selected one, or the latest, and what we ’ ll see here is the actual reason why the code change has created a slower situation.

As I was say you can see here the build is now 6 seconds for this particular. It employ to be 5.3 s. Now what we can do here is look at the existent yell spate with timing information to see what ’ s happening. So yeah as you can see here the UI thread runs for 722 milliseconds. And notice this chrome IO ribbon here is a 252 milliseconds. Now on the other hand we receive a slightly faster UI thread at 684 msec. But look at this chrome Io thread it ’ s actually get much obtuse. So we can clearly see that the reason the anatomy hither ran for longer is because of this particular method being slowed down and now developers can look into the details of that.

SUSA automates exploratory testing with persona-driven behavior, catching bugs that scripted automation misses.

And again there ’ s some different test that were being done, but let ’ s actually rivet on what happens during the Cold inauguration; that ’ s the time from when the app is click. That ’ s the time it conduct the app to really launch to the first screen where users can interact with the app. And so if you look at the detail here you ’ ll see that this particular frigidity startup takes 4.1 seconds. There ’ s some metrics here about network and disk I/O, but the key is these 30 retardation

So, let ’ s look at those in a little more particular. These are all the different method which are on the UI thread and they ’ re actually freezing up the UI thread while they execute. There ’ s also these things we call hot method which are basically any background method which is not freezing up the UI thread but it ’ s contributing to CPO usage more than 100 milliseconds.

Also check:

So, if I look at any of these initial methods like this on create method you can see we provide a outstanding amount of detail of what exactly occur when this on create method is ring. And from this we can see that there is some very specific high-level method calls that conduct up a lot of time and then down here we can appear at the details all the way to the very bottom of the cry mess. And again, we ’ re providing this timing information so that developers can use this to actually improve performance.

Is it potential to take this method off of the UI ribbon and move it to a background method?

If yes, then you can speed up your name Startup clip by doing that. You can also look at the timeline view which shows all the different thread on the order in which they launch and for each one you can actually again pull up the methods that are accomplish by each thread to get some detail on you cognise for example what ’ s going on hither. So, by using this timeline view or by using the full call batch pairs are capable to recognise what is making the app slow down and assorted plan then and perhaps rectify the situation

Nathan:Thanks Ilya.

We besides took a aspect at the theme parks app usingHeadSpin execution session. This enable us to take a look at the node waiter relationship of the application during this test session and HeadSpin AI-based issue espial engine will automatically flag any anomaly and issues that get happened during the session.

This is what happened during the like application for Android.

As you can see here, we hold a waterfall the sight of what happened during this coating. And as I scroll through this, we can see the exact UI State of the application at any give moment time thither this test session.

From hither we can take a look at issues such as areas of low page content. These are areas of small to no clickable elements on the blind. And as you can see here on cold offset it took 7.32 seconds for the application to launching.

And here we can see the black screen.

Likewise, we can see an incomplete UI province from occupy a look at this you can also appear at errors that are happening. For example, HTTP fault. And if we tick on this info, we can see failed API minutes that occurred.

In alike fashion, we can let the AI based topic detection engine steer us through any of the subject during the session and it help us pinpoint the needle in the haystack with esteem to offending API cry and help us perfect in on for example dim host telephone as good as also slow downloads such as this download that impact the client by over 1 bit and 30 seconds.

What ’ s very powerful about this is that in addition to detecting matter we can take a look at the requests and response headers to dig deeper…deeply inspect what ’ s happening in a afford session.

In addition to our we also have a burst UI for taking a look at this data the burst UI helps us answer the question of given the fact there are numerous issues where I start first. The idea hither is that you can visually see what is the area of greatest impact of your application and when you click on it will show the same issues that we saw earlier as bubbles on an impact curve to allow you to see the peaks and vale of your covering client waiter performance. These are the same matter that we saw earlier in the waterfall view but now presented in a card formatting and they ’ re already sorted for me. So for example the first card will represent the area of sterling wallop. This was a slow download that we saw early that was conduct one minute and over one and 30 seconds typically to complete. I can see the composition of this dealings. I can see for example that the majority of it was time that the client spent download the data.

And this concludes the review of the falls and burst UI

FAQs

1. What is performance examination, and its significance?

is testing an app ’ s performance metrics like fastness, responsiveness, and dependableness under a high workload. Higher app performance conduct to better customer reviews, higher receipts, client satisfaction, and a positive encroachment on the marque image.

2. Is load testing the like as stress testing?

Load testing ensures that your application works as expected under expected usage conditions. On the early hand, a stress test, on the other mitt, is done to identify the breaking point of your application.

3. What are some common execution bottlenecks in mobile apps?

Some of the most common constriction in mobile applications are

• Memory usage
• Network speed
• CPU utilization
• OS Limitations

4. What are some common method to improve mobile app performance?

Some of the most mutual methods to are:

• Reduce the application size
• Optimize the retention and record usage
• Update the persona and screen sizing to optimal execution
• Test on lower-end phones and slow network hurrying
• Use AI to find latency points and eliminate them

4 Parts

Connet Now