<?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 Satheesh Kumar on Medium]]></title>
        <description><![CDATA[Stories by Satheesh Kumar on Medium]]></description>
        <link>https://medium.com/@satheesh.francis?source=rss-cf03b3ac7ffe------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*tAi8GK9aRMnj76cmSXAgqA.jpeg</url>
            <title>Stories by Satheesh Kumar on Medium</title>
            <link>https://medium.com/@satheesh.francis?source=rss-cf03b3ac7ffe------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 12:12:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@satheesh.francis/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[Continuous Testing for iOS Apps using XCUITest, Bitrise & Browserstack]]></title>
            <link>https://medium.com/dubizzletechblog/continuous-testing-for-ios-apps-using-xcuitest-bitrise-browserstack-795c7c1af391?source=rss-cf03b3ac7ffe------2</link>
            <guid isPermaLink="false">https://medium.com/p/795c7c1af391</guid>
            <category><![CDATA[bitrise]]></category>
            <category><![CDATA[xcuitest]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[browserstack]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[Satheesh Kumar]]></dc:creator>
            <pubDate>Thu, 01 Aug 2019 10:40:35 GMT</pubDate>
            <atom:updated>2019-10-17T21:51:59.584Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EKEtEMZW7iB0UkFSRqkktg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@andreas_haslinger?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Andreas Haslinger</a> on <a href="https://unsplash.com/search/photos/ios-testing?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>iOS Apps Continuous Testing journey is really exciting for anyone who is trying to implement it using different tools/framework combinations.</p><p>In this article, I will share about how it can be implemented using XCUITest, Bitrise and Browserstack platforms.</p><p>We used <strong>XCUITest </strong>automation framework provided by Apple and POM design pattern for writing tests which helped us to write clean and maintainable tests.</p><p><strong>Bitrise </strong>continuous Integration system enabled us to create pipelines which can build both iOS and android projects without worring about managing build environments/machines.</p><p><strong>Browserstack </strong>served the need of a Cloud Testing platform well to enable “Continuous Testing” for iOS and android apps.</p><p>Let me share few of the tips that will make “Continuous Testing” seamless in your Continuous Delivery pipelines:</p><ol><li><strong>Avoid building “UI Automation Scheme/Tests” in the release pipelines</strong>: If you are building your xcuitests as well in the release pipelines (release to beta/appstore), this will increase the build time and might act like additional build step which would take almost same time of building your ipa. The optimized approach would be to build your “XCUITests” scheme on a nightly basis(we created scheduled jobs in Bitrice-CI) and publish the xcuitests to your cloud testing platform. Browserstack has handy apis using which you can publish your xcuitests on the cloud, which can be used for executing the tests later in the release pipelines.</li></ol><p><strong>Bitrise-CI: Scheduled Job View:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fA-lNrpCqNynlnVCZwEQmQ.png" /></figure><p>Now your release pipeline steps will be optimized like below: (ie: once the ipa is built, just publish it to Browserstack and then start executing tests using previously published xcui_test_suites)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YsFr88MmahT-PONm2ycFnQ.png" /></figure><p><strong>2. Group your tests:</strong></p><p>We classified our tests into BVT, Smoke, Sanity and Regression and created separated files to store tests details and device to execute the test as shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qSfhYSsGYCbEE3pyooMkSA.png" /></figure><p><strong>3. Use the newly available Bitrise step “Browserstack iOS UI Test” to specify test configurations like ipa url, xcuitest url, tests to execute etc. [ Really excited to become the creator/maintainer of this step :) ]</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s6B9Wyesi4QpIQUD4WTFbQ.png" /></figure><p>Following are the configuration options available on this step:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RosSL2Jef41w7G3IsXdUdw.png" /></figure><p>As we all know that “UI Automation” is sometimes flaky due to different reasons, automatic re-try for failed tests is a must have feature in your CI pipelines. This step supports automatic retry as well to make ui test execution seemless in the continous testing pipelines.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ICpz2865neZb04ll7spjBQ.png" /></figure><p>Also, “Browserstack local testing feature also is supported via this step”. One requirement is, you need to make sure Browserstack local binary is running before executing this step and jq pacakge is installed on the node on which this step is running.</p><p>That’s it. Now you should be able to run your XCUITests on Browserstack successfully.</p><p><strong>Test Results from Browserstack cloud testing platform:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sEaY5VyFhGSNgBNYGCVp1w.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=795c7c1af391" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dubizzletechblog/continuous-testing-for-ios-apps-using-xcuitest-bitrise-browserstack-795c7c1af391">Continuous Testing for iOS Apps using XCUITest, Bitrise &amp; Browserstack</a> was originally published in <a href="https://medium.com/dubizzletechblog">dubizzle Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tips to enhance/optimize appium automation framework.]]></title>
            <link>https://medium.com/dubizzletechblog/tips-to-enhance-optimize-appium-automation-framework-2f066b10ebe6?source=rss-cf03b3ac7ffe------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f066b10ebe6</guid>
            <category><![CDATA[appium]]></category>
            <category><![CDATA[uiautomation]]></category>
            <category><![CDATA[mobile-automation-testing]]></category>
            <category><![CDATA[android-testing]]></category>
            <category><![CDATA[continuous-testing]]></category>
            <dc:creator><![CDATA[Satheesh Kumar]]></dc:creator>
            <pubDate>Tue, 12 Feb 2019 10:36:05 GMT</pubDate>
            <atom:updated>2019-02-12T10:36:05.471Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OQZ5LXy03Ql2xKIQ914W8A.png" /><figcaption>Mobile Testing Automation Tool</figcaption></figure><p>The most commonly used stack for android automation is [<strong>Appium,Java,TestNG]</strong>. Following are few tips to enhance/optimize this framework.</p><p><strong>A) Setup up Re-Try logic using TestNg: </strong>Retry logics will ensure any random flakiness with the test is handled automatically to ensure seamless running of automation tests in the CD Pipeline.</p><p><strong>Implementation Steps:</strong></p><p>Step1: Create a RetryAnalyzer class which implements IRetryAnalyzer and can monitor the test results and informs TestNg runner to re-run failed test case.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0fyg6G68__GNZVKcLuXarw.png" /></figure><p>Now, your test methods needs to be annotated with “RetryAnalyzer.class”, so that it can send the tests results status to it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*apxWE3yjZNbgyzJsgY7rPg.png" /></figure><p><strong>B) Enable Parallelism using Latest Appium Driver: </strong>If you are using in-house testing infrastructure, (Note: Preference will be to use Cloud Testing solutions), you need to enable Parallelism using Latest Appium Driver to keep the implementation strategy simpler.</p><p>In the older versions of appium server, we would require to start separate Appium server instances to enable paralell testing on different real devices/simulators, however the latest version of appium server supports paralellism using single appium server itself.</p><p><strong>Implementation Steps:</strong></p><p><strong>Step 1</strong>: Update your base driver method to accept parameters like udid and systemport.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*943qL0clznCknK24n_rfZw.png" /></figure><p><strong>Step2</strong>: TestNg.xml file needs to be updated, to pass these parameter values to base driver method. [Note: You can specify any port number between8200 to 8299]</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ab6KZpnhQwP7C3OMpw6k8g.png" /></figure><p><strong>C) Implement UI Scrolling using UIAutomator(UiScrollable): </strong>Latest versions of Appium server doesnt have swipe/scrollTo methods. You need to use UIAutomator for this. Different ways of implementing scrolling using UIScrollable class are mentioned below:</p><pre><strong>public void </strong>scrollForwardByResourceID(String resourceID) {<br><br>    <strong>driver</strong>.findElementsByAndroidUIAutomator(<strong>&quot;new UiScrollable(new UiSelector().resourceId(&#39;&quot;</strong>+resourceID+<strong>&quot;&#39;)).scrollForward()&quot;</strong>);<br><br>}<br><br><strong>public void </strong>scrollForwardByResourceID(String resourceID, <strong>int </strong>steps) {<br><br>    <strong>driver</strong>.findElementsByAndroidUIAutomator(<strong>&quot;new UiScrollable(new UiSelector().resourceId(&#39;&quot;</strong>+resourceID+<strong>&quot;&#39;)).scrollForward(&quot;</strong>+steps+<strong>&quot;)&quot;</strong>);<br><br>}<br><br><strong>public void </strong>scrollBackwardByResourceID(String resourceID, <strong>int </strong>steps) {<br><br>    <strong>driver</strong>.findElementsByAndroidUIAutomator(<strong>&quot;new UiScrollable(new UiSelector().resourceId(&#39;&quot;</strong>+resourceID+<strong>&quot;&#39;)).scrollBackward(&quot;</strong>+steps+<strong>&quot;)&quot;</strong>);<br><br>}</pre><p>Other important methods available in UiScrollable class are as follows: <strong>scrollDescriptionIntoView</strong>(String text), <strong>scrollTextIntoView</strong>(String text), scrollIntoView(<strong>UIObject</strong> obj). Complete list of referene can be found <a href="https://developer.android.com/reference/android/support/test/uiautomator/UiScrollable">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f066b10ebe6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dubizzletechblog/tips-to-enhance-optimize-appium-automation-framework-2f066b10ebe6">Tips to enhance/optimize appium automation framework.</a> was originally published in <a href="https://medium.com/dubizzletechblog">dubizzle Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Achieving Continuous Testing in the Continuous Delivery Pipeline for Web-apps]]></title>
            <link>https://medium.com/dubizzletechblog/achieving-continuous-testing-in-the-continuous-delivery-pipeline-for-web-apps-b3181900e4c9?source=rss-cf03b3ac7ffe------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3181900e4c9</guid>
            <category><![CDATA[continuous-testing]]></category>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[continuous-deployment]]></category>
            <dc:creator><![CDATA[Satheesh Kumar]]></dc:creator>
            <pubDate>Tue, 06 Nov 2018 08:40:28 GMT</pubDate>
            <atom:updated>2018-12-10T02:32:24.274Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RrBgSZrczhHPVR-LMzFx6Q.jpeg" /><figcaption>Achieving Continuous Testing in the Continuous Delivery Pipeline</figcaption></figure><p>“<strong>Continuous Testing</strong>” is the buzzword at the moment in the QA/Test Automation world. Let’s have a look at how this can be achieved in an efficient way.</p><p><strong>What is </strong>Continous Testing?</p><p>Continuous testing is the process of executing automated tests as part of the software delivery pipeline to obtain immediate feedback on the business risks associated with a software release candidate. [ref: wikipedia]</p><p>Following <strong>Test pyramid</strong> explains an efficient strategy to achieve Continuous Testing:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wxjkLya4aVc9nISRLmowHw.png" /><figcaption><strong>TEST PYRAMID</strong></figcaption></figure><p>As shown in the diagram above, code coverage via <strong>Unit Tests </strong>plays a major role on this. Maximizing coverage for your front-end/backend services via unit tests will give confidence at the foundation level itself.</p><p>Next step is to set-up CI pipelines, which will be triggered every time developer commits code to source control repository to enable code compliance with the quality guidelines set and also ensures immediate feedback to Developers.</p><p>Another advantage of CI Integration is as follows: once the developer creates a Pull Request(PR) in the Source control System, the reviewers of the PR can easily get information about the CI Status on the PR itself, which will reduce the feedback time required to approve the PR.</p><p>In the next stage of Continuous Testing model, we need to write integration tests and API end point tests[RestAssured is the commonly used library for validating api response, schema and other tests]. For web frontend, adding integration level cypress tests, which can mock specific pages and validate particular functionality, will also help to improve the coverage.</p><p>For UI Automation, considering its complexity and maintainability, try to pick specific set of test cases from your Master Test Cases, and automate it using Stable frameworks. To ensure Browser and OS compatibility these tests can be integrated with any cloud testing platforms and execute it in your CD Pipeline.</p><p>Adding Performance Tests scripts [Jmeter scripts will do the job] and Security Tests [OWASP ZAP is a good open source tool to use], will make Continuous Testing more powerful in the Continuous Delivery Pipeline.</p><p>Sample Implementation of such pipeline will be as shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yCeklCV2FuxVaVtwJsN73w.png" /><figcaption>CI/CD Pipeline with Continuous Testing</figcaption></figure><p><strong>10 Key Points to </strong>consider while implementing <strong>UI/Functional Test Automation Frameworks</strong>:</p><ol><li>Use stable automation frameworks</li><li>Use POM model to organize your tests</li><li>Try to use robust element locators which are less likely to change and are fast.</li><li>Organize your Test Data.</li><li>Use BDD frameworks, which can help to easily convert your user stories/test scenarios into Automation Test Scripts and provides many other benefits.</li><li>Lets not duplicate same tests as part of different test suites.</li><li>Avoid long running tests and split it into separate tests for reliability</li><li>CI/CD Support and other key features like parallel execution, failed tests auto-retry, reporting tests results etc.</li><li>Implement traceability between your Manual Test Cases and Automated Test Cases. [Ex: Test_case_id can be used for mapping]</li><li>Cloud Testing platform support is a major factor and needs to be considered in the starting of the “Test Automation framework” design itself.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3181900e4c9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dubizzletechblog/achieving-continuous-testing-in-the-continuous-delivery-pipeline-for-web-apps-b3181900e4c9">Achieving Continuous Testing in the Continuous Delivery Pipeline for Web-apps</a> was originally published in <a href="https://medium.com/dubizzletechblog">dubizzle Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>