<?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 Lipika on Medium]]></title>
        <description><![CDATA[Stories by Lipika on Medium]]></description>
        <link>https://medium.com/@lipikadugar?source=rss-aa26604be59f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*OBWDq5wSs8Md7icLBMoryg.jpeg</url>
            <title>Stories by Lipika on Medium</title>
            <link>https://medium.com/@lipikadugar?source=rss-aa26604be59f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:06:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lipikadugar/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[Culinary Skills to Time Mastery]]></title>
            <link>https://lipikadugar.medium.com/culinary-skills-to-time-mastery-f08fd307ef82?source=rss-aa26604be59f------2</link>
            <guid isPermaLink="false">https://medium.com/p/f08fd307ef82</guid>
            <category><![CDATA[goals]]></category>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[planning]]></category>
            <category><![CDATA[prioritization]]></category>
            <category><![CDATA[scheduling]]></category>
            <dc:creator><![CDATA[Lipika]]></dc:creator>
            <pubDate>Wed, 27 Jul 2022 10:58:42 GMT</pubDate>
            <atom:updated>2022-07-27T11:00:43.870Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-eWYx4C50TirKHWQ.png" /></figure><p>Are you also one among them who want to finish their work on time with no stress and deviation? Have you been experimenting with various ways how to do it? We never seem to have enough time, yet we have all the time. The problem is not a shortage of time, but how we choose to use that time.</p><p><em>Here’s how you can Master your Time</em></p><h3>Attitude Matters</h3><p>Having the right attitude and developing the right habit to accomplish the task is the key to success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/0*6dSi42vwbSqr8Ii5.png" /></figure><p>Most of us choose the habit of what we feel good about rather than what’s good for us. However, when we choose a habit, we also choose the result of the habit. Hence, having the right habit will help us achieve self-discipline and self-discipline is simply doing what we know we should do regardless of whether or not we feel like doing it. Most of us only change when we are forced to do so either externally or internally.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*ZsqOiwwjiSLICceB.jpg" /></figure><blockquote>If we want something strongly we will definitely find the necessary discipline to do it.</blockquote><h3>Set your Goals and Prioritise</h3><p>Set yourself SMART Goals both long-term and short-term. Documenting these goals is the first step toward achieving your goal. As we say, only the Dreams written down with a Date and deadline become a Goal. Visualizing these goals and putting them on paper or on your computer will further help you analyze the details and organize them better. Long-term goals will help provide continuity and add meaning to short-term goals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sIsLpxOcvirH9QOrVN-7Pg.png" /></figure><p>I maintain a Daily To-Do List for my personal and professional work, which has helped me keep track of my short-term goals. Even if we think this is a small task, let’s add a To-Do for it, say replying to emails or buying groceries for that matter. Having this habit has made me more organized and moreover, I don’t need to remember anything now. I am free from mental pressure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/0*iulKDT3JyW4YB1Ey" /></figure><p>Once my To-Do is in place, I keep 10 minutes daily to revisit these tasks and set priorities. While setting the priority, it is essential to understand between the URGENT vs IMPORTANT. Most of the time we start with the quick, easy, enjoyable things first. Instead, we should start with the essential things. Remember just because something is Urgent, it might not always mean that it is important. Once we understand this difference, we will be more sorted. This way I know what I need to achieve by the end of the day and whenever I feel lost or get deviated, all I need to do is go back to my To-Do List and check the priorities.</p><h3>Planning and Scheduling</h3><p>Finally, in the verse of Time Management “Planning” and “Scheduling” are the two other major factors that play an important role. Flexibility is the key to better planning. We must be realistic and set our deadlines accordingly like how we estimate our story cards. There might be an unexpected situation. How do we handle such a situation? Has our planning gone wrong? Not, really! We must have room for these unexpected situations. In one of my interactions, someone rightly said, it does not matter how we overcame the situation or a crisis but what matters is how we respond to it. Even if the action may be correct, was it thought through, or was it a quick reaction to an event.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/0*3R2gquRpyZxZ7CU7.jpg" /></figure><p>The best time for planning your day’s activity is the night before and for a week is mostly Friday evening. Start doing this and see the difference yourself!</p><blockquote>While Planning is deciding what to do,</blockquote><blockquote>Scheduling is deciding when to do it.</blockquote><p>Scheduling is more like a Commitment and If you want it to happen, schedule it. Revisit your priority list and see what needs to be scheduled and when. Sometimes not very important work might need to be scheduled earlier. Be careful and decide accordingly.</p><blockquote>P.S: When conditions change, we may need to modify our goals and as we achieve the goals, we are all open to setting new ones.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f08fd307ef82" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Influencing: A child’s game]]></title>
            <link>https://lipikadugar.medium.com/influencing-a-childs-game-175035072761?source=rss-aa26604be59f------2</link>
            <guid isPermaLink="false">https://medium.com/p/175035072761</guid>
            <category><![CDATA[influencers]]></category>
            <category><![CDATA[stakeholder]]></category>
            <category><![CDATA[negotiation]]></category>
            <category><![CDATA[influence]]></category>
            <category><![CDATA[stakeholder-management]]></category>
            <dc:creator><![CDATA[Lipika]]></dc:creator>
            <pubDate>Wed, 29 Jun 2022 10:30:14 GMT</pubDate>
            <atom:updated>2022-06-29T11:46:33.370Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JSfT1Y2oBecQEl21SVZ55A.png" /></figure><p>Ever been in a tough spot to influence or persuade people around you? Looking to learn the best ways to influence people around you?</p><p>Well, if you ask me, influencing and persuasion skill starts getting built right from our childhood. Remember, as a child, we would try to influence our parents on how important the computer is for us, or persuade them to let us go to the fun fair or a college trip. It was never a YES as the first answer and we would use various different tricks and tactics to get what we want.</p><p>And now we are here trying to learn influence skills. You might be saying that influencing parents is different than influencing clients or stakeholders. Is it really? Are your parents not your stakeholders during that given point in time?</p><p>You would need to provide data points on why the computer is important to you, how would it eventually impact your performance and how can it lessen the burden on your parents in the long run for teaching them.</p><blockquote><strong>Principle 1: Make your stakeholders heroes in their story</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IV7CaNlBfmQ0obJv6ggJGQ.png" /></figure><p>We would know who would be easier to influence and who is important for us to influence on various matters.</p><p>For example, many of us would go to our elder siblings to get it communicated, for certain matters we would go to our father, and similarly on certain matters to our mother. How do you know or how do you decide whom to reach? And this brings us to our second principle of Influencing Skills.</p><blockquote>Principle 2: Pick and Choose</blockquote><p>Remember not everyone might be important at every stage. Prioritize who you want to influence first. At a higher level there are 2 types of characters at every stage of influencing:</p><ol><li>Non Playing Characters: Ones who are present but might not be interested in the current state of the discussion. You could use them at a later stage when needed.</li><li>Playing Characters or DMUs: The decision-Making unit or the Playing Characters need to be kept in the loop and is an important candidate to influence</li></ol><blockquote>Principle 3: Priorities Change. All stakeholders are important at different stages</blockquote><p>Again, remember to map all your stakeholders and figure out who is controlling the people and resources at this point in time. Refer to my blog <a href="https://lipikadugar.medium.com/stakeholder-management-a-piece-of-cake-514280759bef">Stakeholder Management</a> on how to map your stakeholders. Priorities of the stakeholders would continue to change over the period of time and hence continue to map your stakeholders at every stage to make a better decision.</p><p>Making assumptions is one of the biggest mistakes we do while trying to influence our stakeholders. We assume someone is already influenced and doesn’t make an effort to present. For example, for a few things when our grandparents have the highest influence on a few matters and we assume that they will anyway approve it. In this process, we plan everything and at the last minute, the proposal is denied.</p><blockquote>Principle 4: No Assumptions!</blockquote><p>One of the simple things that we would generally do is show that we are responsible. And we can do this by achieving smaller milestones like we would do our basic chores perfectly before showing our parents that we are capable to take care of ourselves. This would over time develop trust and becomes easier to influence. It then becomes a piece of cake to get any kind of approval.</p><blockquote>Principle 5: Small commitments build trust to gain larger commitments</blockquote><p>As a child, we would know what strategy would work best for someone. In fact even today, I am sure we would make use of the strategies that work well for someone and these strategies would change from person to person. Sometimes we make use of the emotions to influence while sometimes logic would work and sometimes a mix of these things. And this makes me introduce myself to the famous <strong>Rhetorical appeals</strong> of <em>Ethos (Credibility), Pathos(Emotions), and Logos(Logic).</em></p><blockquote>Principle 6: Identify what strategy works best for the stakeholder</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*hhoMeIs3qVal6OJWRxojjQ.png" /></figure><p>As I mentioned we have been practicing these influencing skills right from our childhood and almost daily in our lives, it’s time to apply the same with our client stakeholders in our professional space.</p><p>I have also covered the 6 most important principles of persuasion in my previous article on <a href="https://lipikadugar.medium.com/stakeholder-management-a-piece-of-cake-514280759bef">Stakeholder Management</a>.</p><h3><strong>Challenges of Influencing</strong></h3><p>Even after knowing all these principles of influencing, there might still be challenges while trying to influence people in a room. Influencing is in fact the toughest when there are people with different ideas in the room. Even if the end goal is the same, the process to the end goal might be different for everyone.</p><p>Understand that everyone in the room has an equal voice and authority. If there is an authoritative person in the room, then the power can be used to enforce a decision and one might need to influence only the one who is in power. However, this might not always be true. And in such a scenario one of the key concepts is <strong>NEGOTIATION.</strong></p><p>Having a negotiation contract that works in the favor of both parties is the only solution here. This is also called ZOPA(Zone of Possible Agreement).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1014/1*yoxsZgdz3Du9J08WwOnAQg.png" /></figure><blockquote>Active influencers always look towards the narrow possibilities of ZOPA by being the Anchor first when Infleuncing and Persuasion does not work</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=175035072761" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stakeholder Management: A piece of cake]]></title>
            <link>https://lipikadugar.medium.com/stakeholder-management-a-piece-of-cake-514280759bef?source=rss-aa26604be59f------2</link>
            <guid isPermaLink="false">https://medium.com/p/514280759bef</guid>
            <category><![CDATA[stakeholder-management]]></category>
            <category><![CDATA[persuasion]]></category>
            <category><![CDATA[stakeholder]]></category>
            <category><![CDATA[relationship-building]]></category>
            <category><![CDATA[influencers]]></category>
            <dc:creator><![CDATA[Lipika]]></dc:creator>
            <pubDate>Tue, 12 Apr 2022 14:55:59 GMT</pubDate>
            <atom:updated>2022-04-12T15:21:24.900Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Have you had difficulty handling stakeholders or did you avoid talking to stakeholders? Well, not anymore!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*Mw-qoZ4Pj8M9PfDd.gif" /></figure><p>Let us look at the thumb rules and basic principles for handling different stakeholders and winning their trust.</p><blockquote>Disclaimer: These are just the basic principles and will work for most scenarios. Also, this article is not about influencing or managing the conflicts with the stakeholders. I intend to keep the scope of this article limited to understanding the mindset of stakeholders, essentially learning how to and not what to.</blockquote><h4><strong>Principle 1: Know Who?</strong></h4><p>The first thumb rule even before managing your stakeholders is to understand <em>who your stakeholders are. </em>You should also understand their interest and influence level for your product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YS2KaDfho87sXT9RKRPMGQ.png" /></figure><p>Once the stakeholders are identified, shortlist the stakeholders who have <strong>High Interest and High Influencing Power</strong>. Remember the states of the stakeholders might keep changing as we progress with dealing with multiple stakeholders and over time interest or influencing power of the stakeholders may also change. So, the best way is to keep a tab on the stakeholders frequently possibly every sprint with the entire team.</p><h4><strong>Principle 2: The Key</strong></h4><p>When a team starts engaging with the stakeholders, one understands that the stakeholders are at point zero with the product details or the implementation i.e., they are unaware.</p><p>There are various stages that a stakeholder goes through in an engagement:</p><p><em>Unaware -&gt; Aware -&gt; Neutral -&gt; Supportive -&gt; Leading</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/633/0*6mpTO9ZMKmVoOnyI.png" /></figure><p>And the objective here is to make the stakeholders aware of the product and move them to the leading state. Well, how do we do that? This brings us to our second principle of stakeholder management <strong>“Relationship Building” and “Trust”</strong>. Staying authentic to our stakeholders and having frequent catchups formally or informally might help in having the base.</p><blockquote>Disclaimer: Relation building is very tricky and would vary from person to person and situation to situation.</blockquote><p><strong>Listen and Understand:</strong> Sometimes just hearing them out and understanding their point of view might just help. This would also ensure ruling out the assumptions. Ensuring that the stakeholders are also on the same page as you are is the key here.</p><h4><strong>Principle 3: Cracking the Nut</strong></h4><p>Aristotle has given us the <strong>3 modes of persuasion</strong> — Ethos, Pathos, and Logos. These are how a person can win over their audience. As we have already mentioned that not every person is the same and not the same trick would work for everyone. However, these 3 modes can be tried by various individuals and one can identify the best technique to convince or influence the stakeholders.</p><blockquote>Note: Having open-ended questions at the beginning of the conversation might help in unfolding the nature and culture of the stakeholders.</blockquote><p><em>Ethos (Credibility), Pathos(Emotions), and Logos(Logic)</em> are also known as <strong>Rhetorical appeals. </strong>You can read more about them <a href="https://en.wikipedia.org/wiki/Modes_of_persuasion">here</a>. Once we unlock the trick, all we have to do is find the right balance between the three modes and present the idea accordingly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*99zYVc7lrne2b3x5.png" /></figure><h4><strong>Principle 4: The Process</strong></h4><p>As we deal with multiple stakeholders, we are bound to take certain decisions. Stakeholders always want more and have weird asks. How do we make such decisions and have a win-win call? Well, the process of how these decisions are taken, counts. The mantra is to be agile and stay empathetic to stakeholders. <em>Make stakeholders the hero in their journey</em> and ensure that have the last word.</p><blockquote>Disclaimer: Being agile does not mean that we say “yes” to everything that stakeholders ask. It’s about collaboration and maintaining sustainability.</blockquote><p><em>What&#39;s in it for me? </em>— Every individual on this planet or maybe outside as well (if it exists) always thinks about the self-benefit first and then about others. Remember to talk about the <em>benefits the stakeholders </em>will get rather that the features of the product. You may have awesome features, fancy screens, the latest technologies, and everything but if none of these brings benefit to the stakeholders then the product is just like a Showpiece.</p><p>This takes me to talk about <strong>6 Principles of Persuasion</strong> that once can use to persuade the stakeholders:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mS9aHi7iM9S8oI5s.png" /></figure><ol><li><strong>Reciprocity: </strong>This works on the principle of returning the favors to people who have in turn done something in the past.</li><li><strong>Liking: </strong>The principle behind “Liking” is to be a little biased towards the people we like. Building a great rapport and trust develops the liking among the people</li><li><strong>Commitment: </strong>Ensuring that one has delivered what was said or committed. Commitment is all about achievements.</li><li><strong>Authority:</strong> Gaining confidence via authority. Essentially, people are likely to trust a credible and widely known source more easily than an unknown source.</li><li><strong>Social Proof/Consensus:</strong> Following the leader. This works on the principle of the fact that if something is working well for others, then it would work for me too.</li><li><strong>Scarcity:</strong> People tend to value things that might be going in scarce or maybe less available.</li></ol><h4><strong>Principle 5: Being Mean</strong></h4><p>Yes, that’s right…! Be mean and make use of existing stakeholders with whom you have built your trust to open up connections with other stakeholders. As I mentioned earlier, one must keep a tab and be <em>mindful of the state of various stakeholders</em>. This also helps in understanding where our stakeholders lie and who can we ask for favors to open up gates to other high-interest and high influential stakeholders. Remember, we have also talked about that there would be stakeholders whose interests and influence would vary based on time and situations. At the same time, we might also have stakeholders incoming and outgoing. In a nutshell, be mean and <em>leverage the existing connection to build new connections.</em></p><p>Before wrapping up, I would like to introduce you to the Types of Stakeholders we deal with in our day-to-day activity who are part of the Decision-Making Unit(DMU).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*C5-LK2no67AqZqFD.jpg" /></figure><ol><li><strong>Decision Maker:</strong> One who has the final say in an organization</li><li><strong>Influencers: </strong>These are the ones who persuade others or make recommendations based on experience and their knowledge of the product.</li><li><strong>Gatekeeper: </strong>Gatekeepers are the ones who have the authority to press the stop/to go button and provide their inputs to the decision-makers.</li></ol><p>Voila! You now know all the tricks to understand the mindset of stakeholders and the key mantras to manage your stakeholders better. Apply these principles and do let me know in the comment section how this has helped in managing your stakeholders.</p><p><em>#TWBloggersClub</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=514280759bef" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Testing Cloud-Native Applications]]></title>
            <link>https://lipikadugar.medium.com/testing-cloud-native-applications-a325b4c0077d?source=rss-aa26604be59f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a325b4c0077d</guid>
            <category><![CDATA[cloud-native-application]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[cloud-native]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Lipika]]></dc:creator>
            <pubDate>Sun, 07 Mar 2021 05:55:16 GMT</pubDate>
            <atom:updated>2021-03-08T07:01:00.387Z</atom:updated>
            <content:encoded><![CDATA[<p>We have been hearing the term “Cloud Native” quite very often but what exactly is this Cloud Native and how does it impact the Testing Strategy? In this article, I will try to explain the basics of Cloud Native, highlight some of the key features that need to be taken care of while designing the Test Strategy for Cloud-Native Applications and how can Cloud-Native help in Testing an Application.</p><blockquote>Cloud Native app is an approach to building and running applications which uses the cloud computing delivery model. It helps in running scalable applications.</blockquote><h4>It is also now considered to be the future of App Development and 28% of our applications are likely to be migrated to Cloud-Native by 2022.</h4><p>With Cloud Native Architecture being actively adopted for Software Development, Quality Analysts should also start working towards this.</p><p>Before going towards the Testing Approach for Cloud-Native Applications, let’s first understand the difference between monolithic architecture and cloud-native architecture.</p><h4>Monolithic Architecture vs Cloud-Native Architecture</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5P3ulWkXADbfOFS6JY3u3w.png" /></figure><p>Monolith Architecture is the traditional model of app development where all the components are tightly coupled. For a small functionality change, we need to redeploy the entire application which would take a lot of time for the deployment process hence becoming a tedious job even for the QAs to perform regression on the entire application. And because deployment takes a lot of time, most likely deployment is done once in 6 months.</p><p>On the other hand, Cloud Native is pretty much the opposite of Monolithic Architecture. <strong>Every component called containers in Cloud Native</strong> is loosely coupled and is independent of each other. These containers are then connected via the cloud. Since every component is independent of each other, it becomes very easier to maintain and becomes a shared responsibility to manage. In Cloud Native for a small functionality change we just need to make changes to the existing component and deploy the same. Even QAs can focus on the respective component.</p><p>In Cloud Native, it is always believed to release early and often. Other major advantages of having Cloud-Native are its ability to scale and freedom to choose the tech stack.</p><h3>Testing in Monolith and Cloud-Native Architecture</h3><p>Now that we understand the difference between Monolith and Cloud-Native, let’s understand how is testing different in these architectures.</p><p>Testing in monolith architecture is a process to verify a product after a feature or functionality is developed and before it gets deployed to production.</p><p>While in Cloud-Native Apps since everything is hosted in the cloud, we testers need to be alert all the time. Testing should be a Continuous Process. QAs need to test every stage of the Software Development Life Cycle be it a small bug fix or a functionality change. After every build, developers can push the changes to the cloud, and we can test them immediately and independently. Not only in the dev environment QAs can perform the testing during deployment and even after the product is released in Cloud Native Architecture.</p><p>Essentially, We “QAs” are always testing. So, With Cloud Native apps we know we will never run out of work and our job is secured 😜</p><blockquote>We can also say that development and testing in Cloud Native happens at a common place. Well, honestly it’s just a common server that is used!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VGOjXlxF6Zdq5MqgSrHPzQ.png" /></figure><h3>Testing Approach for Cloud-Native Applications</h3><p>In general, While designing a testing strategy or coming up with a testing approach one needs to understand certain features of a technology. Similarly, Cloud Native has a certain measure that we need to focus on while coming up with a Test Plan. These measures not only ensure the better development of the application but also ensures efficient and effective testing.</p><h4>Measures in Cloud-Native Apps and Approach to testing</h4><ol><li><strong>Scalability: </strong>Scalability is the ability to scale the containers or pods based on the real-time requirement.</li></ol><p>For instance, during Big billion days or any sale on e-commerce, there is a sudden spike in the number of users. So it is required to ensure the containers are automatically scaled up to incur such heavy demand based on Data storage capacity or processing power and also it auto-scales down when the usage is less.</p><p>As QAs, some of the basic scenarios to cover here would be</p><ul><li>What happens when instances are no longer required?</li><li>How is the service scaled?</li><li>How is traffic routed when nodes are overloaded?</li></ul><p>In such Auto Scaling testing, watching out for any memory leak becomes a key point here and to verify if all the threads are being closed with proper logging and CPU Utilisation.</p><p><strong>2. Resiliency: </strong>The second measure is Resiliency. It is the ability to recover any failed container or cluster without losing the state.</p><p>To take an example, consider a user is in the middle of the payment and suddenly the app crashes. In such a scenario proper load balancing is required and redirecting to the “Disaster Recovery Cluster” to ensure that there is no impact on the user’s experience in terms of functionality or performance. This also helps in maintaining the impact of the cost associated with the business.</p><p>Handling the failure scenarios to have a resilient system should be the focus here:</p><ul><li>Does the system degrade gracefully?</li><li>Can we still respond to user requests if legacy systems are unavailable?</li><li>Kubernetes can perform rolling restarts and ensure the automated spin up for disaster Recovery clusters in such scenarios.</li></ul><p><strong>3. Robust Deployment: </strong>When planning out the automation efforts for cloud-native apps, the team should focus on the valuable areas and not focus on automating everything. Since time is limited, it clearly will not be possible or add value to automate everything.</p><p>The focus should not be on large unmaintainable, unreliable regression packs that add no value but smart test packs that can:</p><ul><li>simultaneously validate a deployment, and</li><li>perform a selected set of functional tasks</li></ul><p>This type of automated regression will add a constant value to the development effort and accordingly can be expanded or reduced as the product matures.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sghokN_7VFZ2WcaHdgUJ9w.png" /></figure><p><strong>4. Resource Utilisation: </strong>In traditional applications, operations teams would manage the infrastructure resource allocations manually. This is a tedious job and requires heavy maintenance.</p><p>In cloud-native applications Resources are utilized automatically via a central orchestrating process that dynamically manages and schedules containers. Since this is based on certain rules set by dev ops, we need to ensure the balanced loads are maintained otherwise it can result in low resource utilization or increase the response time of tests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e0Iyvw6WC47p8Ch85KeBGQ.png" /></figure><p>This reduces the costs associated with maintenance and operations.</p><h4>CLOUD NATIVE AND SOFTWARE TESTING</h4><p>While much of the functional aspects don’t change too much, the cloud offers and sometimes requires very different ways to meet non-functional requirements especially while developing the application. Cloud-Native helps testing apps in a better way.</p><p>Let’s look at how Cloud Native helps in achieving</p><ul><li>E2E Automation</li><li>AB Testing</li><li>Performance Testing</li><li>Security Testing</li></ul><p><strong>1. E2E Automation: </strong>Selenium Grid is mostly used to achieve end-to-end testing in Traditional Model. Also, in Selenium Grid, we have come across a very common error while automating tests which is <em>“Error communicating with the remote browser. It may have died</em>” or<em> “UnreachableBrowserException”</em></p><p>Deploying browsers using Cloud Native say with Kubernetes brings in all the advantages like the Self-healing feature which is nothing but automatically spinning up the mode or pod when it goes down.</p><p>From a scalability perspective — with just one command called “Replicas” we can scale to any number of browsers we need (which may not be the same in other technologies)</p><p><strong>2. AB testing:</strong> AB testing is nothing but releasing a version of the Product to a Specific Set of Users. AB testing ensures while there is zero downtime one can test a feature with real-time production users and also monitor the traffic. QAs play a vital role especially while selecting the target audience and run the tests for a reasonable period to reach a statistical significance of at least 95%.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/0*1rKcpP4KhX5OmFGh" /></figure><p>When performing an AB test, we route a subset of users to new functionality based on routing rules. Routing rules often include factors such as browser version, user agent, geolocation, and operating system. Based on the various factors and measuring which version produced the better results, the production environment can then be upgraded to the same version.</p><p><strong>Key challenges for AB Testing:</strong></p><p>Several factors can skew the test results, including false positives, <a href="https://wikipedia.org/wiki/Sampling_bias">biased sampling</a>, or external factors (such as seasonality or marketing promotions).</p><p>Observability can potentially be a challenge when we perform such testing. When we run multiple AB tests on overlapping traffic, the processes of monitoring and troubleshooting can be difficult. To put it in simpler terms, if we test product page A versus product page B, or checkout page C versus checkout page D, distributed tracing becomes important to determine the metrics.</p><p><strong>3. Performance Testing:</strong> Performance Testing in Cloud-Native Apps is a challenge here.</p><p><strong>Fundamental Shift of Approach: </strong>For monolith applications, we have always been hitting URLs to do the performance testing but for Cloud-Native Apps hosted in the cloud with various containers; instead of hitting the URLs we would now look at the Cluster or Containers performance. So we are now moving from the URL approach to Container-based performance. I would not say that we do not hit URLs but something that we need to consider in Cloud-Native Apps is the<strong> Performance of the containers which is the core of this architecture.</strong></p><p>For better performance in Cloud Native Application, Load Balancers are configured to ensure that requests are sent to various nodes based on their configuration or rules. Although everything is automated here, observing the logs and keeping track of the container logs is also required to ensure an effective troubleshooting mechanism.</p><blockquote>Preparation of right set test data is crucial to analyze the results correctly.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/436/1*e3e30Cozv_75HzGNku9shg.png" /></figure><p><strong>4. Security Testing: </strong>Nowadays, all or most of the applications are hosted in the Cloud and since everything is hosted in the cloud security of the applications is at stake as most of the applications have highly sensitive data.</p><p>The main objective of Cloud-based security testing is to stop any threat or malware from accessing, stealing, or manipulating any of the sensitive data. It is responsible to identify any of the threats measure their potential vulnerabilities. One advantage with cloud-based application security testing is that it can be applied to the large application, applications with low to medium risk, and even to applications with a strict budget or time restrictions</p><p>Cloud-based Application Security Testing also provides the feasibility to host the security testing tools on the Cloud for testing. In traditional testing, we need to have on-prem tools and infrastructure to perform any kind of testing. With industries adopting Cloud-based testing techniques, the processes have also become faster and cost-effective.</p><h3>New Era for QAs</h3><p>With applications being upgraded towards Cloud Native apps we QAs also need to upgrade ourselves. Testing has always helped us build applications that are more maintainable, debuggable, reliable, and performant allowing us to ship faster with more confidence.</p><p>But as applications have become more and more complex, new types of failure modes have been introduced which are becoming more difficult to anticipate or troubleshoot. To efficiently detect, debug and fix them, we should review how we can use traditional testing techniques to embrace the new ones and apply them to all stages of the development lifecycle. Only then testing can return to be the valuable ally as it once was in delivering high-quality software.</p><p>Special Thanks to Manoj for guiding me through this topic :)</p><p>If you enjoyed reading, please do support with claps &amp; share.</p><p>Do share your thoughts in the comments section!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a325b4c0077d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A World without QAs]]></title>
            <link>https://lipikadugar.medium.com/a-world-without-qas-2280683f5eb1?source=rss-aa26604be59f------2</link>
            <guid isPermaLink="false">https://medium.com/p/2280683f5eb1</guid>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[qa-testing]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <dc:creator><![CDATA[Lipika]]></dc:creator>
            <pubDate>Sat, 20 Feb 2021 06:53:31 GMT</pubDate>
            <atom:updated>2021-02-22T06:17:02.667Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/626/0*c2JlBIRnmsr3nQZd" /></figure><blockquote>‘Biggest Blunder in Banking History’: Citibank Wired $900 Million to Lenders by Mistake.</blockquote><p>We all know how Wire Money Transfer has made life easy for all of us. But, a bank as big as Citibank made a wrong money transfer worth $900 million.</p><p>Software Systems are a great blessing and solve so many problems, but if they misbehave, they can create major issues. Each software failure costs money in the time spent fixing it, in halting production, in lost revenue, or in another way.</p><p>In today’s world, we’re heavily dependent on software systems for our financial management, investments, healthcare, shopping, dining, and a lot more. If something as critical as the hospital management system misbehaves, it could cost lives.</p><p>Let’s imagine what could happen if software systems did not work as expected -</p><ol><li>I am unable to send messages on WhatsApp</li><li>I am unable to access my bank account</li><li>My phone has suddenly stopped working</li><li>My car‘s horn is not working</li><li>I cannot order food on Zomato or Swiggy</li><li>Uber/Ola apps do not let me book a cab</li></ol><p>There can be countless such examples and the list is surely never-ending.</p><h3><strong>Ain’t Developers the best QA?</strong></h3><p>“It works on my machine,” said a developer and we frequently come across such cases in the software world.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JnKM1s0MZcvfY3ku" /></figure><p>A developer does a great job in developing products and it does work well on their machine. Imagine if the code working on the developer machine were shipped to production?</p><h3>Why QA should be done by QA experts</h3><p>Quality Assurance is not about just validating that the system is performing how it should be. It is also about assuring that the system isn’t performing in ways it shouldn’t be. An expert QA tester can delicately go about pushing a system to (and beyond) its limits to ensure quality and appropriate functionality.</p><p>Quality assurance testing includes:</p><ul><li>a critical approach to the project, often missing in the developer’s tests. Testing is a creative, destructive process in which every aspect of a project is carefully looked at and picked apart to ensure it works how it’s expected and supposed to.</li><li>more than just a post-programming evaluation. QA should be an integral part of each phase of the systems development life cycle (SDLC).</li><li>searching for the flaws in the project. This requires a neutral and objective set of eyes and critical analysis to find anything that might go wrong.</li><li>providing truthful feedback to the customer while demoing presentations that help to stay on the same page during SDLC.</li></ul><p>A dedicated QA engineer brings a fresh perspective and interacts with the product features the way a new user would. A person with experience in QA will try to break the application, finding the faults in the system long before any user is exposed to them, which is exactly what you want to happen during the testing of your product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/473/0*v9zVwUSI8SzLEEOF" /></figure><p>We’ve all come across jokes like above, but the bugs that these QA Testers find are important and can be critical at assuring the software’s quality.</p><h3>QA is invaluable</h3><p>The importance of quality assurance may not be evident, but it is invaluable. Think of QA as a water filter, finding and fixing the impurities in your tap water. Even though you might not easily be able to see these impurities, they are there and they can make you sick. This is what QA does for software development. Even if the flaws are not evident, it is important to test for, find, and fix them before they make the software sick or broken.</p><p>A product that hasn’t been tested may look okay at first glance, but once you start to scrutinize it, you find the issues that should have been filtered out. This is the value that QA provides and this is why it is such a critical and highly recommended part of software development.</p><p>Do share your thoughts in the comments section!</p><p>If you enjoyed reading, please do support with claps &amp; share.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2280683f5eb1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I’m working from home, Now What? Here’s my experience with Remote Working]]></title>
            <link>https://lipikadugar.medium.com/im-working-from-home-now-what-here-s-my-experience-with-remote-working-12380e8d56de?source=rss-aa26604be59f------2</link>
            <guid isPermaLink="false">https://medium.com/p/12380e8d56de</guid>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[thoughtworks]]></category>
            <category><![CDATA[motivation]]></category>
            <category><![CDATA[corona]]></category>
            <category><![CDATA[work-from-home]]></category>
            <dc:creator><![CDATA[Lipika]]></dc:creator>
            <pubDate>Mon, 23 Mar 2020 09:21:07 GMT</pubDate>
            <atom:updated>2020-03-24T05:07:11.450Z</atom:updated>
            <content:encoded><![CDATA[<p>It all started 6 months back… actually post my wedding. Very new and very different experience. No people to talk around, no one to discuss, it was all getting void.</p><blockquote>I was clearly seeing an end to all the chit chats during breaks, those extra shots and extra gossip post client calls.</blockquote><p>And now… I talk to only a limited set of people with a defined agenda. It’s been 6 months and things have changed. Yes, I switched to working from home post my wedding. I have close to 5 years of experience now and honestly, I am the kind of person who would be in the office even during weekends 😉. And now here I am completely working remotely from a different city altogether.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D2HASKEUldIZ5SmjqteOZQ.png" /></figure><p>When I go back to those initial few weeks of my Remote Working, I was completely lost. <em>Even then I had to keep up my motivation level high. </em>Those days I was even struggling to get a project which would support work from home for a longer time. I was on the beach(bench as it is referred to in the industry) for almost a month (Well, I had never been on the beach in the last 4 years). In fact, I had also made up my mind to quit if this didn’t work and figure out something else. But thanks to many people in <a href="https://www.thoughtworks.com/">Thoughtworks</a> who didn’t give up and said: “Let’s wait we’ll find something for you”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ig_nSemwnxvMdpWZbo-hIw.png" /></figure><p>And then… I was assigned temporarily for a month to a project. Although I was happy that I was assigned to a project, the struggle continued even then. There were times I felt disappointed being away from the team, missing out on all the bench talks, team lunches, office activities and lot more. Thanks to my Project Manager <a href="https://www.linkedin.com/in/ruchika-bhargava-40350913a/">Ruchika</a> and all the team members for constantly making an effort to not make me feel away from the team.</p><blockquote>Well, I was a satellite team member (one and the only one working remotely, I learned the term very late 😁).</blockquote><p>In just a couple of months, I finally got used to my Working from Home culture. I actually started finding positives in working from home and various ways to overcome the challenges of Remote Working majorly of which it was the feeling of being disconnected. <strong>I was back in the game again 🤘</strong></p><p>Thanks again for all the support that I received from Thoughtworks and my family especially my husband. Honestly, I never felt any difficulty from the personal front with everyone being so supportive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YBDG2YP7zL5x_vki-Qz5Zg.png" /><figcaption>Team Lunch, Coimbatore</figcaption></figure><p>It’s been close to 5 months now in the project and since then I have traveled twice to my work location Coimbatore to be in the office. Really found fruitful to meet people in person. I was almost planning my third visit when the <strong>COVID-19 Corona Virus</strong> outbreak happened and every one of us has now landed in a distributed team. We all have started working from home to ensure Social Distancing. I have been through the challenges of working from home and with everyone being remote, it has become really challenging for the organization. I had time to overcome the challenges but with this sudden outbreak, each one of us is dealing with various challenges. Moreover, the company as a whole is facing various challenges globally.</p><p>Kudos to everyone in Thoughtworks especially the leadership team for their prompt decisions and benefits offered (we have been given the extra benefit of 5k to support Remote Working).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NyIHey23czf0367X-Wk7Tw.png" /><figcaption>Day 1 of Remote Working</figcaption></figure><p>We are now in our second week of Remote Working Challenge and it’s very overwhelmed to see the way all Thoughtworkers have handled this situation from talking about various challenges to all the positives of working from home.</p><h4>Examples:</h4><p><em>“I’m at home 24/7 looking after my family, but this time I’m not on break… I’m still working :D”</em></p><p><em>“Got time to spend with family, getting time to learn new skills. Take care of my health and able to give more productive time to work as no travel to work in crazy traffic. A lot of positive in these situations too.”</em></p><p><em>“Not having to commute through Bangalore traffic.”</em></p><p><em>“Actually it has been very good. Just realizing how important small things in life are. Like having home-cooked food. Going for a walk every day morning with parents. With no stress of commuting to the office every day, work has also been going smoothly. I have taken up dance practice after years. Might get used to this routine :P”</em></p><p><em>“Improving cooking skills. More workout, less stress. Better productivity. Gave some attention to my plants. Cleaned my almirah. Arranged the Kitchen. Got to know current rates of things in the grocery market. Dressing comfortably. I can just go on and on.”</em></p><blockquote>It really feels great to stay motivated and listen to these positive vibes.</blockquote><p>Well, we also have lunch sessions, morning workouts, cooking classes, team fun activities, and many more being organized remotely to keep up our motivation levels.</p><p>All I would want to say is I know it’s challenging but in this tough time where the entire world is going through the phase of Covid-19, we are just a small part of this.</p><p>Let’s be positive, stay motivated and together let’s overcome it 🙂</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*76K2tdCrwcZWNkQwhYK43Q.png" /><figcaption>Together we can make a difference!</figcaption></figure><p>Do you have a story to tell? Please do share and join the challenge!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12380e8d56de" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Challenges in Testing Blockchain Application]]></title>
            <link>https://lipikadugar.medium.com/challenges-in-testing-blockchain-application-ca8103f6fc81?source=rss-aa26604be59f------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca8103f6fc81</guid>
            <category><![CDATA[blockchain-application]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[blockchain-technology]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Lipika]]></dc:creator>
            <pubDate>Sun, 22 Dec 2019 03:49:20 GMT</pubDate>
            <atom:updated>2019-12-22T03:49:20.766Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>The data volumes are exploding, more data has been created in the past two years than in the entire previous history of the human race.</blockquote><blockquote>There are 2.5 quintillion bytes of data created each day at our current pace, but that pace is only accelerating with the growth of the Internet of Things (IoT)</blockquote><p>With this rate, we will all be surrounded with just data. Multiple technologies/tools have been introduced to store and analyse such data. While there are multiple tools that have been introduced to process such huge data, securing the data becomes a key in this world of the internet. Blockchain is one such technology that is used to store such huge data keeping security in mind.</p><p>If you are new to Blockchain technology, please refer to my <a href="https://blog.usejournal.com/can-blockchain-solve-iot-concerns-dff3ed616e0e?gi=1588a164f4e8">previous article</a> to understand the <strong>Basics of Blockchain</strong>. As of today, Blockchain is often discussed or used majorly in providing financial services or cryptocurrencies. However, Blockchain offers a lot more and has the potential to expand its scope to various other services like healthcare, media, retail, communications and lot more.</p><p>Most of the industries have already adopted Blockchain as its technology which brings a huge responsibility to the Testing Industry as well. Blockchain in itself bring huge challenges in Testing World due to its concepts and the amount of data it is expected to handle.</p><h3>Key Challenges</h3><p>Let’s focus on the top 10 key challenges that are likely to be faced while Testing a Blockchain Application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AAaT5ZI0BpA33dv8UqwZQQ.png" /><figcaption><strong>Key Challenges in Testing Blockchain Application</strong></figcaption></figure><ol><li><strong>Understanding the technology: </strong>Blockchain is a relatively new technology and needs to be understood in depth before adopting Blockchain as a technology for an application to be built. Technical expertise along with domain knowledge is very important in testing Blockchain Application</li><li><strong>Testing Tools:</strong> There are quite a few testing tools in the market that can be used to test the Blockchain application. However, picking up the right tool as per the application is a crucial decision. This again depends on knowing the pros and cons of each tool. <br><a href="https://www.trufflesuite.com/docs">Truffle</a>, <a href="https://github.com/ethereum/eth-tester">Ethereum Tester</a>, <a href="https://bitcoinj.github.io/#documentation">BitcoinJ</a> and <a href="https://embark.status.im/docs/quick_start.html">Embark</a> are some of the popular tools used to test Blockchain Application</li><li><strong>Lack of Experience/Skills: </strong>Blockchain technology was first introduced in 2008 by Satoshi Nakamoto in the form of Bitcoin. However, it has not been widely adopted in the industry due to a lack of experience and skills. This makes testing a challenging task.</li><li><strong>Defining the Test Strategy:</strong> Defining the test Strategy for Blockchain is like any other application that keeps a few parameters in mind. Like any other application, coming up with Test Strategy for Blockchain Technology requires a deep understanding of the application, its usage and the technology itself.</li><li><strong>Addition of Blocks: </strong>Blockchain technology is meant to be used to store and process huge amounts of data and as this increases blocks continue to get added. Handling such a testing scenario brings in a lot of test cases to be considered. With such huge data getting added every second, the addition of blocks is likely to happen at a similar pace. Well, the complexity of block addition can be self-understood.</li><li><strong>Block and Chain Size: </strong>Testing the size of the block and chain is an important aspect for the blockchain application. This requires a proper validation of the data being added.</li><li><strong>Transmission of crypto-graphical data: </strong>The main crux of the Blockchain Technology is the transmission of encrypted data. There is high risk of failure in case the transmission of data is not properly tested.</li><li><strong>Integration Testing: </strong>This is self-explanatory. Since there are multiple components involved in designing the Blockchain application, one must ensure that all these are integrated properly. Hence, integration testing must be carried out frequently to avoid any failures.</li><li><strong>Security Testing: </strong>Well, security testing is yet another aspect of testing Blockchain application. As mentioned earlier, securing the data should be the utmost priority. Blockchain technology can be used in various sectors like Health, Banking, Finance, Education, etc and any kind of security breach would eventually lead to a huge loss.</li><li><strong>Performance and Load Testing: </strong>Performance and Load testing for a Blockchain application would essentially mean the amount of data that can be added in a block, size of the chain, how fast and accurate a miner can validate the transaction using “Proof of Work” algorithm.</li></ol><p>To conclude, like any other application testing Blockchain application also requires the right set of skills and understanding to come up with the Testing Strategy. Most importantly, non-functional testing becomes a key challenge here.</p><p>If you find this article to be useful, do give a thumbs up and if you have anything to share, please leave a comment.</p><p>Thanks, Stay tuned for another article to further deep dive into Blockchain technology!</p><p>Check out my other articles <a href="https://medium.com/@LipikaDugar">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca8103f6fc81" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Can blockchain solve IoT concerns?]]></title>
            <link>https://lipikadugar.medium.com/can-blockchain-solve-iot-concerns-dff3ed616e0e?source=rss-aa26604be59f------2</link>
            <guid isPermaLink="false">https://medium.com/p/dff3ed616e0e</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptography]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[iot]]></category>
            <dc:creator><![CDATA[Lipika]]></dc:creator>
            <pubDate>Mon, 16 Jul 2018 03:01:59 GMT</pubDate>
            <atom:updated>2018-07-17T18:19:16.899Z</atom:updated>
            <content:encoded><![CDATA[<p>Over the time <a href="https://blog.usejournal.com/is-iot-really-worth-the-buzz-947a1d50422d">IoT</a> has faced a lot of criticism, especially around security and data privacy. IoT collects the data and stores it in the cloud to be used by the devices over the internet. IoT devices have now been the easy targets for the Hackers. As the devices tend to grow and collect more data, hackers have become more hyperactive in identifying the potential threats and vulnerabilities. So now, what next? Are we ready to face the consequences? Is there any solution to solve the increased IoT concerns?</p><p>With all these questions and curious to find the answers, something really caught my eyes on.! Yes, it was <strong>Blockchain</strong>. Blockchain has already caught many eyes from different stakeholders especially after the launch of very popular cryptocurrency <a href="https://bitcoin.org/en/">Bitcoin</a> by <a href="https://en.wikipedia.org/wiki/Satoshi_Nakamoto">Satoshi Nakamoto</a>. After the launch of Bitcoin, many cryptocurrencies have been introduced in the market based on Blockchain technology.</p><p>Blockchain has a lot of applications other than building cryptocurrencies. Most of the organizations have already started implementing this new technology.</p><p>Let’s understand the basic concepts of Blockchain and what makes it so special.!</p><blockquote>In simple words, I would describe <em>Blockchain as an evergrowing ledger.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tL2V_doUOrRfKlkW.png" /><figcaption><a href="https://scet.berkeley.edu/future-blockchain-berkeley-perspective/">Evergrowing blocks in a blockchain</a></figcaption></figure><p>Technically speaking,<em> </em>Blockchain is a chain of hundreds and thousands of blocks linked together using cryptography where each block maintains the cryptographic hash of the previous block, timestamp, and the transaction details.</p><h4>Blockchain Structure &amp; Concepts</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MkVDtWso_eptD2Lult5Fxg.png" /><figcaption>Structure of BlockChain</figcaption></figure><p><strong>Genesis Block —</strong> The first block in the chain of blocks is referred to as the Genesis Block. Essentially it is the root of the chain.</p><p><strong>Cryptographic Hash —</strong> A cryptographic hash is an encoded number. There are many algorithms to generate a secured cryptographic hash. Each block contains the hash of its previous(parent) block.</p><p><strong>Transaction —</strong> A transaction is all the information needed to perform the transaction — sender info, receiver info, documents(if any), other transaction details, etc.</p><p><strong>Block Time —</strong> Block Time is very crucial measure in the Blockchain technology. This is the time taken by a block to be added in the Blockchain. This determines the performance of the Blockchain technology. Bitcoin takes ~10min while <a href="https://www.ethereum.org/">Ethereum</a> takes just 10s–15s.</p><h4><strong>What forms the base of trust?</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*O9BhLPwC9CQsQA6d.gif" /><figcaption><a href="https://dribbble.com/shots/4032985-Evil-Hacker">C</a>an you trust?</figcaption></figure><p><strong>Proof of Work —</strong> One of the major key concepts behind Blockchain technology is the “Proof of Work”. Proof of Work ensures the authenticity of the transactions. Each block undergoes validation stages under “Proof of Work” algorithm to decide the eligibility of the block to be the part of the blockchain. Once a part of the blockchain, neither can the transaction rollback nor can the block be deleted from the chain.</p><p><strong>Miners and Transaction Fee —</strong> A miner is a real-world person who validates the transaction by solving a complex mathematical problem. Miners compete to solve the problem based on “Proof of Work” algorithm. Only when a block is solved, the transitions are considered valid and is confirmed. Higher the number of miners the more likely the transactions are to be secured.</p><p>Every miner receives a reward for solving the block in terms of the transaction fee. Ethereum uses “Gas”, a measuring unit to calculate the transaction fee. The time taken by such operation to carry is nothing but the “Block Time” as mentioned earlier.</p><p><strong>Smart Contracts — </strong>Along with “Proof of Work”, Smart Contract is the heart of the Blockchain Technology. A smart contract is a set of protocols between two parties/individuals that need to be followed while carrying out a transaction. There is no place for the third party in <em>Smart Contracts</em>. Such transactions are highly reliable and irreversible.</p><p><strong>Centralised Private Blockchain —</strong> While the Proof of Work algorithm validates the eligibility of each block, centralized Private Blockchain adds an additional layer of validation to decide the rights for making the changes to the Blockchain ledger. These involve fewer resources and less computational powers due to the limit in the number of the participating miners. Centralized Private Blockchains are less secure as compared to Public Blockchains due to the involvement of fewer miners.</p><p><strong>Decentralised Public Blockchain — </strong>Decentralised Public Blockchain offers transparent transactions between the parties. No single party or organization governs the transaction performed under Decentralised Public Blockchain. Since there is no control over the network, these require heavy computational powers and need a lot of resources. However, these are more secure than the Centralised Private Blockchains.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*bpqi3qEorZiihzB6.png" /></figure><p>The blockchain technology is sure to make the data and transactions more secure. The technology involves stronger security design which includes cryptographic hashes, Proof of Work algorithms and Decentralisation concept.</p><p>Is it really something that we can consider while designing the IoT devices? Well, we never know..! There is a lot more coming in. Do leave in your thoughts in the comments section.</p><p>Stay tuned to know more about Blockchain.! As I said there’s lot coming in ;)</p><h4>More where this came from</h4><p>This story is published in <a href="http://blog.usejournal.com/">Noteworthy</a>, where thousands come every day to learn about the people &amp; ideas shaping the products we love.</p><p>Follow our publication to see more product &amp; design stories featured by the <a href="https://usejournal.com/?utm_source=usejournal.com&amp;utm_medium=blog&amp;utm_campaign=guest_post">Journal</a> team.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dff3ed616e0e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Thinking Workshop — Sharing Experiences]]></title>
            <link>https://lipikadugar.medium.com/design-thinking-workshop-sharing-experiences-7be14698be42?source=rss-aa26604be59f------2</link>
            <guid isPermaLink="false">https://medium.com/p/7be14698be42</guid>
            <category><![CDATA[ideo]]></category>
            <category><![CDATA[thoughtworks]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[prototyping]]></category>
            <dc:creator><![CDATA[Lipika]]></dc:creator>
            <pubDate>Wed, 04 Jul 2018 05:13:18 GMT</pubDate>
            <atom:updated>2018-07-17T10:43:02.754Z</atom:updated>
            <content:encoded><![CDATA[<p>Design Thinking Workshop! Sounds too creative and XD kind of thing, isn’t it?</p><blockquote>Wikipedia defines Design Thinking as “creative strategies <strong>designers</strong> use during the process of designing.”</blockquote><p>Designers? Are you thinking the same…? Well, even I did until I attended the Design Thinking Workshop organized by <a href="https://www.thoughtworks.com/">ThoughtWorks</a> last month. By the way, before I get started, let me tell you that I’m a QA by profession and nowhere related to XD.</p><p>The workshop has truly added value in making me understand the process of Design Thinking and how important it is for every member of the team. There are hundreds of blogs and resources explaining the concepts of Design Thinking, but hands-on sessions organized during the Workshop justified it all.</p><h3>So, what is design thinking?</h3><p>Design Thinking is an iterative process of understanding the user, identifying the problem statement, ideating over the solutions and building the product with the continuous help of users. Design thinking helps in problem-solving keeping users’ in mind and not necessarily meant only for <em>designers</em>.</p><h3>Five Stages of Design Thinking</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/448/1*dpJwU-ofTNUK5N03OlZqfg.png" /></figure><h4><strong>Empathise</strong></h4><blockquote>It is not about the product and what you have built. It’s all about who have you built the product for and why have you built it.</blockquote><p>Understanding the users and close interaction with them reduces the chances of having unlikely assumptions which otherwise might result in the failure of the product. One needs to empathize with the user and explore more about their experiences.</p><p><strong>User Research — </strong>This involves researching the potential users of your product most likely by interviewing, observing and sometimes even analyzing the competitors in the market.</p><p>User Research primarily focuses on answering some of the following questions:</p><ul><li>What is the thinking process of a user while using the product? How do they feel or react?</li><li>What are their needs, pain points, and motivations?</li><li>What are the users looking for? What medium are they using to reach that goal?</li></ul><p>The more you interact with the users with different backgrounds in different circumstances, the more likely you are to understand the users.</p><p><strong>Personas — </strong>After a detailed user research, divide the users into different groups based on the common goal, common pain point, etc. Creating such a representation is called <em>Personas. </em>Teams generally put up these personas near the project table to constantly remind themselves about <em>“Who are they building the product for?”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sn0PcFnZ9CPbtBWBstz1Dg.png" /></figure><p><strong>Empathy Maps — </strong>Empathy Maps gives a pictorial representation of the user research categorized under various sections. These maps give a deeper insight into what users want and need.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*gr8V7cvEutziUDZp.jpg" /><figcaption><a href="https://sites.google.com/site/astamuea/1-business-management-airport/1-6-business-model-canvas/customer-profile">sites.google.com</a></figcaption></figure><h4>Define</h4><p>The next step towards building a product is defining your problem statement. Identifying and defining the problem statement early in the cycle helps in maintaining the focus and building a similar understanding among all the members of the team. This is a result of the analyzing various areas of user concerns identified during the <em>emphasizing</em> phase.</p><p><strong>Best ways to define a problem statement — </strong>One can use the data collected from the Empathise stage and create a <em>Customer Journey Map.</em> Customer Journey Map is the best tool to depict the users’ journey mapped against their experience/mood at every step in the process. These maps can be of great help in identifying problem statements that are most likely needed by users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DjO0Fd3Kp7EShppX.png" /><figcaption><a href="http://shopifynation.com/marketing/create-customer-journey-map-for-ecommerce/">Shopify Nation</a></figcaption></figure><p>One must ideally focus on solving those areas during which the users’ face lot of issues and have difficulty reaching their goal. Once the area to solve is identified, define your problem statement in a simple <em>“How Might We”</em> like format.</p><h4>Ideate</h4><p><strong>Divergent Thinking — </strong>How crazy can you go with your ideas? It was just the idea of having self-driven cars back then. And now we have self-driven cars built right in front of us. Had Wright Brothers never thought about flying machines, airplanes would not have been discovered. This exercise of divergent thinking freely opens up your gate of how crazy can you go while solving a problem statement. An idea is never silly.</p><p><strong>Convergent Thinking—</strong> Having a huge list of ideas let’s now narrow down these ideas with an “<em>Ease of implementation vs Impact</em>” graph. Put down all your ideas in the graph and decide it for yourself which solution would best fit in the market.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/286/0*NRvqjONjcYo10PUa" /></figure><h4>Prototype/Build</h4><p>Wireframing or Prototyping is an important phase in designing your product. This step gives a visual representation to your solution by designing the wireframes of user interfaces along with their navigation controls. Prototype building demonstrates the product based on the solution and communicates the idea much quicker without the need of explanation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*bjQpvyLeaMEHh-zc.jpg" /><figcaption><a href="http://sketchapp.rocks/learn/material-design-prototype-one/">Sketch App Rocks!</a></figcaption></figure><p>Depending on the stage of the product, a prototype can be built at different fidelities:</p><ul><li><strong>Low-Fidelity:</strong> These are just the Simple Sketches to demonstrate the idea.</li><li><strong>Mid-Fidelity:</strong> Mid-fi prototypes intents at defining a layout allowing a user to navigate through the product.</li><li><strong>Hi-Fidelity:</strong> These represent the almost finished products with a similar look and feel as the real product. With hi-fi prototypes, users can visualize the product as is.</li></ul><h4>Test/Feedback</h4><p>This is an important phase of product building. User feedbacks and User Testing is the most important aspect when it comes to designing the product. In an agile methodology, the involvement of a customer is given much more precedence to overcome the unnecessary assumptions.</p><p>User testing ensures that the product built is right and the best way to validate the product. It helps in understanding the users’ behavior and experience while using the experience. The feedback received in this phase is then corporated back into the ideating phase, re-solutionizing the problem statement, building and taking the feedback again. This is an iterative process and continues until the users’ use the product ;)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/430/0*P5I14bBuC8FEbDEV.png" /><figcaption><a href="http://www.genomecompiler.com/new-design-cycle/">genomecompiler.com</a></figcaption></figure><h4>Key Takeaways from the Workshop</h4><ul><li>Different users go through different experiences while arriving at the same goal. Detailed user research and analyzing the competitors solve 80% of the problem.</li><li>Visual Representations such as Empathy Maps, Personas, and Customer Journey Maps helps in rightly identifying the problem statement and brings all the Team members to the same page.</li><li>Creating a product for the users and not for yourself. User Feedbacks is the crux of getting the right product to the market. More is the user involvement at each phase, more likely we are to build the right product.</li></ul><p>Great thanks to <a href="https://medium.com/@snehaprabhu">Sneha Prabhu</a> and <a href="https://medium.com/@prashanth3690_4903">Prasanth</a> for driving a successful workshop. Kudos to all the volunteers ☺</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/984/1*glRXya-x759J6GWUQv8OKQ.png" /><figcaption>Getting the hands dirty during the Workshop</figcaption></figure><h4>More where this came from</h4><p>This story is published in <a href="http://blog.usejournal.com/">Noteworthy</a>, where thousands come every day to learn about the people &amp; ideas shaping the products we love.</p><p>Follow our publication to see more product &amp; design stories featured by the <a href="https://usejournal.com/?utm_source=usejournal.com&amp;utm_medium=blog&amp;utm_campaign=guest_post">Journal</a> team.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7be14698be42" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The lifecycle of a Story in QA’s Hand]]></title>
            <link>https://lipikadugar.medium.com/the-lifecycle-of-a-story-in-qas-hand-87dd5aa81c1b?source=rss-aa26604be59f------2</link>
            <guid isPermaLink="false">https://medium.com/p/87dd5aa81c1b</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[extreme-programming]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Lipika]]></dc:creator>
            <pubDate>Sat, 23 Jun 2018 03:50:34 GMT</pubDate>
            <atom:updated>2018-06-27T18:09:11.213Z</atom:updated>
            <content:encoded><![CDATA[<p>As a QA, I have been asked multiple times to take sessions on how I come up with test cases for a story. And my usual answer to this would be “what is there to take session about” nothing much to share. Hold on “Is it really that I don’t have anything to share?” Made me thinking…. and so I decided to jot down every small task that I do while coming up with test cases for a story. And believe me, I was amazed myself.</p><h4>What exactly is a story?</h4><blockquote>In the best of its definition “A story is that piece of functionality of a feature which satisfies the <a href="https://xp123.com/articles/invest-in-good-stories-and-smart-tasks/">INVEST</a> principle”.</blockquote><p>So what happens when the story comes to QA? Or rather the question would be when does a story come to QA? Well, honestly a story comes to QA&#39;s hands when the feature itself is being discussed which is most likely a release ahead assuming the feature is supposed to be played in next release.</p><p>A feature then is divided into multiple stories and when it comes to writing test cases or test strategy for a story, it is like a Roller Coaster Ride that a QA goes through from understanding the bigger picture to drilling down to the most granular level.</p><h3>Now the crux of writing test cases</h3><p>I believe coming up with test cases is itself an art and is full of creativity not because it gets your brain into working mode but it definitely needs some focus and analyzing skills.</p><p>So how should we start with writing test cases? Let&#39;s get started</p><blockquote>Consider that we need to come up with test cases for a Reset Password functionality as part of login feature.</blockquote><h4>Get the business context about the feature</h4><p>The first and foremost requirement to come up with test cases is to understand the business. As simple as the feature business says</p><blockquote>As a user of the application</blockquote><blockquote>I should be able to reset my password</blockquote><blockquote>So that I can login to the application</blockquote><h4>Read between the lines</h4><p>Most of the test cases are easily identifiable when we read the business context.</p><blockquote>As said “Read the question again and again, you will find an answer”. Similarly, read the Business Context and Acceptance Criteria, you will be able to identify test cases easily. Its all hidden ;)</blockquote><h4>Analyse</h4><p>Analysing a story is very important to identify risks at the earlier stage. This involves identification of areas which is related to the story being implemented. While coming up with test cases one must definitely identify the regression scenarios and add as part of the story testing. Yes, you read it right. Regression should be done as part of story testing. If we know that any functionality being implemented does touch the other functionality or feature then it is wise to perform regression as part of story testing. Having automation in place is always an add-on.</p><p>Based on the analysis of the story or feature one can use following Testing Design Techniques to come up with various Test Cases</p><ol><li><strong>Boundary Value Analysis —</strong> This covers the values from extreme ends of the partition. For eg: Boundary Values for Input fields accepting age above 18 years can be <em>17, 18, 19</em></li><li><strong>Equivalence Partitioning — </strong>Equivalence Partitioning and Boundary value analysis is closely associated with each other. Equivalence Partitioning takes in the values from a partition done based on the analysis of the problem statement. Say for the same example, Equivalence Partitioning can be done as <em>Negative Numbers, Below 18, Above 18, 3-digit number, </em>etc. Equivalence Partitioning is done to ensure that Test Cases cover a wide range of values</li><li><strong>Pairwise Testing — </strong>Consider an example where a user would need to verify various combination actions for an input field. This might not take much time as its just one input field. But imagine a scenario where there are 100s of 1000s of combinations involved. Having such test cases might be tedious to maintain and test every time. The pairwise testing method helps in designing the minimum number of effective test cases covering all necessary combinations.</li></ol><h4>Finally comes the Edge Cases</h4><p>Really? I strongly believe that no test case is an edge case if it has come to your mind. An edge case is something which a user is very less likely to do. In such a situation, as a QA you should always question or validate your test case with the relevant stakeholders and users. If it has come to your mind then there is a good probability that it might come to user’s mind as well. And you never know, what you considered as Edge Case might turn out to be the very likely scenario.</p><h4><strong>Connecting the dots</strong></h4><p>So now we have individually tested stories in place. Once a story is tested, it does not mean that it&#39;s done. The lifecycle of the story remains incomplete unless it gets integrated with other components to get the right functionality working. Connecting these dots to get the feature ready for the end users marks the end of the <em>Chapter 1 lifecycle of the story in QAs Hand</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/482/0*i74xNmCpD2fKZnFX.gif" /></figure><h4>Now the Mantra:</h4><blockquote>Ask questions, stop making assumptions. Remember no question is a bad question and most importantly challenge the solution. This helps in getting better understanding of the users and business.</blockquote><h4>More where this came from</h4><p>This story is published in <a href="http://blog.usejournal.com/">Noteworthy</a>, where thousands come every day to learn about the people &amp; ideas shaping the products we love.</p><p>Follow our publication to see more stories featured by the <a href="https://usejournal.com/?/utm_source=usejournal.com&amp;utm_medium=blog&amp;utm_campaign=guest_post">Journal</a> team.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87dd5aa81c1b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>