<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[MoQuality - Medium]]></title>
        <description><![CDATA[Revolutionizing App Testing with Intelligent Tools - Medium]]></description>
        <link>https://medium.com/moquality?source=rss----61ee7ef44ea7---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>MoQuality - Medium</title>
            <link>https://medium.com/moquality?source=rss----61ee7ef44ea7---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 04:31:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/moquality" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Android 7 vs Android 8: Performance Testing]]></title>
            <link>https://medium.com/moquality/android-7-vs-android-8-performance-testing-a9df2a7cc234?source=rss----61ee7ef44ea7---4</link>
            <guid isPermaLink="false">https://medium.com/p/a9df2a7cc234</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[game-testing]]></category>
            <dc:creator><![CDATA[Pushkar Kolhe]]></dc:creator>
            <pubDate>Tue, 10 Oct 2017 17:44:42 GMT</pubDate>
            <atom:updated>2017-10-30T18:52:46.318Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s well known that mobile games are resource hungry apps. That’s why they become the best candidate for testing underlying system performance. Google has made lots of improvements in the Android 8 Run Time over Android 7, we decided to test it out with two popular games Flappy Bird and Super Mario.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F8I_BNw9uyuA%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D8I_BNw9uyuA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F8I_BNw9uyuA%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/fc87e3051cb00acbe6ef1f65f3dac626/href">https://medium.com/media/fc87e3051cb00acbe6ef1f65f3dac626/href</a></iframe><p>When it come to performance the main parameters to test against are fps, cpu and memory consumption. This is what we found:</p><p>From the graphs for FlappyBird we see that the CPU usage is around 18% and memory consumption is around 80 MB in Android 7. For a simple game like Flappy bird we can see comparable performance in Android 8. We tested it on a pre-release Android 8 when it showed jagged rendering.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*E9NiROWbe42DOESS." /><figcaption><strong>Flappy Bird on Google Pixel running Android 7</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JGthFxWzxhv_0YZD." /><figcaption><strong>Flappy Bird on Google Pixel running Android 8</strong></figcaption></figure><p>From the graphs for SuperMario we can see the same, the CPU and memory consumptions is almost similar. However the rendering profile is slightly smoother.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zcggplmGR5ak0I4L." /><figcaption><strong>Super Mario on Google Pixel running Android 7</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EuaFYU3GXm3KUpP1." /><figcaption><strong>Super Mario on Google Pixel running Android 8</strong></figcaption></figure><p>On the <a href="https://developer.android.com/about/versions/oreo/android-8.0.html">Android 8 improvements feature list</a>, Google doesn’t specifically mention any new improvements in their graphics rendering unit. However they do say that Android RunTime is a lot faster. Along with that Android 8.0 correctly identifies apps that are running background services and <em>are not</em> connected to what you’re doing on the phone. This probably helps games utilize all the resources it can.</p><p>We are working towards a more detailed analysis, which will give us more insights into potential differences. We will also run these tests on several games which utilize a lot of phone resources where we will be able to tell if Android 8 is actually better than Android 7 or not.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a9df2a7cc234" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moquality/android-7-vs-android-8-performance-testing-a9df2a7cc234">Android 7 vs Android 8: Performance Testing</a> was originally published in <a href="https://medium.com/moquality">MoQuality</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Testing Games on Android using Deep Reinforcement Learning]]></title>
            <link>https://medium.com/moquality/testing-games-on-android-18c1f040a94a?source=rss----61ee7ef44ea7---4</link>
            <guid isPermaLink="false">https://medium.com/p/18c1f040a94a</guid>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[deep-learning]]></category>
            <category><![CDATA[game-testing]]></category>
            <dc:creator><![CDATA[Pushkar Kolhe]]></dc:creator>
            <pubDate>Wed, 26 Apr 2017 17:59:14 GMT</pubDate>
            <atom:updated>2017-04-27T03:27:02.329Z</atom:updated>
            <content:encoded><![CDATA[<p>DeepMind was able to show that deep learning networks can be effectively used to train agents to play games. This is significant because the input their learner takes in is the game screen and a set of controls the agent can perform. In previous work in this area, researchers had to hand extract features which helped the AI agent learn the game. With deep learning that process is automated in the deep learning network. The network learns important features and learns policies that lead to a good score.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FZpCjxRXjy3_XRIkhppcPA.png" /><figcaption>Score detection on a Game Screen</figcaption></figure><p>There are four main parts of any Reinforcement Learning (RL) algorithm — states, actions, transition function and the reward function. When you use the game screen as input the state space of the problem is really big. A standard RL approach do not scale particularly well with the size of the state space and often require extensive engineering on the part of the designer to minimize the search space. To alleviate this problem, we use use human demonstrations to guide the exploration of the bot. How this RL algorithm works is a part of another series of article.</p><p>In this series I will cover the first part of building a system towards automating game testing — reading scores from the game.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FHbD29mvsDkk%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DHbD29mvsDkk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FHbD29mvsDkk%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/94db27800c5a8eb305de55df58ae5ec2/href">https://medium.com/media/94db27800c5a8eb305de55df58ae5ec2/href</a></iframe><p>The score of the game is the reward to the RL agent. The higher the score, the better the AI agent is playing the game. In DeepMind’s ATARI games, or for that matter, other game interfaces we can directly query the game for the score. However this is not possible when a game is being played on Android.</p><p>OpenAI solved this problem in it’s <a href="https://universe.openai.com/">Universe</a> by developing an OCR for reading score of games. In their scenario games were running inside a docker container. They get an image of the game inside the docker and process it for finding a score. Similarly, we can stream a video from any Android device and recognize the score in real time. Our OCR detection algorithm is a supervised learning classification algorithm that has a classification rate of almost 98% and can classify the score at 70fps.</p><p>This allows us to feed the score to a reinforcement learning algorithm that is running in parallel and learning to play the game. This reinforcement learning algorithm learns how to play a game, in this case, flappy bird. When the agent has learnt the game sufficiently we can run the agent across multiple phones and carry out stress testing and performance testing.</p><p>Recent advances in Deep Reinforcement Learning has made it possible to automate game testing. And we are on it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18c1f040a94a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moquality/testing-games-on-android-18c1f040a94a">Testing Games on Android using Deep Reinforcement Learning</a> was originally published in <a href="https://medium.com/moquality">MoQuality</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On Using Robots for App Testing]]></title>
            <link>https://medium.com/moquality/on-using-robots-for-app-testing-88633c3c919f?source=rss----61ee7ef44ea7---4</link>
            <guid isPermaLink="false">https://medium.com/p/88633c3c919f</guid>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[testing-tools]]></category>
            <category><![CDATA[android-testing]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Shauvik Roy Choudhary, Ph.D]]></dc:creator>
            <pubDate>Wed, 26 Apr 2017 05:48:09 GMT</pubDate>
            <atom:updated>2017-04-28T01:14:16.316Z</atom:updated>
            <content:encoded><![CDATA[<p>I gave a talk at GTAC 2015 on using robots for Android App Testing. The talk got a lot of interest and I presented on the same topic at AndroidSummit, Connect.TECH and several meetups to share my ideas with developers and get feedback on their thoughts. Most of my audience were fascinated by the idea of having a robot test your app for increasing coverage and identifying all failures (crashes) in the application.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FVt8EUQtqBuA%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DVt8EUQtqBuA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FVt8EUQtqBuA%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/9e87199f3b93e610e818e4198f5de8b8/href">https://medium.com/media/9e87199f3b93e610e818e4198f5de8b8/href</a></iframe><p>We’ve come a long way since the talk. After 3 years of research and customer discovery with developers, these two reasons come to the top on why one should use robots for app testing.</p><ol><li><strong>Scale &amp; Agility:</strong> Manually approving each release across all the devices, takes a lot of time and requires a lot of skilled people to get right.</li><li><strong>Better Error Detection:</strong> Without strong rigor, it is easy to miss a lot of customer facing errors, mostly in the regression and compatibility areas.</li></ol><p>A test framework must work towards a better customer experience by making sure that the apps have the highest app quality. It seemed that Artificial Intelligence was the most obvious way to proceed with this problem.</p><p>The AI we are building is not replacing human testing, but supplementing it. We have created sophisticated reinforcement learning algorithms that can better <strong>explore</strong> an app <em>like a human</em> and then <strong>classify</strong> bugs using deep learning algorithms.</p><p>One common rant we heard from our initial users was that the way users use their app is very different than how the current set of automated tools out there test apps. We are trying to bridge this gap by having the robot observe app users from varied sources to understand usage patterns and train our algorithms to make the robots mimic the general human behavior.</p><p>One straight-forward way to help the robot is to provide it recorded test cases using the <a href="https://play.google.com/store/apps/details?id=com.moquality.barista&amp;hl=en">Barista App</a>. Through trial and error, the robot biases the exploration of the reinforcement learning algorithm to learn the user flow encoded in this test case. Then it prioritizes the algorithm for this flow, thereby mimicking the human behavior in this flow while also explore the adjacent flows in your app.</p><p>Once the robot has explored the application, it needs to communicate back and tell it’s story. How does it do that? What worked, what didn’t work, what errors did the robot encounter while using the application? The answer can be found by visualizing the robot’s internal model, we call the <strong>AppMap. </strong>It’s just like a <a href="https://en.wikipedia.org/wiki/Site_map">Site map</a> except the screens are app screens instead of webpages, which are linked by actions (e.g., tap, scroll, swipe etc.) instead of web links.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/871/1*lKoqF70g9S0XvQq6VWbk_A.png" /><figcaption>The robot sees the application as a model of screens and interactions that is can have with the application to transition between them.</figcaption></figure><p>This is the future of testing — a visual approach to help developers make their app more stable quickly, so that they can release it fast.</p><p>We are testing apps for our beta users. If you would like to have your app tested, reach out to us at <a href="/service/mailto:support@moquality.com">support@moquality.com</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88633c3c919f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moquality/on-using-robots-for-app-testing-88633c3c919f">On Using Robots for App Testing</a> was originally published in <a href="https://medium.com/moquality">MoQuality</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>