<?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[Stories by Yukti Srivastava on Medium]]></title>
        <description><![CDATA[Stories by Yukti Srivastava on Medium]]></description>
        <link>https://medium.com/@yukti2512?source=rss-8613b6a6b6e6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*jDtyxJnDS8DImbduDLeQVg.jpeg</url>
            <title>Stories by Yukti Srivastava on Medium</title>
            <link>https://medium.com/@yukti2512?source=rss-8613b6a6b6e6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 22:07:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yukti2512/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How AI can help in Automation Testing]]></title>
            <link>https://medium.com/analytics-vidhya/how-ai-can-help-in-automation-testing-78f279f95703?source=rss-8613b6a6b6e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/78f279f95703</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Yukti Srivastava]]></dc:creator>
            <pubDate>Wed, 21 Oct 2020 10:26:35 GMT</pubDate>
            <atom:updated>2020-10-25T16:38:47.066Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/626/1*977SmGNpxFjTAYe0Jp7KHQ.jpeg" /></figure><p>Every gadget around us is now controlled by a mobile app. Be it television, refrigerator, virtual reality sets, home automation, or any other appliance. To give users the best experience, Software companies around the world are using the best delivery practices to release software updates every week. Some of the updates are generally bug fixes to ensure smooth working of the product. But there are a couple of challenges in testing which might block frequent releases:-</p><ol><li>Using the traditional approach of Software testing using manual techniques.</li><li>Not having enough automation coverage.</li><li>Flaky Automation scripts.</li></ol><h4><strong>Solution</strong></h4><p>Having good automation coverage is always good, but if scripts are taking more time to execute and test coverage is mostly of low priority scenarios then it is not a 100% solution to ensure timely releases. With AI being the latest buzzword in the market, let’s look into what it offers to Software Testing:-</p><h4><strong>Improved Automation Stability</strong></h4><p>The common challenge in Test automation is to maintain its stability. It is impacted by many factors, like synchronization issues, locator change, environmental changes. Automation relies on locating the element and then performing actions on it. If your DOM remains static <em>(only in the ideal world)</em>, then you’ll not face the locator issue, but in reality, it keeps on changing with new implementations, causing automation scripts to fail. The solution is to train AI to <strong>logically locate</strong> the elements in the script and perform the action. This way we don’t have to rely on static implementations.</p><h4><strong>Test data generation</strong></h4><p>Al can help testing teams to generate the test data without having to manually create it. Manually creating test data is a time-consuming process and may not be accurate due to human errors. There are many ML techniques that can be used to prepare test data, like:</p><p>Image analysis</p><p>Text analysis</p><p>Sentiment analysis</p><p>Data analysis</p><p>Data Filtering</p><p>Predictions</p><h4><strong>Pattern Analysis</strong></h4><p>AI/ML can be used to study patterns based on demographics. e.g. if a release is in a particular region, we can generate relevant test data using pattern analysis and develop test suites. We can also generate data based on devices used. The data generated give SDETs an insight into what areas of testing need to be fixed, hence spending less time running the actual tests and speeding up the development cycle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/779/1*iFBHEcF5OVXq7RbdqIsNuA.png" /></figure><h4><strong>Unit Testing</strong></h4><p>One advantage of unit testing is that it doesn’t interact with other components of the application. We can test a module independently using unit testing by creating stubs or drivers. AI can help the automation team to find the code modules which are not covered by unit tests. It can also provide the input for the uncovered modules. In the future, AI will be able to update these unit tests as soon as the source code changes, this will increase the stability. The current constraint is to train AI to isolate modules and create drivers for them.</p><h4><strong>API Testing</strong></h4><p>AI can be trained on different API calls used in the system and then it can do analysis &amp; automatically develop all combinations of API calls with multiple parameters. With time, the suite will become smarter and smarter.</p><h3><strong>AI-Based tools for Automation testers</strong></h3><h4>Testim</h4><p>This is an AI-based <a href="https://www.testim.io/test-automation-tool/">tool</a> that uses Smart Locators to evaluate hundreds of attributes and score them so that if elements change, the tests don’t break. They also provide tester <a href="https://www.testim.io/blog/testim-ai-certification-build-your-testing-skills/">certification</a>.</p><h4><strong>TestCraft</strong></h4><p>It is an AI-powered test automation platform for regression and continuous testing that works on top of Selenium. It is also used for monitoring web applications. The best thing about TestCraft is that testers can visually create automated, Selenium-based tests using a drag and drop interface, and run them on multiple browsers and work environments, simultaneously. No coding skills required.</p><h4>Applitools</h4><p>Applitools is an application visual management and AI-powered visual UI testing and monitoring software. It provides an end-to-end software testing platform powered by Visual AI and can be used by professionals in engineering, test automation, manual QA, DevOps, and Digital Transformation teams. Also, the AI and machine learning algorithm are entirely adaptive — it scans the apps’ screens and analyze them like the human eye and brain, but with the power of a machine.</p><h4>Functionize</h4><p>Functionize is a cloud-based automated testing technology that is used for functional, performance, and load testing. This tool uses machine learning and artificial intelligence to speed up test creation, diagnosis, and maintenance. All you have to do is type what you want to test in plain English and <strong>NLP</strong> creates functional test cases. It also executes thousands of tests in minutes from all desktop and mobile browsers.</p><h4>Sauce Labs</h4><p>Sauce Labs support a comprehensive list of browsers and operating systems, mobile emulators and simulators, and mobile devices, and at the speed that its users need to test their apps. It offers over 800 browser and operating system combinations, 200 mobile emulators and simulators, and thousands of real devices.</p><h4>Autify</h4><p>Autify is an AI-powered test automation platform that allows recording test scenarios without writing code. Once recorded, AI maintains your script. With each Agile release cycle, Autify identifies the changes in your code and automatically updates test scenarios accordingly.</p><h3>Conclusion</h3><p>Although AI/ML is helping testers to write scripts with less or zero maintenance &amp; helping companies to release faster, it is still an initial phase and is evolving.</p><p>The time reduced in script maintenance can be utilized to keep automation coverage above 90%. Having said that, it is not a replacement for manual testing teams. We still have to train AI a lot to make it more useful for us.</p><p><em>Thanks for reading, if you enjoyed it, hit the applause button below, it would mean a lot to me and it would help others to see the story. Let me know what you think by reaching out on </em><a href="https://www.linkedin.com/in/yuktisrivastava"><em>Linkedin</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78f279f95703" width="1" height="1" alt=""><hr><p><a href="https://medium.com/analytics-vidhya/how-ai-can-help-in-automation-testing-78f279f95703">How AI can help in Automation Testing</a> was originally published in <a href="https://medium.com/analytics-vidhya">Analytics Vidhya</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to test a game?]]></title>
            <link>https://medium.com/@yukti2512/how-to-test-a-game-b0acee48937d?source=rss-8613b6a6b6e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/b0acee48937d</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[games]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Yukti Srivastava]]></dc:creator>
            <pubDate>Thu, 16 May 2019 14:44:27 GMT</pubDate>
            <atom:updated>2019-05-16T14:44:27.798Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/734/1*pRUfboKfL5bm6PsN9NnG5A.png" /></figure><p>We all love games!! Be it Snake on Nokia 2200 or PubG on OnePlus.</p><p>To make the game interesting and fast, all gaming companies invest a lot in QA and performance testing. As Multiplayer gaming is the new trend in industry, the game testing has become more complex.</p><p>Below are the common bugs that we notice in games:</p><p><strong>Hang/Crash : </strong>When game crashes with “App not responding” error, it suddenly freezes. This is a Priority 1 issue.</p><p><strong>Collisions</strong>: When 3D objects are not as per physics.</p><p><strong>Movement</strong>: When the player movements are not proper.</p><p><strong>Graphics</strong>: Incorrect textures, patterns, colors</p><p><strong>Sound</strong>: Synchronization issues, volume and looping problems</p><p><strong>Play defects: </strong>Functionality is not working as per the requirement</p><h3>Below are the techniques for finding the bugs in a game</h3><p><strong>Exploratory testing: </strong>This is interesting as here you just have to play the game with an intent to discover bugs. Ask everyone in your team to just play the game.</p><p><strong>Break the rules:</strong> Go beyond the scope of test cases to find potential vulnerability or defect and choose different ways to achieve the same result</p><p><strong>Use unconventional method: </strong>Play game in a wrong order or incorrectly, such as not doing any actions, skipping some steps and observe the changes that happen.</p><p><strong>Use all functions everywhere: </strong>Try to use all functions even at every stage even if it is not of any use at that point.</p><p><strong>Try things that are not allowed: </strong>Press buttons rapidly at different places. Before finishing level retrace steps and check the result</p><p><strong>Examine Effects: </strong>Try playing games with minimum inputs or minimum user actions. Similarly, try playing games with maximum inputs. Try to walk through walls, obstructions or objects and examine the effects</p><p><strong>Test cases: </strong>Production or development team suggests testers the specific areas of a game that needs to be tested. Testers follow test cases given by the development team and complete each action as per given directions.</p><p><strong>Functionality testing:</strong> Test menu and every menu function, and assure that it is working correctly.</p><p><strong>Durability testing:</strong> Test for odd situations like load game without a memory card, run the game for 48 hours and check how game respond</p><p><strong>Appoint different testers for the same job:</strong> If a same tester is performing test cases over and over for every new build, then the person may lose enthusiasm and focus. This can lead to missed defects or bugs. New testers will start work with a new point of view and can find new bugs if any. Always rotate testers to get best results.</p><p><strong>Performance Testing:</strong>A game with incredible graphics and features may still fail to satisfy a player if the game is too slow or freeze up at certain levels. The critical success factor of a game is its underlying development and testing. For this, run a game without pause or keep on increasing the number of players if it is a multi-player game.</p><p>Thanks a lot for reading the article. Give a ❤ if you liked it :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0acee48937d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[All about Android App Performance]]></title>
            <link>https://medium.com/mindorks/performance-testing-of-mobile-apps-4453dcfaa2a9?source=rss-8613b6a6b6e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/4453dcfaa2a9</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[performance]]></category>
            <dc:creator><![CDATA[Yukti Srivastava]]></dc:creator>
            <pubDate>Thu, 20 Sep 2018 08:58:54 GMT</pubDate>
            <atom:updated>2018-09-21T07:39:09.829Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*0P1YMyK3Eu3s3UwqIMjuAw.png" /></figure><p>One of the important metrics for measuring the quality of an app is its Performance. An app’s performance and stability are directly proportional to its success and revenue.</p><p>Here is a snapshot of what performance testing can monitor:-</p><ul><li>RAM usage by the app</li><li>How app is behaving in Network change condition, connectivity issues</li><li>Is app crashing with more number of simultaneous users</li><li>How app is working with other installed apps</li><li>Splash time of app</li><li>Packet loss, if any</li></ul><p>A slow app leads to loss of user interest and ultimately its uninstall. Here are some metrics that need our attention:</p><p><strong>App Start-Up time: </strong>How much time your app takes to start up after the user taps on app icon the first screen should be shown in <strong>1–2 seconds</strong>.</p><p><strong>Battery: </strong>Your app should not consume memory in background and it should not heat up the device. Use battery historian to track the battery usage.</p><p><strong>Memory: </strong>Check memory usage of your app using android monitor. Find out the screen, module which is taking more memory. Use animations carefully.</p><p><strong>Interference: </strong>When the app is running in parallel with other apps, there should be no interference. The best way to check it is by switching app under testing and other apps.</p><p><strong>Background scenario: </strong>An app that is running in the background is retrieved, it should remain in the same state as it was before. If this scenario is not handled properly, then data get lost.</p><p><strong>Data to and from server: </strong>In certain apps, data is sent in a specified format. So before displaying it in the app, it should be converted to a relevant format. In this process, apps sometimes become slower and response time becomes longer.</p><p><strong>API Calls: </strong>The number of calls from App under test to the server generated from app should be less. In some cases, multiple API calls are made for the same functionality. For better performance, this should be handled with less number of calls.</p><p><strong>Server Down Time: </strong>Whenever the server is down, we can show data stored in the native database. Another solution could be the failover database servers i.e. if one of the servers is down or in maintenance phase the backup server should be available to switch over. The failover/backup server should be in continuous replication and synchronization with the main server.</p><p><em>For Network performance, you will check following things.</em></p><p><strong>Jitters: </strong>When there is a delay in receiving information on the network, then it is termed as jitters. It is a problem with the connectionless networks or packet switch networks.</p><p><strong>Packet Loss: </strong>In the case of complete packet loss, the app should be able to resend the request for the information or should generate the alerts accordingly.</p><p><strong>Network Speed: </strong>The app should be tested on 2.5G, 3G, and 4G networks. Both Wi-Fi and mobile networks are included in this.</p><p><strong>Caching</strong>: Downloading of external resources can be time-consuming, so pay special attention to cache your images.</p><p><strong>HTTP Requests: </strong>Prefer going for fewer HTTP requests, needed to acquire resources for each page, so as to reduce the complexity for your Android app.</p><p><strong>Templates: </strong>In order to increase the speed of the Android app, load only limited templates just by reusing them.</p><p><strong>Loading: </strong>Adding something during the loading process will give the users an illusion that it is loading rapidly.</p><p><strong>Data: </strong>If your Android app is supported well only with the help of massive data, then that is when you should go ahead to load it. Don’t keep the user waiting for a longer time than that is needed by looking into the parts of the app. Dividing the assemblies will make the target easier to accomplish. There is also another option in which you can pre-load or prefetch the data so that the user is not kept waiting for long at the time of requirement of data.</p><p><strong>Offline Mode: </strong>At the time of network problem, while the user is amidst the process of completing an action, it is best to prompt them as to why the action has failed in between.</p><p><strong>Smooth Scrolling: </strong>If you want your Android apps to score on the lines of scrolling, prefer using UI thread for UI only. This will be great to handle 99% of your problems. Don’t load images, parse JSON, access databases and work on networking calls on UI thread. If you want quick solutions, go for libraries in case of images, JSON, and networking. In case of database access, use Loader that is very effective to do batch updates to databases and thus, shift your focus on the important stuff in the app.</p><h3>Tools</h3><ol><li><strong>Monkop</strong>: There are various tools available in the market to conduct mobile performance tests, but an excellent tool amongst the lot is Monkop because of its simple function used in testing of Android apps. First, you have to upload your .apk and then if you want, test data and scripts.</li></ol><p>2. Robotium</p><p><strong><em>For iOS: </em></strong>Automator (Mac)</p><p><em>Thanks for reading :-) , if you enjoyed it, hit the applause button below, it would mean a lot to me and it would help others to see the story. Let me know what you think by reaching out on </em><a href="https://www.linkedin.com/in/yuktisrivastava"><em>Linkedin</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4453dcfaa2a9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mindorks/performance-testing-of-mobile-apps-4453dcfaa2a9">All about Android App Performance</a> was originally published in <a href="https://medium.com/mindorks">MindOrks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Selenium: Cheat codes and Tips]]></title>
            <link>https://medium.com/@yukti2512/selenium-cheat-codes-and-tips-a56d6296611a?source=rss-8613b6a6b6e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/a56d6296611a</guid>
            <category><![CDATA[selenium]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[qa]]></category>
            <dc:creator><![CDATA[Yukti Srivastava]]></dc:creator>
            <pubDate>Thu, 16 Aug 2018 06:31:08 GMT</pubDate>
            <atom:updated>2018-08-16T06:31:44.772Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*91SH24Zw9CkR0si3R21UJw.png" /></figure><p>In this story I’ve consolidated all the important shortcuts &amp; tips from the web for writing better and optimized code.</p><h4>Tip-1: Best Method To Create Webdriver Instance.</h4><p>It’s one of the most common Selenium Webdriver coding tips which you can’t avoid to use.</p><p><strong>1.1-</strong> Use the <strong>&lt;Factory&gt;</strong> design pattern to create objects based on browser type.</p><p><strong>1.2-</strong> Extend the below code or use it as is in your projects.</p><pre>public class DriverFactory {<br>    private WebDriver driver = null;</pre><pre>    public static WebDriver getBrowser(String browserType) {<br>        if (driver == null) {<br>            if (browserType.equals(&quot;Firefox&quot;))</pre><pre>            {<br>                driver = new FirefoxDriver();</pre><pre>            } else if (browserType.equals(&quot;Chrome&quot;))</pre><pre>            {<br>                driver = new ChromeDriver();</pre><pre>            } else if (browserType.equals(&quot;IE&quot;))</pre><pre>            {<br>                driver = new InternetExplorerDriver();</pre><pre>            }<br>        }<br>        return driver;<br>    }<br>}</pre><h4>Tip-2: Simple Method To Check If An Element Exists.</h4><p><strong>2.1-</strong> You should use <strong><em>&lt;findElements&gt;</em></strong> instead of <strong><em>&lt;findElement&gt;</em></strong>.</p><p><strong>2.2-</strong> <strong><em>&lt;findElements&gt;</em></strong> returns an empty list when it doesn’t find any matching elements.</p><p><strong>2.3-</strong> You can use the code given below to check for the presence of an element.</p><pre>Boolean isItemPresent = driver.findElements(By.testLocator).size() &gt; 0</pre><h4>Tip-3: Avoid Exception While Checking An Element Exists.</h4><p><strong>3.1-</strong> The code in the previous tip may lead to <strong><em>&lt;NoSuchElementException&gt;</em></strong>. Also, it could be a bit slower in some cases.</p><p><strong>3.2-</strong> Webdriver has a Fluent wait feature. We can use it to check the element.</p><p><strong>3.3-</strong> It gives the ability to ignore any exception and allows to test the <strong><em>&lt;WebElement&gt;</em></strong>. Let’s see how to achieve what’s said here.</p><pre>/* 1- Test if an element exists on the page.<br>   2- Ignore the no element found exception.<br> */<br>By element = By.xpath(&quot;.//*[@id=&#39;demo&#39;]/p&quot;);<br>Wait &lt; WebDriver &gt; wait = new FluentWait &lt; &gt; (driver)<br>    .withTimeout(60, TimeUnit.SECONDS)<br>    .pollingEvery(5, TimeUnit.SECONDS)<br>    .ignoring(NoSuchElementException.class);<br>wait.until(ExpectedConditions<br>    .presenceOfElementLocated(element));</pre><h4>Tip-4: Wait For A Page With JavaScript(JS) To Load.</h4><p><strong>4.1-</strong> It’s quite common working with pages bloated with JavaScript. The challenge is how to make sure the page has finished loading.</p><p><strong>4.2-</strong> Here, we are giving a solution that works. This code will help you setting wait for a page containing JavaScript.</p><pre>wait.until(new Predicate &lt; WebDriver &gt; () {<br>    @Override<br>    public Boolean apply(WebDriver driver) {<br>        return ((JavascriptExecutor) driver).executeScript(&quot;return document.readyState&quot;).equals(&quot;complete&quot;);<br>    }<br>});</pre><h4>Tip-5: Take A Screenshot Using Webdriver.</h4><p><strong>5.1-</strong> It’s easy to capture a screenshot of any error using Webdriver.</p><p><strong>5.2-</strong> Use the below Webdriver code. It saves the screenshot to the current project directory.</p><pre>WebDriver driver = new FirefoxDriver();<br>driver.get(&quot;//www.google.com/&quot;);</pre><pre>// Store the screenshot in current project dir.<br>String screenShot = System.getProperty(&quot;user.dir&quot;) + &quot;\\screenShot.png&quot;;</pre><pre>// Call Webdriver to click the screenshot.<br>File scrFile = ((TakesScreenshot) driver).getScreenshotAs(OutputType.FILE);</pre><pre>// Save the screenshot.<br>FileUtils.copyFile(scrFile, new File(screenShot));</pre><h4>Tip-6: Take A Partial Screenshot Using Selenium Webdriver.</h4><p>It’s one of the premium Selenium Webdriver coding tips.</p><p><strong>6.1-</strong> Sometimes you only need to take a screenshot of the part of the screen. Like of only one frame within a set of frames.</p><p><strong>6.2-</strong> You can add below code in your project to shot the image of a particular frame.</p><p><strong>6.3-</strong> Find the <strong><em>&lt;WebElement&gt;</em></strong> of the frame and pass it to the function given below.</p><pre>public void takePartialScreenShot(WebElement element) throws IOException {</pre><pre>    String screenShot = System.getProperty(&quot;user.dir&quot;) + &quot;\\screenShot.png&quot;;</pre><pre>    File screen = ((TakesScreenshot) this.driver).getScreenshotAs(OutputType.FILE);</pre><pre>    Point p = element.getLocation();</pre><pre>    int width = element.getSize().getWidth();<br>    int height = element.getSize().getHeight();</pre><pre>    BufferedImage img = ImageIO.read(screen);</pre><pre>    BufferedImage dest = img.getSubimage(p.getX(), p.getY(), width,<br>        height);</pre><pre>    ImageIO.write(dest, &quot;png&quot;, screen);</pre><pre>    FileUtils.copyFile(screen, new File(screenShot));<br>}</pre><p><strong>6.4-</strong> You may require adding a few imports to get the above code working.</p><pre>import org.openqa.selenium.Point;<br>import org.openqa.selenium.TakesScreenshot;<br>import java.awt.image.BufferedImage;<br>import javax.imageio.ImageIO;</pre><p><strong>6.5-</strong> Alternatively, you can use the <strong><em>&lt;CTRL+SHIFT+O&gt;</em></strong> shortcut in Eclipse.</p><h4>Tip-7: Get HTML Source Of WebElement In Selenium WebDriver.</h4><p><strong>7.1-</strong> Webdriver’s <strong><em>&lt;WebElement&gt;</em></strong> class provides <strong><em>&lt;getAttribute()&gt;</em></strong> method to get the HTML inside the element.</p><p><strong>7.2- </strong>You need to pass the <strong><em>&lt;innerHTML&gt;</em></strong> as attribute type in the above method. See the code below.</p><pre>String html = element.getAttribute(&quot;innerHTML&quot;);</pre><h4>Tip-8: How To Select/Get Drop Down Option In Selenium Webdriver.</h4><p>You can achieve this in the following two steps.</p><p><strong>8.1-</strong> Select an option based on the label.</p><pre>Select dropdown = new Select(driver.findElement(By.xpath(&quot;//drop_down_x_path&quot;)));<br>dropdown.deselectAll();<br>dropdown.selectByVisibleText(&quot;selectLabel&quot;);</pre><p><strong>8.2-</strong> Get the first selected value from the drop-down.</p><pre>WebElement option = dropdown.getFirstSelectedOption();</pre><h4>Tip-9: Refreshing Web Page By WebDriver During Tests.</h4><p><strong>9.1-</strong> The below code should refresh the web page.</p><pre>driver.navigate().refresh();</pre><h4>Tip-10: Run A JavaScript Code Using Selenium Webdriver.</h4><p><strong>10.1-</strong> When you are testing a website, you can’t skip using JavaScript.</p><p><strong>10.2-</strong> Webdriver provides support to call JavaScript.</p><p><strong>10.3-</strong> You just need to add the below lines in your project.</p><pre>JavascriptExecutor JS = (JavascriptExecutor) driver;<br>JS.executeScript(&quot;alert(&#39;hello world&#39;)&quot;);</pre><h4>Tip-11: Getting The Result Of Javascript Code In Webdriver.</h4><p><strong>11.1-</strong> It’s a bit tricky but easy. Use the <strong><em>&lt;return&gt;</em></strong> keyword in JavaScript to send back the result.</p><p><strong>11.2-</strong> Place the following code in your project.</p><pre>((JavascriptExecutor) driver).executeScript(&quot;return 10&quot;);</pre><h4>Tip-12: Perform Mouseover Function Using WebDriver In Java.</h4><p><strong>12.1-</strong> Sometimes you need to use a mouseover function with a drop-down menu.</p><p><strong>12.3-</strong> When you hover over the menu, it shows new options.</p><p><strong>12.5-</strong> Webdriver provides an &lt;Actions&gt; class to handle mouse events.</p><p><strong>12.4-</strong> We can achieve this by chaining all actions to simulate mouse hover.</p><pre>Actions action = new Actions(driver);<br>WebElement item = driver.findElement(By.xpath(&quot;html/body/div[5]/ul/li[5]/a&quot;));<br>action.moveToElement(item).moveToElement(driver.findElement(By.xpath(&quot;/write-expression-here&quot;))).click().build().perform();</pre><h4>Tip-13: Make Selenium WebDriver Click A Checkbox Which Is Not Currently Visible.</h4><p><strong>13.1-</strong> Sometimes you’ve to click checkboxes on a form. But you fall into problems when they get added dynamically.</p><p><strong>13.2-</strong> If you use Webdriver calls, then the following error occurs.</p><pre>&quot;Element is not currently visible and so may not be interacted with.&quot;</pre><p><strong>13.3-</strong> In such cases, we advise to use Webdriver’s JavaScript executor to do the job.</p><p><strong>13.4-</strong> Check out the below lines of code.</p><pre>((JavascriptExecutor)driver).executeScript(&quot;arguments[0].checked = true;&quot;, checkbox);</pre><h4>Tip-14: Switch To A New Browser Window In Webdriver.</h4><p><strong>14.1-</strong> You can easily switch between popup windows.</p><p><strong>14.2-</strong> Copy the below code in your project to switch windows.</p><pre>// Get the current window handle.<br>String hBefore = driver.getWindowHandle();</pre><pre>// Click to open new windows.</pre><pre>// Switch to new windows.<br>for(String hNew: driver.getWindowHandles()){<br>    driver.switchTo().window(hNew);<br>}</pre><pre>// Close all new windows.<br>driver.close();</pre><pre>// Switch back to first window.<br>driver.switchTo().window(hBefore);</pre><pre>// Resume your work.</pre><h4>Tip-15: Setting The Driver Executable Path In Webdriver.</h4><p><strong>15.1-</strong> For some browsers, Webdriver needs to know the locations of their driver files. e.g. Chrome, and IE.</p><p><strong>15.2-</strong> We need to set the driver file path in the Webdriver configuration.</p><p><strong>15.3-</strong> See the code snippet given below.</p><pre>File ieDriver = new File(&quot;path/to/iexploredriver.exe&quot;);<br>System.setProperty(&quot;webdriver.ie.driver&quot;, ieDriver.getAbsolutePath());<br>WebDriver driver = new InternetExplorerDriver();</pre><h4>Tip-16: Find Element Using CSS In Webdriver.</h4><p><strong>16.1-</strong> While working with list items, you may find it interesting to use CSS for locating elements.</p><p><strong>16.2-</strong> <strong>Use case:</strong> You’ve to find the third element from a list. The element is an anchor text and uses <strong><em>&lt;css1&gt; and &lt;css2&gt;</em></strong> classes for styling.</p><p><strong>16.3-</strong> Implement with <strong><em>&lt;By.CssSelector&gt;</em></strong>.</p><pre>IList&lt;IWebElement&gt; list = driver.FindElements(By.CssSelector(&quot;.css1.css2&quot;));<br>IWebElement target = list[3];</pre><p><strong>16.4-</strong> Implement with <strong><em>&lt;By.XPath&gt;</em></strong>.</p><pre>driver.FindElement(By.XPath(&quot;(//a[contains(@class, &#39;css1 css2&#39;)])[3]&quot;));</pre><h4>Tip-17: Open A New Tab Using Selenium WebDriver In Java.</h4><p><strong>17.1- </strong>At times you may need to open a new tab in the same browser window. It’s easy to do it, use the following code.</p><pre>driver.findElement(By.cssSelector(&quot;body&quot;)).sendKeys(Keys.CONTROL +&quot;t&quot;);</pre><p><strong>17.2-</strong> If you wish to run your tests in the new tab, then you’ve to switch to it first. Check out the given code fragment.</p><pre>ArrayList&lt;String&gt; tablist = new ArrayList&lt;String&gt; (driver.getWindowHandles());</pre><pre>driver.switchTo().window(tablist.get(0));</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a56d6296611a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top Open source tools for Test Management]]></title>
            <link>https://medium.com/@yukti2512/top-open-source-tools-for-test-management-c9fdc4db9a37?source=rss-8613b6a6b6e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/c9fdc4db9a37</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Yukti Srivastava]]></dc:creator>
            <pubDate>Thu, 14 Jun 2018 04:52:22 GMT</pubDate>
            <atom:updated>2018-08-16T06:33:30.043Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/430/1*rFH6rep_-ydoYWadSc6meg.png" /></figure><p>Test management is the process of documenting, executing and tracking test cases and tests. Here is the list of top open source tools for test management:-</p><h3><a href="http://fitnesse.org/">FitNesse</a></h3><p>FitNesse is a software development collaboration tool. FitNesse enables customers, testers, and programmers to learn what their software should do, and to automatically compare that to what it actually does do. It compares customers’ expectations to actual results.</p><h3><a href="http://www.mozilla.org/projects/testopia/">Mozilla Testopia</a></h3><p>Testopia is a test case management extension for Bugzilla. It is designed to be a generic tool for tracking test cases, allowing for testing organizations to integrate bug reporting with their test case run results.</p><h3><a href="http://sourceforge.net/projects/qamanager/">qaManager</a></h3><p>qaManager is a platform independent web based application for managing QA projects with a very simple installation. qaManager comes with project tracking, resource management, test case management and more.</p><h3><a href="http://www.brominefoundation.org/">Bromine</a></h3><p>Bromine is an open source QA tool that uses selenium RC as its testing engine. The tests are created with the custom Selenium IDE format and uploaded to Bromine.</p><h3><a href="http://sourceforge.net/projects/qatraq/">QATraq</a></h3><p>QATraq is a tool that provides the framework for task management and control, across the whole test process. Control everything from defining test plans to writing test cases and recording results</p><h3><a href="http://sourceforge.net/projects/radi-testdir/">Radi</a></h3><p>Radi is a lightweight test management tool. Radi supports test directory features like configuring test plans, updating (create/edit) test results for the test images/builds, backup, user management and more.</p><h3><a href="http://sourceforge.net/projects/rth/">RTH</a></h3><p>RTH (requirements and testing hub) is an open source test management tool that also has requirements management and bug-tracking capabilities.</p><h3><a href="http://code.google.com/p/rth-turbo/">RTH-Turbo</a></h3><p>RTH Turbo is an optimized version of RTH, a testing management tool, that allows for requirement management, test case management, defect tracking, creating test plans and analyzing your test results.</p><h3><a href="http://wiki.ow2.org/salome-tmf/">Salome-TMF</a></h3><p>Salome-TMF is an independent Test Management Tool, which helps you to manage your entire testing process, including creating test scripts, executing tests, tracking results, produce documentation and more.</p><h3><a href="http://tesly.sourceforge.net/">Tesly</a></h3><p>Tesly is a web application written in PHP that helps you create, execute, and report on test plans. QA leaders can track the progress of testing as testers use the interface to report completion of test cases.</p><h3><a href="http://sourceforge.net/projects/tcw/">Test Case Web</a></h3><p>Test Case Web (TCW) is an online test case management (TCM) and test-tracking system built with PHP and a SQL backend.</p><h3><a href="http://www.majordojo.com/testitool/download.php">Testitool</a></h3><p>Test Run is the next generation of test planning software. Based upon Testitool it provides QA engineers with a state of the art test bench, and managers with the reports they need to bring visibility into their teams work.</p><h3><a href="http://sourceforge.net/projects/testlink/">TestLink</a></h3><p>TestLink is a web-based test management tool. The application provides test specification, test plans and execution, reporting, requirements specification and collaborate with well-known bug trackers.</p><h3><a href="http://testmaster.sourceforge.net/">Testmaster</a></h3><p>Testmaster is a test case logging, reporting and test automation tool, much like the commercial product Test Director. Testmaster runs on Linux and utilizes Apache to serve web pages, postgresql as the database, antiword to convert MS docs and Perl as the development language.</p><h3><a href="http://tetworks.opengroup.org/Products/tet.htm">TET</a></h3><p>The Test Environment Toolkit (TET) is provided as an open source, unsupported, command-line product. It is widely used in many test applications including The Open Group’s UNIX Certification program and the Free Standards Group’s LSB Certification program.</p><h3><a href="http://trac-hacks.org/wiki/TestCaseManagementPlugin">TracTest</a></h3><p>A test case management tool for trac that uses subversion as the test case repository and uses the ticket framework in trac to create test runs.</p><h3><a href="https://github.com/prove/tarantula">Tarantula</a></h3><p>Tarantula is an open source test management tool. The source code is hosted on GitHub for easier collaboration and it’s recommended to install Tarantula on CentOS by using it’s automated script installer.</p><h3><a href="http://webtst.sourceforge.net/">WebTst</a></h3><p>WebTst is an open-source test management tool aimed at creating and managing user-centric testing. WebTst is a tool written in Perl and dependent on Apache.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c9fdc4db9a37" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What should you really measure Code Quality against?]]></title>
            <link>https://medium.com/@yukti2512/what-should-you-really-measure-code-quality-against-ef8c0c83b14c?source=rss-8613b6a6b6e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/ef8c0c83b14c</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[code]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[qa]]></category>
            <dc:creator><![CDATA[Yukti Srivastava]]></dc:creator>
            <pubDate>Wed, 06 Jun 2018 11:10:37 GMT</pubDate>
            <atom:updated>2018-06-06T11:13:30.470Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/535/1*B_HRjYFG2YlLRI2-sNHwTg.png" /></figure><p><em>Answer: Test coverage.</em></p><p>But how do you really measure test coverage?</p><p>Popular answer: number of lines of code executed by test cases.</p><p><strong>NO!</strong></p><p>Why? Because ensuring 100% coverage in terms of lines of code executed doesn’t really get you a quality product.</p><p>Then what does?</p><p><strong><em>Good Test Cases and Adequate test coverage.</em></strong></p><p>To achieve both, you need to look critically at your points of reference.</p><p><strong>Improving the ratio of Good Test Cases in your Test repository<br></strong>A good test case traces a requirement (positive and negative flows included) to fulfilment. All you have to do to ensure you mainly have good test cases, is to establish Requirements Traceability. In Agile projects, given you’re supposed to only focus on requirements intended for the next immediate release, achieving 100% test coverage by Requirements should be fairly straightforward if you use an elementary Traceability Matrix.<br>If you are only testing to requirements, you should only have good test cases in your repository.</p><p><strong>Adequate test coverage</strong><br>If you only write test cases that can trace back to a requirement, you’re effectively eliminating any redundant, unnecessary test cases. Now, if you turn that around, what you’d get is this: if you ensure 100% of your requirements are covered by test cases, then you have all the test cases you need. Then again, how do you ensure you have 100% accurate requirements? What if some requirements are incorrect, or missed? Well, as they say, “A high quality product built on bad requirements, is a poor quality product.” The focus then shifts to ensuring you have high quality user stories that cover all functional and non-functional requirements.</p><p>With Test-Driven Development, this is truly achievable. And if you are able to demo a working, almost-bug-free product every Sprint, and follow this up with mop-up Spikes to fix the remaining unseemly bugs, my experience suggests you’re in a good place to go to Release.</p><p><em>So, What Should Code Quality be really measured against?</em></p><p>Both requirements coverage and number of lines of code executed. I believe ensuring 100% requirements coverage is adequate. After all, with Agile, you’re supposed to only work on the high priority requirements for a release all the time, thereby reducing waste — of effort, time, money. Then again, humans aren’t perfect. Bad requirements could sneak into your scope. Good requirements could be missed. You may not discover this until late into your project. We can’t always guarantee 100% accuracy with requirements. It’s quite common to encounter projects where developers have written so many more lines of code than is necessary. Coding effort veers away from the requirements, and developers spend precious resource writing unnecessary lines of code. The golden rule is only write code necessary to deliver a requirement. Even then, there may be scenarios where 100% coverage may not be achievable or necessary. The goal, therefore shouldn’t ever be to achieve 100% code coverage. Although when combined with 100% requirements coverage, you should be able to find that code coverage by default hovers in the high 80s and even low to high 90s.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef8c0c83b14c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Usability Testing : “Pay attention to what users do, not what they say.”]]></title>
            <link>https://medium.com/mindorks/usability-testing-pay-attention-to-what-users-do-not-what-they-say-3b964f43190f?source=rss-8613b6a6b6e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b964f43190f</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Yukti Srivastava]]></dc:creator>
            <pubDate>Tue, 27 Mar 2018 11:15:41 GMT</pubDate>
            <atom:updated>2018-04-11T06:10:33.323Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/645/1*i-3pZXNVfulC6NO6fJU5fA.png" /></figure><p>There are many reasons why users uninstall apps. One of them is Usability. Your app might be crash or lag free but that won’t guarantee its success. Users uninstall apps because they don’t like using the app or they find it too difficult to use.</p><p>Apps fail because users don’t know</p><ul><li>Where to click next?</li><li>If it is link or a label?</li><li>Which Icon represents what?</li><li>Prompts, toasts, errors are not user friendly</li><li>How to exit a flow</li></ul><p>As Jakob Nielsen so perfectly worded it, you must <em>“pay attention to what users do, not what they say.”</em> Ever since mobile apps began, their creators have been trying to understand what exactly their users are doing. According to a survey about how customers react to <a href="https://info.dynatrace.com/rs/compuware/images/Mobile_App_Survey_Report.pdf"><strong>poor mobile app experiences</strong></a>. 48% reported they would be less likely to use the mobile app, 34% said they would switch to a competitor’s app, 31% would tell others about their poor experience, and another 31% said they would be less likely to purchase from the app company.</p><p>For ensuring the usability aspect of the app, we need to keep following things in mind:</p><ol><li>How tech savvy the users are</li><li>Their environment (Network coverage)</li><li>Their Age range</li><li>Devices they use</li><li>Their interests</li></ol><p>A lot of people confuse Usability testing with User testing. Well, here’s the difference:-</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/615/1*OrmTFNKUcf20CiwWqSLreA.png" /></figure><p>Some of the key characteristics of usability are:</p><h4>Simple Design</h4><p>The design should be simple catering to all user groups. The best example is:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/306/1*DakmPyhXzx8M_NxNJClRgw.png" /></figure><p>The interface should not confuse users where to click, what to do on this screen etc. The screen should be designed in a way that it is self explanatory. If your design needs tutorial or user manuals, then it is not good design.</p><p><em>Good design does not need tutorials.</em></p><h4>User Focused</h4><p>Usability depends on target audience. An app designed for 5–8 years kids is different from an app designed for banking professionals. While doing usability testing, we need to take account of the behavior and habits of the users.</p><p>We can conduct moderated and unmoderated UX testing with user groups to understand how they are using the apps.</p><p><em>But how many users are required to do usability study? Research ( Virzi, 1992 and Neilsen &amp; Landauer , 1993) indicates that </em><strong><em>5 users are enough to uncover 80% of usability problems</em></strong><em>.</em></p><p>A lot of tools are available in market to understand user behaviors. You can use heatmaps for basic understanding of app usage.</p><p><strong><em>Heatmaps </em></strong>: They tell where your users are actually clicking. How are they using the app. Are they clicking on dead ends? Is some flow undiscovered?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/196/1*rQ3_lOCeSeCZyWbkLDSaLQ.png" /></figure><h4>Tips for Usability testing</h4><ul><li>Verify the app usability before development. Do static testing on wire-frames and mocks</li><li>Check competitors’ app to understand target audience and the expected standards.</li><li>Go for A/B testing when you are unsure about which flow will work.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/573/1*gY7pOSotzSjxnVSOeTQZlg.png" /></figure><ul><li>Assign a single observer to each user while using group study. This helps observer to accurately note tester’s behavior.</li><li>Test all input methods for data entry: typing, voice, gestures, etc</li><li>Check playstore/appstore reviews to understand the design implementation and expectation gap.</li><li>If your app has good user-base, setup online forums and moderate them</li></ul><p>and, remember —</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*Yf6jCz-eKBhSGzBgfqshHA.gif" /></figure><h4>Thanks for reading :-) , if you enjoyed it, hit the applause button below, it would mean a lot to me and it would help others to see the story. Let me know what you think by reaching out on <a href="https://www.linkedin.com/in/yuktisrivastava">Linkedin</a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b964f43190f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mindorks/usability-testing-pay-attention-to-what-users-do-not-what-they-say-3b964f43190f">Usability Testing : “Pay attention to what users do, not what they say.”</a> was originally published in <a href="https://medium.com/mindorks">MindOrks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Risk Based Testing : When and How?]]></title>
            <link>https://medium.com/mindorks/risk-based-testing-when-and-how-df926fca531c?source=rss-8613b6a6b6e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/df926fca531c</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Yukti Srivastava]]></dc:creator>
            <pubDate>Mon, 22 Jan 2018 10:48:52 GMT</pubDate>
            <atom:updated>2018-01-22T13:59:55.847Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/559/1*DwHqcrztAiHw8FDsX0j_LQ.png" /></figure><p>In almost every project, development gets delayed which leads to squeeze in testing time to meet the release deadline. This means testing has to be done in limited time maintaining the same quality. Fortunately, Risk-Based Testing provides a way to de-scope tests in a logical manner and allows visibility of the risk coverage. RBT allows the stakeholders to make decisions based on QA’s assessment of risks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*KYDuEkTrsVN9uN-8yPuyqA.png" /></figure><p>Risk is the probability of occurrence of an uncertain event. It could be events that have occurred in the past or current events or something that could happen in the future. These uncertain events can have an impact on the cost, business, technical and quality targets of a project.</p><p><strong>Types of Risks</strong></p><p><strong>Level 5</strong>: System crash<strong>,</strong> loss of data (ex. leaving name field blank is crashing the app)</p><p><strong>Level 4</strong> : Boundary conditions (ex. App is not working fine when name has 20 characters)</p><p><strong>Level 3</strong> : Negative Testing scenarios (ex. App is not working fine when name has numbers or special characters)</p><p><strong>Level 2</strong> : Inconsistent behavior (ex. App hangs for 10 seconds on entering username, but the frequency of the bug is 1/50)</p><p><strong>Level 1</strong> — Spelling mistakes/UI issue</p><p>Chances of fixing the bugs just before the deadline is rare. If it is a Blocker Bug, the probability of occurrence would be &lt;1% , and it’ll be fixed. If it is a Medium or low priority bug, the probability would be &lt;5% and it won’t be fixed just 1 day before release.</p><h4>RBT — When to do it?</h4><ol><li>When QA team is out of time</li><li>The project is new and team does not have experience</li><li>When team is following Incremental and iterative models</li></ol><h4>RBT — How to do it?</h4><p>Here are some ways to do Risk based testing:</p><p><strong>Prioritization</strong></p><p>Testing is always a sample. It is impossible to test all the possible combinations. So, when time is limited, QA team needs to prioritize the test cases.</p><p><em>How to prioritize test cases?</em></p><ul><li>Which functions and attributes are critical</li><li>How often a feature is used</li><li>How visible the problem is to the end user</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*gEQ1-VpmG-8E8PiVfMKeFg.png" /><figcaption>You should make a risk calculation table like this, assigning weight to different metrics and then calculating the sum to access the risk</figcaption></figure><p>The formula to calculate the risk is: <strong>R(f) = P(f) * C(f)</strong></p><p><em>R(f) : Calculated risk of function f</em></p><p><em>P(f): Probability of fault in functin f</em></p><p><em>C(f): Cost related to a fault in function f</em></p><p><strong>Automation &amp; UT</strong></p><p>Another important thing that takes up most of the testing time is Regression testing. The solution is Automation. Automation saves lot of time and gives a clear view of product’s stability.</p><p><em>Unit Testing : Unit tests should be automated as well and rerun every time units are changed or integrated.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/544/1*HsKLMrRrdgfbggxkqUtemA.png" /><figcaption>Automation : The solution of Regression Testing</figcaption></figure><p><strong>Documentation : Yes/No?</strong></p><p>Proper documentation of test cases is often not needed. In agile approach, it can be avoided to save the time. Just brief summary or pointers are fine to execute test cases by any tester.</p><p><strong>QA Skills</strong></p><p>A lot of time can be saved if QA team has good experience &amp; skills. A good QA can write better test cases which have higher chances of finding bugs.</p><p><strong>Bug Resolution</strong></p><p>Another important question is which bug to fix when the deadline is near. Here are some industry guidelines to do that.</p><p><em>Rule 1: Fix only important defects.</em></p><p><em>Rule 2: Change requests and small defects should be moved to the next release.</em></p><p><em>Rule 3: Correct defects in groups, only after blocking failures are found.</em></p><p><em>Rule 4: Use an automated “smoke test” to test any corrections immediately.</em></p><h3>RBT Benefits</h3><p><em>For Management:</em></p><ol><li>To see progress in terms of risks addressed and benefits that are available for delivery</li><li>To manage the risks that block acceptance</li><li>To make the release decision.</li></ol><p><em>For Testers</em></p><ol><li>Approval to test against risks in scope</li><li>Clearer test objectives upon which to design tests</li></ol><p>Thank you so much for your time.Your comments and suggestions are welcome!</p><p>Happy Testing!!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*lnyZId19We1NJowiLfhFAg.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df926fca531c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mindorks/risk-based-testing-when-and-how-df926fca531c">Risk Based Testing : When and How?</a> was originally published in <a href="https://medium.com/mindorks">MindOrks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Things to check before integrating any third party SDK in your Android app]]></title>
            <link>https://medium.com/mindorks/things-to-check-before-integrating-any-third-party-sdk-in-your-android-app-4a338fc59e52?source=rss-8613b6a6b6e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a338fc59e52</guid>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[androiddev]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Yukti Srivastava]]></dc:creator>
            <pubDate>Mon, 15 Jan 2018 06:33:41 GMT</pubDate>
            <atom:updated>2018-01-15T06:59:46.331Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/655/1*NzAUUUZGw4-zFV33ul4Kog.png" /></figure><h4>Battery</h4><ol><li><strong>Excessive Wakeups</strong></li></ol><p>Percentage of battery sessions during which more than 10 wakeups occurred per hour. A battery session is the period between two full charges of a device. Data is collected only when the device is off-charger.</p><p><strong><em>Threshold: 1.35%</em></strong></p><p>Source: <a href="https://developer.android.com/topic/performance/vitals/wakeup.html">https://developer.android.com/topic/performance/vitals/wakeup.html</a></p><p><strong>2. Excessive WiFi Scans</strong></p><p>Percentage of battery sessions during which users experienced more than 4 Wi-Fi scans per hour. A battery session is the period between two full charges of a device. Data is collected only when the device is off-charger.</p><p><strong><em>Threshold: 0.10%</em></strong></p><p>Source: <a href="https://developer.android.com/topic/performance/vitals/bg-wifi.html">https://developer.android.com/topic/performance/vitals/bg-wifi.html</a></p><h4>Stability</h4><ol><li><strong>ANR(App Not Responding)</strong></li></ol><p>Percentage of daily sessions during which your users experienced at least one ANR. A daily session refers to a day during which your app was used.</p><p><strong><em>Threshold: 0.47%</em></strong></p><p>Source: <a href="https://developer.android.com/topic/performance/vitals/anr.html">https://developer.android.com/topic/performance/vitals/anr.html</a></p><p><strong>2. Multi-ANR (App Not Responding) rate over time</strong></p><p>Percentage of daily sessions during which your users experienced at least two ANRs. A daily session refers to a day during which your app was used</p><p><strong><em>Threshold: 0.24%</em></strong></p><p>Source: <a href="https://developer.android.com/topic/performance/vitals/anr.html">https://developer.android.com/topic/performance/vitals/anr.html</a></p><p><strong>3. Crash Rate</strong></p><p>Percentage of daily sessions during which your users experienced at least one crash. A daily session refers to a day during which your app was used.</p><p><strong><em>Threshold: 1.09%</em></strong></p><p>Source: <a href="https://developer.android.com/topic/performance/vitals/crash.html">https://developer.android.com/topic/performance/vitals/crash.html</a></p><p><strong>4. Multi Crash Rate</strong></p><p>Percentage of daily sessions during which your users experienced at least two crashes. A daily session refers to a day during which your app was used.</p><p><strong><em>Threshold: 0.18%</em></strong></p><p>Source: <a href="https://developer.android.com/topic/performance/vitals/crash.html">https://developer.android.com/topic/performance/vitals/crash.html</a></p><h4>Rendering</h4><ol><li><strong>Slow Rendering</strong></li></ol><p>Percentage of daily sessions during which more than 50% of frames took longer than 16 ms to render. A daily session refers to a day during which your app was used. Google collects the render time of each frame rendered by your app if your app uses the UI Toolkit framework, but not if your app uses OpenGL directly.</p><p><strong><em>Threshold: 1.56%</em></strong></p><p>Source: <a href="https://developer.android.com/topic/performance/vitals/render.html">https://developer.android.com/topic/performance/vitals/render.html</a></p><p><strong>2. Frozen Frames</strong></p><p>Percentage of daily sessions during which more than 0.1% of frames took longer than 700ms to render. A daily session refers to a day during which your app was used. Google collects the render time of each frame rendered by your app if your app uses the UI Toolkit framework, but not if your app uses OpenGL directly.</p><p><strong><em>Threshold: 10.48%</em></strong></p><p>Source: <a href="https://developer.android.com/topic/performance/vitals/render.html">https://developer.android.com/topic/performance/vitals/render.html</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a338fc59e52" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mindorks/things-to-check-before-integrating-any-third-party-sdk-in-your-android-app-4a338fc59e52">Things to check before integrating any third party SDK in your Android app</a> was originally published in <a href="https://medium.com/mindorks">MindOrks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Art of Optimizing Android Testing]]></title>
            <link>https://medium.com/mindorks/the-art-of-optimizing-android-testing-c253f46b563b?source=rss-8613b6a6b6e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/c253f46b563b</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Yukti Srivastava]]></dc:creator>
            <pubDate>Mon, 19 Jun 2017 17:52:57 GMT</pubDate>
            <atom:updated>2017-06-20T06:32:44.242Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/709/0*roI_8A6keu7jZJt3." /></figure><p>Apps simply need to work! Let’s start with some numbers:</p><ol><li>Page delays</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/446/1*4vDDC7PsP8AjFf7CYTkt1w.png" /><figcaption><em>**Getelastic.com</em></figcaption></figure><p>2. 55% users blame the mobile app for poor performance not the device, not the Backend.</p><p>3. 53% of users uninstall or remove the app in the case of a severe issue, 37% stop using the app, and 28% look for an alternative</p><p><em>(**Hewlett Packard Enterprise, Mobile App Usage &amp; Abandonment Survey)</em></p><p>4. Only 15% of users would consider downloading an app with a 2-star rating</p><p><em>(**Walz, A.: The Mobile Marketer’s Guide to App Store Ratings &amp; Reviews)</em></p><p><strong>Why Testing is Important?</strong></p><p>Users are seldom tolerant of flaws and failures of apps, unless the app is essential to them.</p><p>Testing verifies that the app meets the requirements including, functional, usability, performance, reliability, security. QA processes help companies to reduce costs of support, while generating customer goodwill that could translate into revenue opportunities.</p><p>So, the Question is how to optimize Android app testing? Below are some solutions for optimizing</p><h3><strong>Fragmentation</strong></h3><p>Below is android fragmentation by manufacturer. It is practically impossible to cover each and every device. So we need to follow risk based testing. We should find out the user base and cover only top used devices. If only 1% of your users are using android 4.1, it’s not recommended to waste time on 4.1.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/517/0*XcpBWowjRI_MgsOd." /></figure><h3><strong>Heatmaps</strong></h3><p>Heat map uses a color coded overlays to show the “attention areas”, where are users clicking? which part of the product is being viewed and used the most? What path are users taking to perform an action?</p><p>Heatmap for mobile apps are generated only when users interacts (tap, swipe, scroll, zoom) on the screen and hence Click/Touch heatmap is the most popular for mobile apps. For each screen, generally there are two heatmap: one for each orientation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/225/0*dSgI-TBPUv0ypAWI." /></figure><p>Top tools for Heatmap</p><ul><li>Appsee</li><li>Heatdata</li><li>Uxcam</li><li>Appanalytics.io</li></ul><p>Heatmaps help us to analyze real use-cases which leads to designing better test-cases for the app. Heatmaps reveal user behaviour.</p><p>1. Link test: Are users clicking on dead ends?</p><p>2. Distraction test: Are irrelevant elements distracting users? This helps in designing better UX</p><p>3. Device test: Is app working fine on different screen sizes?</p><p>4. Depth test: Is all your content easily available?</p><p>5. Engagement test: What are app visitors really looking for.</p><p>6. Feature test: Which feature is being heavily used and which one is rarely used?</p><h3><strong>Google’s RAIL MODEL</strong></h3><p>Google published this model for Web but it is also relevant for Mobile apps.</p><p>A good quality app should follow <a href="https://developers.google.com/web/fundamentals/performance/rail">RAIL</a> model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/815/0*A1NB6iXaMroedy5M." /></figure><p><strong>R</strong>esponse to Input : Respond in 100ms</p><p><strong>A</strong>nimation: Each frame completes in &lt; 16ms</p><p><strong>I</strong>dle: Use idle time to proactively schedule work.</p><p><strong>L</strong>oad: Page should be ready to use in&lt;= 1000ms (1s)</p><h3><strong>Code Review</strong></h3><p>Code Review should be done to ensure :</p><ol><li>There shouldn’t be unnecessary objects as allocating memory is always more expensive than not allocating memory</li><li>If you don’t need to access an object’s fields, make your method static. Invocations will be about 15%-20% faster</li><li>Floating point should be avoided as it is about 2x slower than integer on Android-powered devices.</li><li>Use Package instead of Private Access with Private Inner Classes</li></ol><h3><strong>App profiling</strong></h3><p>Profiling is especially important on mobile apps because of the tight resource constraints. The end user could have a lower end device with less RAM, could be running multiple apps, or just switching between apps. You can avoid the Android OS from crashing your app by making sure it is as optimized as possible. There are many tools to do android app profiling, e.g.</p><p><strong>Dalvik Debug Monitor Server (DDMS)</strong></p><p>DDMS is a java app that is independent of the IDE you’re using and can be launched directly from the command line.</p><p>Features : Heap View, Memory allocation tracker, Method profiling, Logcat, File explorer, Thread examination, Network traffic, View hierarchy, Emulate phone calls, General System info(CPU, GPU, FPS)</p><p><strong>GPU Rendering</strong></p><p>You can enable GPU rendering under Android Developer options. This show on-screen bars that each represent one frame of rendering. The taller the bar the longer it took to render.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/235/0*nwbNu-alwnbFf-ov." /></figure><p><strong>Traceview</strong></p><p>Traceview is a graphical viewer for execution logs that you create by using the Debug class to log tracing information in your code. It displays the log data in two panels:</p><p>1. Timeline panel describes when each thread and method started and stopped</p><p>2. Profile panel provides a summary of what happened inside a method</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/872/0*sOE5UaeGOUUvZ9x5." /><figcaption>Timeline panel</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/868/0*eaZM34xEtQYwte7B." /><figcaption>Profile panel</figcaption></figure><p>In summary, Quality is a competitive advantage. Only in rare cases will people actively come back and use a product that gave them a poor experience the first time they used it. So Optimizing testing not only helps in saving time but also in retaining users.</p><p>Happy Testing!!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*rpKLOuoCVw-Gj7HVDTYOZw.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c253f46b563b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mindorks/the-art-of-optimizing-android-testing-c253f46b563b">The Art of Optimizing Android Testing</a> was originally published in <a href="https://medium.com/mindorks">MindOrks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>