<?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 RB on Medium]]></title>
        <description><![CDATA[Stories by RB on Medium]]></description>
        <link>https://medium.com/@rajeevbarde?source=rss-9973318b5e9d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*_2VmxOMnfod6ShAgWZ7-tg.png</url>
            <title>Stories by RB on Medium</title>
            <link>https://medium.com/@rajeevbarde?source=rss-9973318b5e9d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 00:20:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rajeevbarde/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[Tour of Quality in Agile World]]></title>
            <link>https://medium.com/@rajeevbarde/tour-of-quality-in-agile-world-bad16c5d2492?source=rss-9973318b5e9d------2</link>
            <guid isPermaLink="false">https://medium.com/p/bad16c5d2492</guid>
            <category><![CDATA[agile-testing]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[test-automation]]></category>
            <dc:creator><![CDATA[RB]]></dc:creator>
            <pubDate>Sat, 28 Sep 2019 19:58:50 GMT</pubDate>
            <atom:updated>2019-10-03T08:45:27.873Z</atom:updated>
            <content:encoded><![CDATA[<p>Welcome aboard on the QA tour , today we are going to explore various sights and attractions such as agile testing, automation, test failures and much more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/407/1*tDoviCnzmYOUKE5RCUxzng.png" /><figcaption>Let’s go !</figcaption></figure><p>Before we begin, let’s recap the agile manifesto -</p><ul><li><em>Individuals and interactions over processes and tools</em></li><li><em>Working software over comprehensive documentation</em></li><li><em>Customer collaboration over contract negotiation</em></li><li><em>Responding to change over following a plan</em></li></ul><h3>Sight 1: The Big Picture</h3><p>Before we dive deep into Quality, lets see the big picture where it exists within the organisation. Quality has evolved, taken various shapes since couple of decades but the fundamental objective has not changed : <strong>user satisfaction.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/651/1*zdAw0xgDU11ERrgCtIfevg.png" /><figcaption>Software Engineering: A Practitioner’s Approach by Roger S. Pressman [chap 14 : Quality Concepts]</figcaption></figure><p>One can look at testing as : <strong>“Art of evaluating user satisfaction”</strong></p><h3>Sight 2 : Agile Testing</h3><p>I assume everyone is aware of the traditional ‘waterfall’ testing approach.<br>so … what makes <strong>‘Agile’</strong> different?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*W11rcZMGwuvmYKd2csf4fA.png" /></figure><ul><li>There is no phase, it is a continuous iterative testing. Testing begins before development : being a stakeholder in project meeting, creating canonical acceptance criteria and providing early feedback.</li><li>Tester focuses more on the <strong><em>“working software</em>”</strong> with lean documentation.</li><li>Tester has a business outlook with user satisfaction in mind.</li><li>Agile enforces the tester to adapt to new technology due to its 4th value : <strong><em>“Responding to Change Over Following a Plan</em>”</strong>. Testing team takes the burden of regression, retesting same functionality again. Tester are smart enough to overcome using automation and strategies.</li></ul><h3>Sight 3: Testing Strategies</h3><p>Before testing begins, it’s always a good idea to keep an eye on the current test pyramid. It helps to provide better estimation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/565/1*Z0LKaOh5Yfr7cZ4YtpHTqg.png" /><figcaption><a href="https://martinfowler.com/bliki/TestPyramid.html">https://martinfowler.com/bliki/TestPyramid.html</a></figcaption></figure><ul><li>Strategies vary from one story to another.</li><li>Profiling business customer helps with better strategy. Sometimes in order to understand pre-testing configuration &amp; data needed for certain test scenarios, testers need to wear the customer’s hat.</li><li>Testers decides on strategies, for example if stories contains :-</li></ul><p># <strong>Business logic and development </strong>— Exploratory, Regression, E2E.</p><p># <strong>Addition of ‘middle name’ in business flow </strong>— Checking unit tests &amp; testing the API.</p><p># <strong>Hotfix deployment </strong>— Hotfix testing &amp; Sanity automation.</p><p># <strong>Investigating customer related tickets</strong> — Manual testing and DB analysis.</p><p>…. many more <a href="http://www.softwareqatest.com/qatfaq1.html#FAQ1_10">http://www.softwareqatest.com/qatfaq1.html#FAQ1_10</a></p><p>There are processes from traditional testing process are still needed :-</p><ul><li>Following defect life-cycle</li><li>Creating summary report &amp; bug tractability matrix.</li></ul><h3>Sight 4: Automation &amp; Tools</h3><p>Automation itself is vast &amp; needs a dedicated tour but here are some key takeaways.</p><p><strong>#Basic Information</strong></p><ul><li>Test automation helps product to achieve better <strong>stability</strong> &amp; <strong>faster delivery</strong>.</li><li>Just to be very clear — <strong><em>“100% automation is a myth”</em></strong>. Aiming for it is huge waste of resource and time. Manual testing is necessary.</li><li>So exactly ….what is automation in testing ? Its mostly focused towards <strong>Regression testing.</strong></li><li><strong>Test coverage report </strong>&amp; <strong>time taken </strong>are the key criteria for success of a good automation test suite.</li><li><strong>Test audits</strong> are equally important for a healthy regression suite along with scripts. If ownership is exist within the team, it is an optional step.</li></ul><p><strong>#Technology</strong></p><ul><li>The testing automation stack depends on the dev’s stack.</li></ul><ol><li>If development team uses C#, test framework created should be on C#. It has its own benefits in the long run</li><li>For devices, Java is an obvious choice due to Android (This might change in few years due to Fuchsia OS using Dart).</li></ol><ul><li>Maintaining a testing framework is requires requires efforts — library creation, refactoring similar test scenarios, 3rd party integrations etc</li></ul><p><strong>#Big Picture</strong></p><p>The final piece to make a successful test framework : integrate it with <strong>CI-CD</strong> [continuous integration — continuous deployment].</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/737/1*OrfOi92v05Y7kzkYKS4lgg.png" /><figcaption>Jenkins’s User Handbook</figcaption></figure><h3>Sight 5: Quality Failures</h3><p>Till now everything sounds great, we have agile testing, automation, strategies — yet failure occurs , below are few of them.</p><ul><li>QA team not being a part of project kickoff.</li><li>Lack of <strong>‘lean’</strong> documentation from all stakeholders in a Agile team.</li><li>Lack of training and skill-set required for automation.</li><li>Testing pyramid is in poor shape.</li></ul><p>…. and finally this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/389/1*YCT4T9Sr-MNOoWsvJZWEng.png" /></figure><p><strong>Tour ends ! Thanks for reading :)</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bad16c5d2492" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[India crypto/alt coin trading in 1 min]]></title>
            <link>https://medium.com/@rajeevbarde/india-crypto-alt-coin-trading-in-1-min-4e4b686a3f6f?source=rss-9973318b5e9d------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e4b686a3f6f</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[india]]></category>
            <category><![CDATA[binance]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[altcoins]]></category>
            <dc:creator><![CDATA[RB]]></dc:creator>
            <pubDate>Fri, 29 Dec 2017 19:45:54 GMT</pubDate>
            <atom:updated>2017-12-29T19:46:31.970Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>India crypto /alt coin trading in 1 min</strong></h3><p>so you heard of Bitcoin(BTC) trading via Zebpay/Koinex, which is</p><ul><li>INR (Bank) -&gt; BTC (Wallet)</li></ul><p><strong>How to trade with other coins ?</strong></p><ul><li>Trade exchanges uses bitcoin. So its BTC -&gt; All coins.</li><li>In same fashion, All coin -&gt; BTC (wallet)</li></ul><p><strong>How do I move BTC to trade exchange ?</strong></p><p>Using address provided.It is created for you automatically when registered. Example — 15gJiApW3G9MN2iTteQwQbq7NundwGWwv6</p><p>It takes min/hour to transfer. There are fees, please check.</p><p><strong>What are the trade exchange ?</strong></p><p><a href="https://www.binance.com/?ref=11122751">binance</a>, <a href="https://bittrex.com/">bittrex</a> and many more. I prefer binance.</p><p><strong>Where can I see all coins and price ?</strong></p><p><a href="https://www.coinmarketcap.com/">Cryptocurrency Market Capitalizations | CoinMarketCap</a></p><p>Thats it ! Short and simple.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e4b686a3f6f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Selenium : save 25% test time using WebDriverService]]></title>
            <link>https://medium.com/@rajeevbarde/use-webdriverservice-save-test-time-f7fa266eb91?source=rss-9973318b5e9d------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7fa266eb91</guid>
            <category><![CDATA[webdriverservice]]></category>
            <category><![CDATA[selenium-webdriver]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[windows]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[RB]]></dc:creator>
            <pubDate>Sun, 26 Nov 2017 15:39:44 GMT</pubDate>
            <atom:updated>2017-11-26T15:39:44.153Z</atom:updated>
            <content:encoded><![CDATA[<h3>Selenium tip : save 25% test time using WebDriverService</h3><p>There are many articles on the net explaining how to automate browser testing using WebDriver like</p><p><strong>ChromeDriver </strong>driver = new <strong>ChromeDriver</strong>();</p><p>There exist another way — <em>ChromeDriverService </em>which can be used as well. But why would anyone need it ? Answer is simple — it saves time. As per google <a href="https://sites.google.com/a/chromium.org/chromedriver/getting-started">doc</a>,</p><blockquote>The ChromeDriver class starts the ChromeDriver server process at creation and terminates it when quit is called. This can waste a <strong>significant amount of time</strong> for large test suites where a ChromeDriver instance is created per test</blockquote><h3>Implementing DriverService</h3><p>Implementation is pretty straightforward as shown below,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/586/1*Tbkhf2kKZObs7mwrne8_iw.png" /><figcaption>sample code</figcaption></figure><p>The C# API documentation for ChromeDriverService can be found <a href="http://seleniumhq.github.io/selenium/docs/api/dotnet/html/T_OpenQA_Selenium_Chrome_ChromeDriverService.htm"><em>here</em></a><em>.</em></p><h3>Performance Comparison</h3><p>Lets compare time taken to invoke &amp; dispose <strong>WebDriver </strong>and <strong>WebDriverService</strong>. The code contains 10 loops, navigating a webpage on local machine with 300 ms sleep.</p><h4><strong>1. Code &amp; Output</strong></h4><ul><li>WebDriver</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/568/1*wkWWAt0-4qZdgA2yFp73Ew.png" /><figcaption>code</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/782/1*5c7-YHUqgBCD10B3DGABxw.png" /><figcaption>output</figcaption></figure><ul><li>WebDriverService</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/697/1*ecd_0hsjXfIaVNO2TVK1wg.png" /><figcaption>code</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/778/1*lsTp9jVe9AQqbB7ajkhYww.png" /><figcaption>output</figcaption></figure><h4><strong>2. Result comparison</strong></h4><p>After running both codes on my machine, below are the results which shows <strong>WebDriverService </strong>is around <strong><em>25% faster</em></strong> than <strong>WebDriver</strong>. The code was ran 5 times for detailed result.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*_txXQoMiCEj_R-NrcMpdNA.png" /></figure><h3>Practical Usage</h3><p>Using Selenium WebDriverService is helpful when :-</p><ul><li>Large number of testcases which contains browser invocation.</li><li>Large number of testcases with multiple browser.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7fa266eb91" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Overview of C# Selenium WebDriver Namespace]]></title>
            <link>https://medium.com/@rajeevbarde/overview-of-c-selenium-namespaces-9473e7cb5158?source=rss-9973318b5e9d------2</link>
            <guid isPermaLink="false">https://medium.com/p/9473e7cb5158</guid>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[csharp]]></category>
            <category><![CDATA[selenium-webdriver]]></category>
            <category><![CDATA[windows]]></category>
            <dc:creator><![CDATA[RB]]></dc:creator>
            <pubDate>Sun, 26 Nov 2017 03:29:22 GMT</pubDate>
            <atom:updated>2020-07-01T14:49:11.547Z</atom:updated>
            <content:encoded><![CDATA[<p>UPDATED — <a href="https://www.jeevnotes.xyz/overview-of-c-selenium-webdriver-namespace/">https://www.jeevnotes.xyz/overview-of-c-selenium-webdriver-namespace/</a></p><p>While I was trying to understand the selenium namespace, found it confusing since it has too much inside and some obsolete namespace as well. Using Selenium webdriver 3.7.0 to explain the library. <em>[Note : This is not an implementation article and assuming reader knows basic implementation of webdriver]</em></p><p>The C# selenium library is can be grabbed from Nuget : <a href="https://www.nuget.org/packages/Selenium.WebDriver/"><em>webdriver </em></a>&amp; <a href="https://www.nuget.org/packages/Selenium.Support/"><em>support</em></a><em> . </em>Ignore <a href="https://www.nuget.org/packages/Selenium.WebDriverBackedSelenium/"><em>WebDriverBackedSelenium</em></a><em> </em>&amp; <a href="https://www.nuget.org/packages/Selenium.RC/"><em>RC</em></a><em> </em>since they are transitional package for old RC API. C# Selenium API documentation can be found here : <a href="http://seleniumhq.github.io/selenium/docs/api/dotnet/"><em>link</em></a></p><h3>Overview</h3><p>Before we begin, lets see a high level diagram of selenium test automation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/460/1*a7BVZGH_cdGtTRjrJkqH9A.png" /></figure><p>All the components above is present and configurable in API. The two libraries are — (i) WebDriver (ii) WebDriver.Support. They contain the following namespaces</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*zTm1XBlmSPnK7GV74qNhog.png" /></figure><h3>Namespace</h3><p>Below is a simple cheatsheet on the namespaces. <strong><em>Added few classes</em></strong> which i felt worth mentioning under each namespace.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/647/1*hdb5CZVkmACdFc-Zv3GbCg.png" /></figure><p><strong>OpenQA.Selenium : </strong>The biggest namespace in the package. Contains the fundamental components of the webdriver. They are group into :-</p><ol><li><strong><em>WebDriver Service/Options </em></strong>: These classes are responsible for initiating service, proxy, <a href="https://github.com/SeleniumHQ/selenium/wiki/DesiredCapabilities">capabilities</a>, extension, arguments, platform.</li></ol><ul><li><a href="http://seleniumhq.github.io/selenium/docs/api/dotnet/html/T_OpenQA_Selenium_DriverOptions.htm">DriverOptions</a> : managing options specific to a browser driver</li><li><a href="http://seleniumhq.github.io/selenium/docs/api/dotnet/html/T_OpenQA_Selenium_DriverService.htm">DriverService</a> : service provided by a native WebDriver server</li></ul><p>2.<em> </em><strong><em>Cookie/Screenshots </em>:</strong> Browser cookie management. Taking screenshot of the browser.</p><ul><li><a href="http://seleniumhq.github.io/selenium/docs/api/dotnet/html/T_OpenQA_Selenium_Cookie.htm">Cookie</a> : Represents a cookie in the browser.</li><li><a href="http://seleniumhq.github.io/selenium/docs/api/dotnet/html/T_OpenQA_Selenium_Screenshot.htm">Screenshot</a> : an image of the page</li></ul><p>3. <strong><em>Inputs/Logging</em></strong> : responsible for input interaction such as keyboard, mouse, navigation, touchscreen. Defines the log entry and type.</p><ul><li><a href="http://seleniumhq.github.io/selenium/docs/api/dotnet/html/T_OpenQA_Selenium_Keys.htm">Keys</a> : keys able to be pressed</li></ul><p>4. <strong><em>Elements/Exceptions</em></strong> : Classes contains the web element selector such as ClassName, id, XPath etc. While there are Exception defined in the package related to above classes.</p><ul><li><a href="http://seleniumhq.github.io/selenium/docs/api/dotnet/html/T_OpenQA_Selenium_By.htm">B</a>y : find elements within a document</li></ul><p><strong>OpenQA.Selenium.Remote </strong>: This namespace contains Web driver base class along with WebElement, sessionid , response. It has commands &amp; capabilities.It also deals with storage such as Application Cache, Local Storage, LocationContext, WebStorage and SessionStorage.</p><ul><li><a href="http://seleniumhq.github.io/selenium/docs/api/dotnet/html/T_OpenQA_Selenium_Remote_RemoteWebDriver.htm">RemoteWebDriver</a> : Provides a way to use the driver through</li><li><a href="http://seleniumhq.github.io/selenium/docs/api/dotnet/html/T_OpenQA_Selenium_Remote_RemoteWebElement.htm">RemoteWebElement</a> : allows you to have access to specific items</li><li><a href="http://seleniumhq.github.io/selenium/docs/api/dotnet/html/T_OpenQA_Selenium_Remote_Response.htm">Response</a> : Handles reponses from the browser</li></ul><p><strong>OpenQA.Selenium.Chrome/Edge/Firefox/IE/Opera/PhantomJS/Safari </strong>: This namespace contains implementation of Remote &amp; Selenium namespace. They are usually required for actual selenium testing. All browser classes inherits — RemoteDriver, DriverService, DriverOptions and RemoteWebElement.</p><ul><li><a href="http://seleniumhq.github.io/selenium/docs/api/dotnet/html/T_OpenQA_Selenium_Chrome_ChromeDriver.htm">ChromeDriver</a>, <a href="http://seleniumhq.github.io/selenium/docs/api/dotnet/html/T_OpenQA_Selenium_Chrome_ChromeDriverService.htm">ChromeDriverService</a>, <a href="http://seleniumhq.github.io/selenium/docs/api/dotnet/html/T_OpenQA_Selenium_Chrome_ChromeOptions.htm">ChromeOptions</a>, <a href="http://seleniumhq.github.io/selenium/docs/api/dotnet/html/T_OpenQA_Selenium_Chrome_ChromeWebElement.htm">ChromeWebElement</a></li><li><a href="http://seleniumhq.github.io/selenium/docs/api/dotnet/html/T_OpenQA_Selenium_Firefox_FirefoxDriver.htm">FirefoxDriver</a>, <a href="http://seleniumhq.github.io/selenium/docs/api/dotnet/html/T_OpenQA_Selenium_Firefox_FirefoxDriverService.htm">FirefoxDriverService</a>, <a href="http://seleniumhq.github.io/selenium/docs/api/dotnet/html/T_OpenQA_Selenium_Firefox_FirefoxOptions.htm"><br>FirefoxOptions</a>, <a href="http://seleniumhq.github.io/selenium/docs/api/dotnet/html/T_OpenQA_Selenium_Firefox_FirefoxWebElement.htm">FirefoxWebElement</a></li></ul><p><strong>OpenQA.Selenium.Html5 : </strong>This package contains HTML5 definitions and represents browser’s physical locations.</p><ul><li><a href="http://seleniumhq.github.io/selenium/docs/api/dotnet/html/T_OpenQA_Selenium_Html5_Location.htm">Location</a> : Represents the physical location of the browser.</li></ul><p><strong>OpenQA.Selenium.Interactions : </strong>This class responsible for advance interactions with the browser such as Action &amp; Touch Action.</p><ul><li><a href="http://seleniumhq.github.io/selenium/docs/api/dotnet/html/T_OpenQA_Selenium_Interactions_Actions.htm">Actions</a> : mechanism for building advanced interactions</li></ul><p><strong>OpenQA.Selenium.Support.UI : </strong>This namespace exist in both DLLs. It helps testing with explicit waits, advanced expected conditions and WebElement Load status.</p><ul><li><a href="http://seleniumhq.github.io/selenium/docs/api/dotnet/html/T_OpenQA_Selenium_Support_UI_ExpectedConditions.htm">ExpectedConditions</a> : set of common conditions</li><li><a href="http://seleniumhq.github.io/selenium/docs/api/dotnet/html/T_OpenQA_Selenium_Support_UI_LoadableComponent_1.htm">LoadableComponent&lt;T&gt;</a> : Represents any abstraction of something that can be loaded</li></ul><p><strong>OpenQA.Selenium.Support.Events : </strong>The namespace helps during execution of test by logging the details using events.</p><ul><li><a href="http://seleniumhq.github.io/selenium/docs/api/dotnet/html/T_OpenQA_Selenium_Support_Events_EventFiringWebDriver.htm">EventFiringWebDriver</a> : A wrapper around an arbitrary WebDriver instance which supports registering for events</li></ul><p><strong>OpenQA.Selenium.Support.PageObjects : </strong>A useful namespace to smartly identify WebElements and can produce PageObject modeling for a page.</p><ul><li><a href="http://seleniumhq.github.io/selenium/docs/api/dotnet/html/T_OpenQA_Selenium_Support_PageObjects_ByAll.htm">ByAll</a> : locate elements within a document using a series of lookups</li><li><a href="http://seleniumhq.github.io/selenium/docs/api/dotnet/html/T_OpenQA_Selenium_Support_PageObjects_ByChained.htm">ByChained</a> : locate elements within a document using a series of other lookups.</li><li><a href="http://seleniumhq.github.io/selenium/docs/api/dotnet/html/T_OpenQA_Selenium_Support_PageObjects_PageFactory.htm">PageFactory</a> : ability to produce Page Objects modeling</li></ul><h3>Thanks for Reading.</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9473e7cb5158" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>