<?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 Subhash Kotra on Medium]]></title>
        <description><![CDATA[Stories by Subhash Kotra on Medium]]></description>
        <link>https://medium.com/@subhash.kotra?source=rss-2d9dabc5c481------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*lRPcmYqW3xKC4h8yWSNmLQ.jpeg</url>
            <title>Stories by Subhash Kotra on Medium</title>
            <link>https://medium.com/@subhash.kotra?source=rss-2d9dabc5c481------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 15:18:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@subhash.kotra/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[Contract Testing: The imperative piece in the Testing Pyramid]]></title>
            <link>https://medium.com/tide-engineering-team/contract-testing-the-imperative-piece-in-the-testing-pyramid-7e3f43c93d57?source=rss-2d9dabc5c481------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e3f43c93d57</guid>
            <category><![CDATA[e2e-testing]]></category>
            <category><![CDATA[contract-testing]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[microservice-architecture]]></category>
            <dc:creator><![CDATA[Subhash Kotra]]></dc:creator>
            <pubDate>Tue, 12 Sep 2023 09:16:26 GMT</pubDate>
            <atom:updated>2023-09-12T09:16:26.186Z</atom:updated>
            <content:encoded><![CDATA[<h3>Contract Testing: The imperative piece in Testing Pyramid</h3><p>Hello Everyone! 👋</p><p>As the world shifts from a single, monolithic backend architecture to using micro-services, the dependency on various teams to manage these services increases. If you are a mid-level backend and Automation engineer looking to navigate through this change — this article is for you. It will delve into the world of Contract Testing to answer questions like:</p><p>✅ <strong>What are Contracts? <br></strong>✅ <strong>Why is it important to test them? <br></strong>✅ <strong>And how can we leverage Contract Tests to reduce the dependency on E2E Tests?</strong></p><p>😏Here we go!</p><p>💡 Contracts are created from a particular micro-service from both the schema and the key perspectives.</p><p>Think about a scenario where an endpoint in micro-service A is used by multiple other services B, C and D as depicted here 👇</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kbEQyvhEbuJ4E_Mman52pg.png" /><figcaption>Service Dependency</figcaption></figure><p>Let’s assume there are some changes to the endpoint in microservice A and the team responsible for them could not communicate with teams B, C and D. In this case, <strong>the endpoints in B, C and D would fail whenever there is a call that goes to it</strong>.</p><p>In normal circumstances, this call occurs only during the E2E Tests, often identifying defects late in the Release cycle.</p><p>💡 This is where Contract Tests come in. Automating them helps identify changes early into the release cycle.</p><p><strong>In the dynamic landscape of backend microservices, ensuring seamless communication and cooperation between disparate components is pivotal. <em>Contract testing is here for this</em>. It has an essential strategic value for strengthening the robustness and reliability of interconnected micro-services.</strong></p><p>Here is where Contract Tests sit in the Testing Pyramid:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/411/1*QAy8K08JssjDZutILWR4sw.png" /><figcaption>Testing Pyramid</figcaption></figure><p>Now that issues can be identified right after the Unit Tests itself, chances (if any) of slipping the issues to the upper level are close to zero, in-turn resulting in rapid development cycles.</p><p>💡 The tests act as a safety net during deployments, instilling confidence in the changes introduced to the microservices ecosystem.</p><p>Let’s take a look at the three components that constitute a Contract Test.👀</p><p><strong>Consumer<br></strong>A Consumer generates and stores their expectations in, what is typically termed as, a Contract file. This file ties its contents to the consumer code. The contract file can be generated in 2 ways:</p><ul><li>by recording requests &amp; expected responses, or</li><li>by generating expectations from the class/schema files available in the Consumer code base.</li></ul><p>In our example earlier, service A would typically be termed as a Consumer.</p><p><strong>Provider<br></strong>Providers are the services which use the Consumer and validates its service against the Contract file generated by the Consumer. For this to happen, the Consumer must pass the contract file generated to all the providers and at all times whenever there is a change in its service. The providers can be other services who are making a call to Consumers or some Front-end actions, like clicking on a button on a Web-page etc. From the scenario above service B, C and D are typical examples of Providers. And as such, they will again create a dependency on maintaining the Contract Files and this is where Pact Broker comes into the picture.</p><p><strong>Pact Broker<br></strong>A Pact broker is a centrally located storage to maintain all the contracts of an organisation. This can be a self-created ecosystem using AWS or using the PACT FLOW provided by the pact.io. Once a Pact Broker is configured, one needs to provide the details of it in the Consumer and Provider Tests for it to understand the nuances. After these configurations, a Consumer and the corresponding Providers will be communicating with the Pact Broker and validate their Contracts with each other.</p><p>The process automates the collaboration amongst all the teams without any dependency on a single person. It also gives us actionable insights which enables us to amplify the reliability and agility of our backend micro-services infrastructure. Hopefully this article is helpful to understand Contract Tests better in order to reduce the deployment cycles in our respective organisations. I strongly recommend using Contract Tests in your day-to-day operations.</p><p>🛰️ Empowering your micro-services with the solidity of contracts will revolutionise how Engineers design, develop, and deploy in this ever-evolving domain. 🌌</p><p>Good luck!</p><p><strong>About the Author</strong></p><p>I am Subhash, a QA Automation Lead at <a href="https://www.tide.co/">Tide</a> — a business financial platform focusing on the needs of SMEs. We concentrate on how best we can automate what we do on a daily basis. My primary interest is to take up new technologies and the challenges associated with them. Outside of work, I am passionate about running, and have completed 4 half-marathons till date.</p><p>For more details and questions find me on <a href="https://www.linkedin.com/in/subhash-kotra-7290068/">LinkedIn</a>/<a href="https://twitter.com/subhashkotra">Twitter(X)</a>/<a href="/service/mailto: subhash.kotra@tide.co">Email</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e3f43c93d57" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tide-engineering-team/contract-testing-the-imperative-piece-in-the-testing-pyramid-7e3f43c93d57">Contract Testing: The imperative piece in the Testing Pyramid</a> was originally published in <a href="https://medium.com/tide-engineering-team">Tide Engineering Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Data Management in Automation Testing]]></title>
            <link>https://medium.com/@subhash.kotra/data-management-in-automation-testing-f20ffaa1ec65?source=rss-2d9dabc5c481------2</link>
            <guid isPermaLink="false">https://medium.com/p/f20ffaa1ec65</guid>
            <category><![CDATA[localization-testing]]></category>
            <category><![CDATA[test-data-management]]></category>
            <category><![CDATA[data-management]]></category>
            <category><![CDATA[automation-testing]]></category>
            <dc:creator><![CDATA[Subhash Kotra]]></dc:creator>
            <pubDate>Sat, 15 Jan 2022 15:52:42 GMT</pubDate>
            <atom:updated>2022-01-15T15:52:42.207Z</atom:updated>
            <content:encoded><![CDATA[<p>In this new Techno-Digital age, all of us focus on two major topics: <strong>Automation</strong> &amp; <strong>Data</strong>. Let us make an attempt to have a look at them together, i.e. Data Management in Automation Testing.</p><p>As with any approach, there can be many alternatives, I am going to put forward an approach which has suited me, in most of the frameworks.</p><p><em>P.S: Since, I have worked more on Banking/FinTech applications, the examples in this post would be around Banking Applications.</em></p><ol><li>The FIRST suggestion I would have is to try and <strong>Generate a Unique Set of Data for every Test Case</strong> as much as possible. One should always try to generate the data required for a Test case before the execution and <em>destroy</em> it properly after the usage. This way, you won’t face issues that come with reusing the same data again and again, reducing (if not removing) the possibilities of Data Corruption failures in Automation. I Strongly recommend generating this Data using APIs/BackEnd (micro)services, further helping us in creation of Faster and maintainable data, without having to go through the ever-changing UI screens.</li></ol><p>For example, Consider the Test case of Requesting a New card, in this case, a new unique user (created from BE services) would be helpful. This user when created through the API’s would provide us huge leverage in overall Automation execution.</p><p>2. While we try to create a Unique Set of Data, practically I do understand that it is not always possible. In such cases, the SECOND question arises: “<strong>Data Storage</strong>”. In my opinion, Data should always be kept separate from the code and stored in easily maintainable files like .property.</p><p>As an example, let us consider storing a set of Test Cards, which are needed to be maintained. This set if maintained in an external file, we would need to change the details (if and when needed) only in this particular file, without having to touch any of the code.</p><p>3. Now, the big one: <strong>Environments: </strong>Most of the banking applications would have multiple environments and it is crucial to consider this while defining test automation data strategy. Let us take a look at managing Test Data on multiple environments in the most flexible, scalable and easily maintainable manner. It is extremely important to split, the file(s), into two categories:</p><ul><li>Common for All Environments</li><li>Specific to a particular environment</li></ul><p>The file(s) that we have discussed earlier, could then be created like below:</p><ul><li>One Common File which would be needed across All Environments and can be used extensively</li><li>One file for each of the other environments. For environment-specific files, put each file into its own environment folder</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/711/0*L_JdOD8yCwvvcIY_" /></figure><p>Example: User Credentials to access a crowd-based device platform (or administrator credentials) can be kept in ‘common.properties’ file and URL of the application or a particular backend service should always be kept in the Environment specific property files.</p><p>4. The Biggest question in these days of International applications is <strong>Localisation</strong>:</p><p>When it comes to managing Automation Data for different locales, the data should be separated for different locales in the different Environments. We should be extremely careful of keeping the data stored in each of the environments and locale specific files (described above) to the extent of what is required and NOT over-flood the files.</p><p>For Example, it’s the various messages displayed on the application, currency of a particular country would be locale dependant, hence, these types of Data should be kept in the locale specific files.</p><p>For any automation project, on a high level, if we can keep these above points considered, we would have a stable running automation test cases without much hiccups.</p><p><strong>Thank you and Wish everyone all the very best.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f20ffaa1ec65" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bitrise — An Aggregator for Mobile Apps]]></title>
            <link>https://medium.com/tide-engineering-team/bitrise-an-aggregator-for-mobile-apps-4b4296dd4ac0?source=rss-2d9dabc5c481------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b4296dd4ac0</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[mobile-apps]]></category>
            <dc:creator><![CDATA[Subhash Kotra]]></dc:creator>
            <pubDate>Thu, 22 Apr 2021 16:21:00 GMT</pubDate>
            <atom:updated>2021-04-22T16:21:00.290Z</atom:updated>
            <content:encoded><![CDATA[<h3>Bitrise — An Aggregator for Mobile Apps</h3><p>Bitrise is a Continuous Integration and Delivery (CI/CD) Platform as a Service (PaaS) focussing on Mobile App development. It is powerful and complex, yet easy to build and maintain, especially in the development and Automation of Mobile apps.</p><p>So, the first question that would come to our mind is: <strong><em>“How do I access it?”</em></strong>. That’s where the <em>“easy” </em>part comes into play. Bitrise can be easily integrated with Bitbucket, Gitlab, Github, or simply by just creating credentials using your Email ID. Signing up with any of the Git service providers helps us to connect the Bitrise account with the service provider and access any of the repositories. We can also integrate between the service providers, for e.g., if I sign-up with Github, I can connect my Bitrise account with any of the repositories, not only in Github but on Bitbucket and Gitlab as well. Amazing isn’t it?</p><p>The account set-up is sorted, what’s the next thing we want → <strong><em>“How can I add a new App</em></strong>”. Right then, here are the essentials:</p><p><strong>Pre-requisites:</strong></p><ol><li>Automation Repo is created</li><li>git submodule is added for the development project by using the following command:</li><li>git submodule add git@bitbucket.org:tideaccount/&lt;dev-project-name&gt;.git</li><li>&lt;dev-project-name&gt; example: universal-app-android</li></ol><p><strong>Steps:</strong></p><ol><li>On the Bitrise home page → Click on Add New App (Bitrise_1.png)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_gM97BvpEqUMqwRI" /></figure><p>2. Select ‘Add New App on Web UI’ (Bitrise_3)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VxJhOAnne36xo4WA" /></figure><p>3. On the ‘Create New App’ screen, Choose Account as &lt; organization account&gt;(Bitrise_2)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*r1fHcDjIdiIeeYN8" /></figure><p>4. Set the Privacy as ‘Private’ and click on the Next button</p><p>5. Select the repository that you want to connect to (Bitrise_4)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JWo115Zn10D8tat7" /></figure><p>6. On the ‘Set-up repository access’ step, Select ‘I need to’ (Bitrise_5)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jxJq-9Nn-zTyFjlN" /></figure><p>7. Copy the SSH-key and add this key to the submodule project (dev-project-name) SSH keys</p><p>8. Enter the branch name of the dev-project that we want the association for</p><p>9. At this stage, Bitrise will run validations with the repository and configurations set above</p><p>10. The project build configuration step will be performed by Bitrise.</p><p>11. Choose a nice-looking ‘App Icon’ for the App and your App is ready.</p><p>Additionally, Bitrise also allows us to set-up</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*xHlLh27LHjZC9LTdN7tKug.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*qeQvDmnwYa465K3M9DEYWQ.jpeg" /><figcaption>Triggers based on Code Push or Pull Request on a particular branch</figcaption></figure><p>After adding an app, what would anyone want in a CI/CD tool:</p><p><strong><em>“How do I view/customize builds?”</em></strong></p><p>In Bitrise, as soon as an App is added, the first build will be triggered automatically and can be viewed in the <em>‘Dashboard’</em> screen on one’s home page. This build (a series of jobs executed in order) can then be further viewed/customized in ‘<em>WorkFlow Editor</em>’. In Bitrise terminology, the jobs are called ‘Steps’, which represent blocks of script execution, and can be arranged on the UI. It can accomplish the various things, mentioned (but not limited to) below:</p><ul><li>Clone your repository</li><li>Build your app</li><li>Run tests</li><li>Pass values to each other (Refer to the next section)</li><li>Send notification messages to stakeholders</li></ul><p>As the App was set as ‘Private’ (Refer Step-4 in ‘Adding a new App section’), we should be providing access to Team members to whom we wish to give access to the App. There is no limit on the number of ‘Team members’.</p><p>In any CI/CD tool, the most important task would be to know how to pass values from one Step to another, as this would be needed for most of the real-time scenarios. In Bitrise, this can be achieved by using the below command:</p><p><em>“envman add — key &lt;variable-name&gt; — value &lt;value&gt;”</em></p><p>This command, when provided in a script section of a Step, would extract the value and assign it to the variable name. This variable would then be used in other steps.</p><p><strong><em>Fan-out option:</em></strong></p><p>There is a feature within Bitrise that can restrict the amount of time a build could run, for e.g.: if I say that a build should run only for <em>‘X’</em> minutes, then the builds would automatically get <em>Aborted</em> after the <em>‘X’</em> minutes. In the new dynamic world, we all want fast results and this option would help us keeping our build times low, as again, we want to have lesser build times, and release to the market sooner. So, now the question everyone would have is how to live with it, or do we have a workaround? Yes certainly, Bitrise has an interesting feature called — ‘Fan-out’, what it does is: literally ‘fanning out or in simple terms segregate the steps of a build into 2 different builds and still being integrated to each other.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/812/1*l6hksXa6_xthjS-t2sGZmw.jpeg" /></figure><p>Let’s take a look at it through a real-time example:</p><p>Consider a scenario where we have Unit Tests (or Any other tests) for an application. Generally, we tend to keep the tests as the last step, but still part of the same build. So, once the “.apk” or a “.ipa” file is generated, we execute these tests to quickly do some sort of tests to make sure everything is working. But over a period of time, these tests keep on increasing (based on the features being rolled out) and in the end increasing the build time, resulting in higher build times and by that making the Bitrise build ‘Abort’. In this typical case, what we can do is: “Separate out the tests from the build generation process”.</p><p>There will be 2 builds in this case:</p><p>Workflow 1</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/1*Ed5dmNShWUUpTEhfstu_eA.jpeg" /><figcaption>Build Generation</figcaption></figure><p>Workflow 2</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/340/1*r_vFrNF1pn2mB3qtqHkOYA.jpeg" /><figcaption>Test Execution</figcaption></figure><p>This is how it is done:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GaxB6doM-JpWxgrK" /></figure><p>So if I have a workflow created for running testing as ‘Workflow 2’ and I want to include this workflow after the step of generating the file(s) in Workflow 1. Then all we need to do is:</p><ul><li>Open Workflow 1 in Workflow editor</li><li>Click on the step of ‘.apk’ (‘.ipa’) file generation</li><li>Click on the “Add workflow after” button from the above page</li><li>Choose the Workflow 2</li></ul><p>From next time, whenever, Workflow 1 is triggered, it will run both workflows.</p><p>Bitrise provides us many other features:</p><ol><li>Changing the owner of an app → Log in with current owner → On the Team tab of an App, click on ‘Transfer ownership’</li><li>Monitoring the logs/crashes</li><li>Configuring everything all this using a ‘.yml file’.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K6ZBlrv3Jy3RRyxRRE3pkA.png" /><figcaption>Configuration through Bitrise.yml file</figcaption></figure><p>A Step can also be Enabled/Disabled conditionally in Bitrise, using the ‘.yml’ file:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/893/1*6OXV9NFffn4cV1Ug-QvBDQ.png" /></figure><p>This and many other features are covered on <a href="https://devcenter.bitrise.io/">https://devcenter.bitrise.io/</a>. Thank you everyone for reading through this.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b4296dd4ac0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tide-engineering-team/bitrise-an-aggregator-for-mobile-apps-4b4296dd4ac0">Bitrise — An Aggregator for Mobile Apps</a> was originally published in <a href="https://medium.com/tide-engineering-team">Tide Engineering Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Technology? Manager? What is your forte’]]></title>
            <link>https://medium.com/@subhash.kotra/technology-manager-what-is-your-forte-8d967c1fa3cd?source=rss-2d9dabc5c481------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d967c1fa3cd</guid>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Subhash Kotra]]></dc:creator>
            <pubDate>Mon, 25 May 2020 09:57:30 GMT</pubDate>
            <atom:updated>2020-05-25T09:58:34.191Z</atom:updated>
            <content:encoded><![CDATA[<p>In India, for someone of the experience more than 12+ years of experience, often the most popular question asked by the Recruiters ask during the initial screening is:</p><p><strong>Are you a Technical Person or a Management Guy</strong></p><p>People like me, would answer as: “I am both”, the recruiter on the other end then gets puzzled and asks follow-up questions: “How, Why etc”. Often people don’t understand this so-called Title: “Technology Manager” in it’s true terms. So friends, Let’s deep Dive into it….</p><p>While my first few lines would look like me attacking the recruiters, but it is not. Maybe the fault is that of many individuals/teams/companies who want to move into management too early.</p><p>The drawback of this is poor managers who are not respected by their team members, I have come across many such individuals/managers in the past (No, I am not taking names, continue breathing 😊). At the same time, there are individuals who take-up management at a very early stage but never give-up on learning technicalities(In my experience, I have come across very few in this category, again NO Names please 😊). There is an increasing number of this second category now (Thanks to Agile) and is a definite need of the hour.</p><p>So, to all those who want to go in that direction, remember to never stop learning about new technologies. There can be a question here: “There is a new technology every now and then how do we cope-up”. Well, the simple answer is: “Try to pick-up from each and every person, learn from them, put your egos aside in asking questions and try to learn as much as you can”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/420/1*JA4ihXCVhWpWSdWof6saiA.jpeg" /></figure><p>Theoretical knowledge is good, but it’s not going to take you far, so we all must practice whatever we learnt. A Technology Manager should be able to sit with and try to resolve any issues his/her team is facing. I remember one-such scenario: where one of my VP’s (who had more than 200 team members reporting to him) on a random floor walk saw me breaking my head on something that I was working on it, he immediately came up to me (he never knew me personally before that), spent about 30 minutes understanding the issue and giving his 2 cents on the issue I was facing. I was just a junior engineer at that time and from then-on this person had gained immense respect in my eyes.</p><p>Situations like these is where we, as budding Technology Manager’s, have to thrive on, learn something new from the new generation, try to give some inputs (it’s immaterial if you could solve the problem but those few minutes would be great for both YOU and the Engineer). You’re wondering what is the conclusion? It is:</p><p><strong>LEARN, LEARN and continue to LEARN!!!</strong></p><p>I, personally, am still learning this skill and would continue to add to this topic, until then please excuse me for any mistakes in my first ever write-up and would be happy to receive reviews/critiques.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d967c1fa3cd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>