<?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 Sahil Puri on Medium]]></title>
        <description><![CDATA[Stories by Sahil Puri on Medium]]></description>
        <link>https://medium.com/@sahilpuri1212?source=rss-8f96ec4370bf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*mAlRIt_2uEU_9bk5BKKvPg.jpeg</url>
            <title>Stories by Sahil Puri on Medium</title>
            <link>https://medium.com/@sahilpuri1212?source=rss-8f96ec4370bf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 05:36:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sahilpuri1212/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[6 pointers to help you choose your next job offer.]]></title>
            <link>https://sahilpuri1212.medium.com/6-pointers-to-help-you-choose-your-next-job-offer-35cc6430340a?source=rss-8f96ec4370bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/35cc6430340a</guid>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[offers]]></category>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[test]]></category>
            <category><![CDATA[jobs]]></category>
            <dc:creator><![CDATA[Sahil Puri]]></dc:creator>
            <pubDate>Fri, 09 Dec 2022 18:42:23 GMT</pubDate>
            <atom:updated>2022-12-23T07:12:12.548Z</atom:updated>
            <content:encoded><![CDATA[<h4>Make an informed and confident decision in choosing your next employer.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*or5tPIX98Hzoh29eczh0ww.png" /></figure><p>Changing your employer and looking for better job options is one of the most challenging tasks in everyone’s professional journey. What makes it more daunting is the uncertainty &amp; few unresolved mysteries about the future associated with different options available for your choice. The anxiety and nostalgia of leaving your current organization, the unpredictability of what the future holds for you &amp; the fear of possibly taking a wrong decision might lead to sleepless nights and stressful conditions.</p><p>Let us discuss some important practices which will help you make an informed decision and reduce your anxiety about this decision. In order to put things into perspective, the very first task is to introspect &amp; understand your reason of changing your current job. These can vary among one or more of the below points -:</p><ol><li>In search of a better manager</li><li>In search of a better company (organization)</li><li>In search of better work/quality of work</li><li>In search of better salary/CTC/compensation.</li><li>In search of a better location</li><li>In search of a better growth plan / promotional ladder for your role.</li><li>Or Just because you are bored and want to change job. 😀</li></ol><p>Although the number is low, still 10–15% of resignations occur because of no particular or urgent reason which is depicted in the 7th point above. The real problem lies in the fact that there is no scale to measure “<strong>better</strong>” and we sometimes unknowingly become impatient with our salary, manager, and growth path without any introspection, industry data, or research.</p><blockquote>So I would request you to stop here and go to the drawing board again if you are not very sure of the exact reason(s) for changing your current job and give your current employer one more chance.</blockquote><p>Once you are sure of the change and have sufficient pointers to back your decision, it becomes vital that you set yourself in the correct state of mind. Below are some ways to collect maximum information to make an informed decision that will be in the best interest of your career perspective -:</p><ol><li><strong>Talk to your next reporting manager<br></strong>Plan a 1–1 meeting with all potential manager(s) and understand their expectations from team members, way of working, preferences, past companies &amp; experiences and check your alignment with all these observations &amp; goals. This is important since you would be spending 60–70% of the time interacting with your manager regarding your tasks, problems, and concerns.<br>He / She will set a platform of opportunities for your career growth in the next few years keeping you motivated and passionate about your job. So understanding the manager’s expectations &amp; having a strong connection with their goals, thoughts, and working style is a strong GREEN signal among others.</li><li><strong>Know about the team structure<br></strong>This data point covers the size, structure, hierarchy &amp; distribution of the team in your next role. This will give you a clear idea about the possible growth opportunities, team members &amp; current dynamics within the team.<br>This becomes important information for taking the right decision since your future team can make your next professional journey really enjoyable, full of learning, and worthwhile.</li><li><strong>Understand the career ladder &amp; growth opportunities for the role<br></strong>In many cases, a job offer with higher growth opportunities is better than a competitive offer offering a way higher CTC/package but limited ladder &amp; growth opportunities.<br>It is always recommended to choose an option that gives you the flexibility, and freedom to grow and trust your abilities to reach the highest ranks in terms of the leadership ladder.</li><li><strong>Ask for the work/ tech stack/ Initial projects<br></strong>The kind of projects, tech stack, product &amp; challenges you will work on in the next couple of years will set your journey for the next decade. Chose the opportunity to learn &amp; solve the tough challenges over higher money at this point in time. This is the best example of investing in today to reap the exponential benefits in the future.</li><li><strong>Make the most of the CEO/CTO/VP round<br></strong>Most product companies have the last round as the culture fit round usually taken by the leadership. Consider this as an opportunity to ask questions about the company’s vision, values &amp; current state of business metrics. This data will give a true sense of your future employer’s growth, stability, and culture, thus enabling you to make a sound choice.</li><li><strong>Ask for medical insurance and other employee perks<br></strong>The employee benefits or perks become another important pointer to closely guess the culture and employee value to the organization. There may be some false negatives and false positives for this pointer, but when considered with other data points, it surely adds on to the confidence in the correct direction.</li></ol><blockquote>To the surprise of many, I did not cover a very important point which is the compensation portion of the job offer.</blockquote><p>Now, first of all, I am very confident that you will not let the CTC factor go away from your decision-making pointers even though you didn’t read that in the above list, and secondly, it doesn’t really matter in the long run as long as you are getting an amount that is worthy of your experience, skills &amp; effort.</p><p><strong>I am no saint and value money as much as every other human being still I always recommend keeping the above-mentioned pointers above monetary gains because money will eventually follow, no matter what.</strong></p><p><strong><em>Connect with me at </em></strong><a href="https://topmate.io/sahil_puri"><strong><em>https://topmate.io/sahil_puri</em></strong></a><strong><em> for mock interviews, 1–1 mentoring sessions, coding lessons, SDET role career guidance, or a casual chat on testing !</em></strong></p><p>See you next time<br>Sahil Puri.(<a href="https://www.youtube.com/channel/UCwQPYaV-uc0yX3-TFeCpfcQ">Youtube channel</a> , <a href="https://www.linkedin.com/in/sahil-puri2022/">Linkedin</a>)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35cc6430340a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Follow these 6 bug report enhancements and see the change!]]></title>
            <link>https://sahilpuri1212.medium.com/follow-these-6-bug-report-enhancements-and-see-the-change-7e82eb3e15b3?source=rss-8f96ec4370bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e82eb3e15b3</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Sahil Puri]]></dc:creator>
            <pubDate>Sat, 03 Dec 2022 19:27:22 GMT</pubDate>
            <atom:updated>2022-12-08T19:45:16.229Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Improve engineer‘s productivity with 6 simple steps.</strong></h4><p>A quality engineer typically spends around 10–15% of the day’s effort in raising new bugs. But this is just the beginning! <strong>An extra 15% effort </strong>is then spent in several back-and-forth communication with the developers involving information exchange about the same bug. This extra share of effort takes a big chunk out of our time &amp; energy thereby directly affecting our productivity.</p><p>The symptoms to this problem can be seen in the form of repeated &amp; redundant communication, re-iterations of test scenarios time &amp; again, and several context-switching instances thereby delaying the current set of assigned tasks and engineer’s burnout!</p><blockquote>The need for this to-and-fro bug-related communication mostly arises from the<em> lack of information</em> about some important aspects of the bug scenario in the initial bug report!</blockquote><p>T o your surprise, most of these redundant efforts can be easily avoided thereby saving hours of engineer’s time.</p><p>Let’s look at some simple improvements in the bug reporting template that can save a major chunk of your &amp; developer’s effort thus contributing to overall engineering productivity.</p><ol><li><strong>Bug occurrence frequency :<br></strong>This is a critical piece of information and is often missed by most test engineers while reporting bugs which leads to wrong assumptions at the developer’s end &amp; false triaging of the bug. A bug can have an occurrence frequency of <strong>Once </strong>(if it has occurred only once in the entire test cycle), <strong>Sometimes </strong>(x%) i.e the bug appears x times out of a total of 100 trials of scenario run, <strong>Always </strong>(100%) i.e the bug appears 100/100 times when the scenario runs.<br>The criticality &amp; severity of any issue changes drastically depending on its occurrence frequency and hence become a very important metric to be added in every bug report.</li><li><strong>Reason for a specific priority/severity :<br></strong>It is very important to add a few details related to the priority of the bug and reasoning to back this priority &amp; severity level! This reasoning can be related to hampered user experience, revenue-affecting scenarios, app crashes having higher frequency probability with production scale, new user journey, user retention, legal action possibilities, etc.<br>A strong reason here with the correct logic and advocacy can even make a mere spell check to be regarded as a release blocker.<em> (Example — The Welcome signup screen has a spell check bug leading to a hampered user experience for all new users which can lead to dropping in new users at this part of the acquisition funnel. Further adding marketing and product members for detailed triaging.)</em></li><li><strong>Initial debugging details / RCA :<br></strong>Randomly assigning bugs to developers without any debugging leads to increased TAT, miscommunication &amp; a possible project delay with unnecessary re-assignments of the bug. The quality engineer is expected to perform basic log analysis and debugging to assign the bug to the correct developer/team with details about the findings of this debugging.<br>The debugging can be done with the help of application logs (adb/Xcode), server logs (pm2/docker), proxy logs (charles/fiddler/etc), and knowledge to read and analyze the above logs. This improvement can save hours of developer’s time and effort thereby leading to higher engineering productivity and faster project release.</li><li><strong>Test data, App Version, and environment details : <br></strong>A bug report can not be complete without mentioning the details of the app build version, server / VM / stage environment details &amp; test data used while reproducing the reported bug. All this information will help the developer in quick debugging &amp; possible resolution of the bug by recreating the same exact preconditions as done by the test engineer.</li><li><strong>Detailed and simple bug reproduction steps : <br></strong>The test engineer should mention the steps of bug reproduction in a detailed &amp; simple manner that doesn’t require any further help or query resolution. A compressed video, screenshot, or gif can go a long way in helping the developer in understanding the bug occurrence steps clearly without any need to poke the tester back with related queries.</li><li><strong>Keep all updates in the bug’s comments section :<br></strong>It is always a best practice to keep adding all updates in the bug’s comments section. This will help in reliable future references, bring transparency in leadership review for project blockers, keep all agile teams updated for communication, and avoid redundant queries. This practice is extremely useful to take the product/BA/client team’s point of view when deprioritizing a bug based on the developer’s comment.</li><li><strong>Bonus tip : Create a common bug template</strong>:<strong> <br></strong>Last but not the least, it is advisable to create a bug template that is followed across all agile pods thereby bringing a sense of uniformity and ensuring all necessary details are added for every bug report as a regular practice.</li></ol><blockquote>The key to saving everyone’s effort from redundant queries around reported bugs is in understanding the importance of the above fields in a bug report &amp; sharing exhaustive information while writing a bug story.</blockquote><p>Apart from improving overall engineering productivity, a complete and exhaustive bug report helps quality engineering teams in various ways -:</p><ol><li>This helps in <strong>bug advocacy </strong>with facts and information.</li><li>Keeping the bug reports updated leads to <strong>reliable future references.</strong></li><li>Depicts your<strong> debugging skills and technical aspects</strong> of the reported bug.</li><li>Shows<strong> your skill of understanding the user experience</strong> &amp; able to map a suitable priority to the bug accordingly.</li><li><strong>Ease of understanding the context of the bug</strong> by leadership, product ,CRM &amp; marketing teams in case of a project review / bug audit or random reference check.</li></ol><p>On the downside, however, a lengthy bug report can also lead to possible reluctance from test engineers to report bugs and prioritize the execution of current pending tasks. Hence it is advisable to collaborate with development teams and create an<strong> optimized bug template </strong>that can carry maximum information in minimum fields thus taking no more than ~3–5 minutes of an engineer’s time to create a new bug.</p><p>So next time you are onto the task of improving your team’s productivity, you already now know the low-hanging fruit right in front of you in the form of bug reports and associated details with that report.</p><p><strong><em>Connect with me at </em></strong><a href="https://topmate.io/sahil_puri"><strong><em>https://topmate.io/sahil_puri</em></strong></a><strong><em> for mock interviews, 1–1 mentoring sessions, SDET role career guidance, or a casual chat on testing!</em></strong></p><p>See you next time<br>Sahil Puri<br>(<a href="https://www.youtube.com/channel/UCwQPYaV-uc0yX3-TFeCpfcQ">Youtube channel</a> , <a href="https://www.linkedin.com/in/sahil-puri2022/">Linkedin</a>)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e82eb3e15b3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Have you ever felt less respected or leftout as a test engineer ?]]></title>
            <link>https://sahilpuri1212.medium.com/have-you-ever-felt-disrespected-as-a-tester-d97da6a0db3d?source=rss-8f96ec4370bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/d97da6a0db3d</guid>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[test]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[sdet]]></category>
            <dc:creator><![CDATA[Sahil Puri]]></dc:creator>
            <pubDate>Sat, 26 Nov 2022 20:52:12 GMT</pubDate>
            <atom:updated>2022-11-29T14:03:26.664Z</atom:updated>
            <content:encoded><![CDATA[<p>A quick peek at our own deeds and a look within.</p><p>Are you in the testing field and have ever felt that you or your team is not getting the same connect, respect and priority as the development, product, or other team members? Don’t worry, there are many other people too who are great quality engineers and felt the same way at least once in their professional careers !</p><p>First, let’s look at some pointers that will make you realize if there is some basis to your feelings or <strong>maybe it is just another misconception</strong> of your mind.</p><ol><li>You are not getting authorization permissions for code, dashboards, and tools.</li><li>Your timelines are not prioritized for critical projects.</li><li>Developers are not keen to help or transfer knowledge to you and your team.</li><li>Developers do not take your bugs/reports seriously and make the release without fixing blocker bugs.</li><li>You get the pressure of closing bugs with the reason of technical limitations without any explanation.</li><li>You are not getting responses to your queries from other teams.</li><li>Your suggestions on design, user journeys, and products are turned down immediately.</li><li>You are not getting hiring approvals when the current team is overloaded.</li><li>You are not recognized along with other team members for major releases and launches.</li><li>You overhear other team members even questioning your existence on the team.</li></ol><blockquote>If you can relate to at least 2–3 of the above points, then you should definitely go on and read the next section where we discuss the possible reasons for others to have a bias against you or your work.</blockquote><p>It is very important to go one level deeper &amp; understand the <strong>possible</strong> <strong>causes of the above bias</strong>.</p><ul><li><strong>Nature of the ‘Testing’ role<br></strong>It is sometimes natural to hate testers given that the prime objective of our existence is to find faults and risks in the developer’s code and system! Also, any blocker bugs found by the testing teams end up delaying the project which frustrates the program and project managers.</li><li><strong>Preconceptions in the industry &amp; past experiences<br></strong>Depending on past experiences, different backgrounds &amp; preconceived notions about the testing and related role, there are different points of view resulting in their varied judgments.</li><li><strong>Lack of ownership skills &amp; curiosity to learn<br></strong>This is the most common reason for this bias. Sometimes, testers become too much dependent on developers for small tasks like capturing logs, changing DB values, validation events, stage deployments, test environment maintenance, etc without having any sort of curiosity to learn these technical hacks and save developers time. This leads to the rightful biases against test engineers stemming from the over-dependence on developers thereby leading to more context switching and frustration at the developer’s end.</li><li><strong>Not using facts and data to support our suggestions<br></strong>Data is the best way to back any suggestion or improvement request made to the product teams. But sometimes it is possible for test engineers to get emotional and develop a deep passion for the product and then raise suggestions or blovker arguements without supporting data or logical facts that could easily hurt other team member’s ego and lead to judgements and miscommunication at work.</li><li><strong>Unable to show (market) our work properly<br></strong>Test teams are sometimes so engrossed in their day to day work duties that they fail to show their work properly to the other teams. Every improvement your team makes in automation, process building, stable releases, etc helps the overall stability and should be shared with development and cross-functional teams in a proper package thereby keeping the trust and required collaboration.</li><li><strong>Silo tasks with no collaboration with other teams<br></strong>Many a times test and automation teams work in silo without any overlap or collaboration with development &amp; product teams, it results in an anti pattern . There is no point in working on processes / automating the tests of a product without understanding your potential users, it is bound to be undervalued and eventually fail.</li></ul><blockquote>As per my experience, quality engineers come with a clean slate and no baggage of preconceived respect which in fact is good and can be considered as an opportunity for us to build our own credibility &amp; trust through our work and contribution to the product and project, which ultimately decides our value and worth in overall picture.</blockquote><p>I t is difficult to measure ‘quality’ &amp; the efforts put out by quality engineering team so objectively. Try out the below practices to build your role’s <strong>credibility</strong> and <strong>respect</strong>-:</p><ul><li><strong>Engineering Productivity<br></strong>As quality engineers, one of our roles and responsibilities is to improve the existing process and pipelines to increase the engineer’s productivity. Ensure not to waste anyone’s time on redundant tasks &amp; focus on documentation, and KT sessions instead of asking for the same help time and again from your peers. The idea is to respect everyone’s time and receive due respect in return.</li><li><strong>Cross Team Collaboration<br></strong>Don’t run test improvement plans and automation projects in silo mode rather enable collaboration with cross-functional teams for all these efforts. They can provide some extremely valuable inputs for your automation scope and requirements thus helping you not to digress and stay aligned with the common goal.</li><li><strong>Knowledge Sessions &amp; Show Your Work<br></strong>Plan knowledge sessions to introduce other teams &amp; members to testing, its different types, your automation project architecture, infra &amp; pipelines, and the impact that your team’s efforts have created on the overall product’s development lifecycle. This impact can be in terms of stability, velocity, or monitoring depending on your objective.</li><li><strong>Talk and Build Relations<br></strong>Build relationships with your peers and other team members. Sometimes a chat over coffee solves all preconceptions and communication gaps thus building more respect towards each other’s work and contribution. Remember, giving and receiving respect works both ways.</li><li><strong>Build a Culture of Quality<br></strong>Develop a passion for quality and talk about it in smaller groups, meetups, org-level meetings, townhalls and 1–1’s. This mindset is like a seed and takes time to blossom but all the efforts put in is bound to give fruits and flowers in the form of better culture and overall respect for everyone responsible for product’s quality.</li><li><strong>Data-oriented approach toward impact analysis</strong><br>Report the impact of your &amp; team’s efforts with data-oriented facts clearly stating the impact it has brought to the overall business and product metrics. The more we align our tasks and impact analysis to the entire company’s business goals, the better we are bound to be valued and appreciated by the leadership and cross-functional teams.</li><li><strong>Trust your work and never underestimate what you are doing<br></strong>This is the most important advice since respect for your work starts from within. If ‘YOU’ trust testing and what you are doing, you will never accept any such behavior or mindset and point out any disrespectful event with dignity and order. But if you yourself don’t value the power of testing and test engineers, then there is little scope of earning everyone’s respect and being the central character in the tales of successful product launches.</li></ul><p>I want to end this discussion on the note of self-worth realization and understanding the value of the contribution made by quality engineers to the overall organization’s success.</p><p><strong>By the way, most of the time it is just an illusion and our own sense of insecurities that leads us to feel not equally respected and the solution to our feelings are hidden inside ourselves only.</strong></p><p><strong><em>Connect with me at </em></strong><a href="https://topmate.io/sahil_puri"><strong><em>https://topmate.io/sahil_puri</em></strong></a><strong><em> for mock interviews, 1–1 mentoring sessions, SDET role career guidance or a casual chat on testing !</em></strong></p><p>See you next time<br>Sahil Puri.(<a href="https://www.youtube.com/channel/UCwQPYaV-uc0yX3-TFeCpfcQ">Youtube channel</a> , <a href="https://www.linkedin.com/in/sahil-puri2022/">Linkedin</a>)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d97da6a0db3d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t make this mistake if you want to grow your testing career!]]></title>
            <link>https://sahilpuri1212.medium.com/dont-make-this-mistake-if-you-want-to-grow-your-testing-career-28801ab95a7c?source=rss-8f96ec4370bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/28801ab95a7c</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[sdet]]></category>
            <category><![CDATA[test]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <dc:creator><![CDATA[Sahil Puri]]></dc:creator>
            <pubDate>Tue, 22 Nov 2022 19:00:50 GMT</pubDate>
            <atom:updated>2022-11-22T19:23:07.082Z</atom:updated>
            <content:encoded><![CDATA[<h4>Understand the difference between good and bad choices of the job role.</h4><p>Are you a quality engineer with 1–6 years of experience and aspire to grow in the field of software testing? If yes, you should invest the next few minutes reading this blog to know what NOT TO DO in the coming years of your professional journey.</p><blockquote>The past few years have been revolutionary for the <strong>software testing community </strong>in terms of skill requirements, a wide range of roles &amp; responsibilities, and a rise in the number of jobs<strong> </strong>due to the below reasons -:</blockquote><ol><li>High demand for test automation skills across the industry.</li><li>Increase in the innovation of testing tools &amp; processes.</li><li>Rise of backend/API testing practices with DevOps and CI/CD principles.</li><li>Increase in non-functional test requirements and practices.</li></ol><p>We can attribute this evolution to the ever-growing user base, high competition, several mind-boggling innovations &amp; multiple choices available to the users.</p><p>On the one hand, where this role has witnessed an increase in salary packages &amp; remunerations, at the same time it has also seen a surge in upskilling requirements across the industry especially related to <strong>‘Automation</strong>’. This surge has led to the birth of several myths surrounding this role due to a shallow understanding of role requirements and test engineers running behind certifications and some template courses.</p><p>Based on my personal experience, I have seen many quality engineers, especially freshers and mid-senior testers losing their way due to some common myths and wrong advice received from peers, sometimes even their mentors.</p><p>Considering the rise in SDET role jobs in recent years, it becomes all the way more important to stay focused and <strong>NOT TO</strong> <strong>FALL </strong>in either of the below two buckets when upskilling yourself and looking for your next job.</p><blockquote>There is a large proportion of candidates who fall in either of two buckets —</blockquote><ol><li><strong>Bucket 1</strong>: He/ She wants to be in a<strong> pure (manual) testing role</strong> with <strong>NO automation skills </strong>&amp; code writing or reading aptitude.</li><li><strong>Bucket 2</strong>: He/ She wants to be in the SDET role with <strong>ONLY automation skills</strong> and <strong>NO testing ‘practice’</strong> on the job.</li></ol><p>If you too fall in this proportion who is looking out for either a 100% automation or 0% automation role, it is high time for you to wake up and get your perspective straight!</p><p><strong>Bucket 1 (100% testing &amp; 0% Automation) </strong>will give you good testing, management &amp; process building skills but you won’t be able to grow into senior QE leadership roles without getting your hands dirty with automation and getting comfortable around reading and writing code. In senior roles, you would be required to understand the system, its design &amp; architecture to be able to define complex test and automation strategies to validate and assess the quality of the system with coverage metrics, pipelines, tooling, and dashboards.</p><p><strong>Bucket 2 (0% testing &amp; 100% Automation), </strong>on the other hand, will convert you into a developer with good coding &amp; design skills but you won’t be able to understand the end-to-end SDLC, work with cross-functional team members in small pods, define test strategies at multiple levels, own &amp; manage the product/feature launch into production with best possible quality &amp; post-production monitoring with user experience feedback. All these experiences that you miss here will keep you from becoming an all-rounder QE lead/manager for your team.</p><p>The secret sauce of success in this role lies in a perfect balance of these two buckets. The ideal distribution for testing to coding (automation) in SDET/QE role is approx <strong><em>60%-40%</em></strong> respectively. Any imbalance from this ratio makes you miss some really important elements and responsibilities of this role which will grow your mindset, decision-making skills, and aptitude eventually helping you to succeed in software testing leadership roles.</p><p>So next time you are looking out for a job and someone asks you your preference for work distribution, don’t be the person who vouches for the two extremes, and remember to choose a balance for the all-around growth of your professional career. And if you are unfortunately stuck in such an extreme role, then it is time to start looking out for something better.</p><p><a href="https://topmate.io/sahil_puri">Connect with me for a 1–1 mentoring session, mock interviews, or any discussion related to software testing and automation.</a></p><p>Like and follow for more blogs on testing , leadership and SDET roles.</p><p>See you next time<br>Sahil Puri (<a href="https://www.linkedin.com/in/sahil-puri2022/">LinkedIn</a>, <a href="https://www.youtube.com/channel/UCwQPYaV-uc0yX3-TFeCpfcQ">Youtube channel</a>, <a href="https://medium.com/@sahilpuri1212">Medium blogs</a>)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=28801ab95a7c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 4 reasons why automation projects become obsolete !]]></title>
            <link>https://sahilpuri1212.medium.com/top-4-reasons-why-automation-projects-become-obsolete-6930af501e95?source=rss-8f96ec4370bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/6930af501e95</guid>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[selenium]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[test]]></category>
            <dc:creator><![CDATA[Sahil Puri]]></dc:creator>
            <pubDate>Sat, 19 Nov 2022 19:22:34 GMT</pubDate>
            <atom:updated>2022-11-20T14:39:19.252Z</atom:updated>
            <content:encoded><![CDATA[<h3>Don’t let your automation project FAIL with below Do’s and Don’ts!</h3><h3><strong>Top 4 reasons why automation projects die!</strong></h3><p>Test Automation has become one of the famous buzzwords &amp; priorities of engineering teams across the industry. As a direct consequence, quality engineers are also focusing heavily on learning automation in their preparation strategy for job interviews and applying automation to excel in current job roles.</p><p>But even after having a strong motivation, leadership support and such a large content base for test automation in the form of tutorial videos, tech talks, blog, conferences, a large number of teams are still unable to successfully integrate the automation efforts in their overall testing and end-to-end software release plans.</p><p>Let’s take an example where you are trying to develop a test automation strategy for your backend service/API validations. You select the programming language, perform a proof of concept (POC) of available tools &amp; frameworks and lock your tech stack. Your team chalks out a design and starts developing the framework and eventually is able to automate the sanity validation checks (say first ~100 test cases) using the built framework.</p><blockquote>The real struggle starts here as most automation projects lose their way at this stage owing to the mistakes done in the planning ,strategy and post-development phase.</blockquote><p>Let’s quickly have a look at the top 4 reasons for the automation projects failure with some Do’s and Don’ts -</p><h4><strong>1. Lack of usability with no last mile connectivity .</strong></h4><p>What most teams fail to understand is that every automation project is a complete product in itself which requires requirement analysis, design, development, release followed by a proper training and user feedback phase. The ‘user’ in this case is the test or development engineers running the automated test cases to validate a code change.</p><p><strong>Don’ts</strong></p><ul><li>Do not run the automated tests on your local machine or through IDE .</li><li>Do not have a manual dependency for triggering the test runs.</li><li>Do not build the automation framework with no or less thoughts about its usability &amp; reachability.</li></ul><p><strong>Do’s</strong></p><ul><li>Make the automated tests accessible &amp; easy to run. Use trainings &amp; documentation for the same.</li><li>Automate the automation triggers too using CI/CD pipelines and webhooks.</li><li>Identify and be clear about the actual use cases for your potential users.</li></ul><h4><strong>2. No process for on-call flaky tests triaging and maintenance.</strong></h4><p>Even after developing the automation framework and building best in class CI/CD pipelines for best usability , the daemon of ‘flakiness’ will not let you live in peace. Yes, handling flakiness is the bridge that every automation team has to cross in their journey of building an efficient and stable automation architecture.</p><p><strong>Don’ts</strong></p><ul><li>Do not leave the failed cases unattended and unassigned.</li><li>Do not prioritize adding more cases over maintenance of existing cases to increase stability.</li><li>Do not let the red builds be seen as normal since it makes you lose credibility and trust.</li></ul><p><strong>Do’s</strong></p><ul><li>Keep a rotational on-call R&amp;R in the team for automation failures .</li><li>Assign all flaky tests immediately for maintenance with target timelines.</li><li>Give or Ask proper reasoning for every red build to keep up the credibility.</li></ul><h4><strong>3. Aiming for 100% automation leading to a bloated automation suite.</strong></h4><p>This is the trickiest of them all since most leadership will ask you to cover 100% test cases in automation. The test manager &amp; leads have to smartly assess the ROI and cost of automating the test cases beyond a certain coverage level. The cases which require human cognitive &amp; decision making skills or some production level security hacks are best to be run without automation.</p><p><strong>Don’ts</strong></p><ul><li>Do not bulk up your automation suite just to increase coverage metrics.</li><li>Do not aim for 100% automation ,rather initially aim for speed &amp; stability with traceability to P0 user stories.</li></ul><p><strong>Do’s</strong></p><ul><li>Evaluate the ROI of automating a scenario before adding it to the automation scope.</li><li>Take security, legal, finance &amp; performance teams in confidence if you ever decide to run your automation on production.</li><li>Many times it is a wise decision to leave some scenarios out of automation scope, at least in the initial phases of automation project. So pick your battles carefully.</li></ul><h4><strong>4. No marketing of automation efforts, metrics &amp; vision.</strong></h4><p>This is the most common reason for good automation projects getting obsolete or replaced. Many teams do not prioritize sharing their metrics, achievements &amp; vision mostly due to time crunch and thus investing no time in marketing your automation projects &amp; effort across different teams.</p><p><strong>Don’ts</strong></p><ul><li>Do not run automation without building a standard reporting structure</li><li>Do not let automation teams work in silo &amp; separate from agile pods .</li></ul><p><strong>Do’s</strong></p><ul><li>Build a reporting dashboard/portal where historical reports can be viewed &amp; analyzed .</li><li>Share weekly/monthly reports of automation runs across the organization with metrics and a brief summary of your findings, challenges, improvements etc.</li><li>Hold quarterly brown bag or knowledge sessions sharing the vision and roadmap for the automation infrastructure with cross functional teams.</li><li>Regularly discuss your strategy of automation with developers to discuss some hacks and avoid the over-engineering.</li></ul><p>Over the years , I have realized that developing an automation framework is relatively easier than predicting the pitfalls that arise from above experiences. Going aggressively with the goal of 100% automation testcase is not the correct solution since it lacks a balanced vision. Also , expecting the development &amp; product teams to <em>self realize</em> the importance of your automated tests without any efforts from your side is asking for a bit too much.</p><blockquote>Always solve the 5W 1H in your automation strategy and planning phase to build ‘last mile connectivity’ and ensuring the best collaboration from every member and team in making your automation project a success.</blockquote><p>See you next time<br>Sahil Puri (<a href="https://www.linkedin.com/in/sahil-puri2022/">LinkedIn </a>, <a href="https://www.youtube.com/channel/UCwQPYaV-uc0yX3-TFeCpfcQ">Youtube channel</a>, <a href="https://topmate.io/sahil_puri">1–1 sessions</a>)</p><p>Like and follow for more blogs on testing , leadership and SDET roles.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6930af501e95" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7-Step guide to be a skilled SDET/QE.]]></title>
            <link>https://sahilpuri1212.medium.com/7-step-guide-to-be-a-skilled-sdet-qe-8ac55915c986?source=rss-8f96ec4370bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ac55915c986</guid>
            <category><![CDATA[interviews-and-insights]]></category>
            <category><![CDATA[sdet]]></category>
            <category><![CDATA[quality]]></category>
            <category><![CDATA[transitions]]></category>
            <category><![CDATA[test]]></category>
            <dc:creator><![CDATA[Sahil Puri]]></dc:creator>
            <pubDate>Tue, 15 Nov 2022 19:18:01 GMT</pubDate>
            <atom:updated>2022-11-16T19:15:42.192Z</atom:updated>
            <content:encoded><![CDATA[<p>Plan the transition with these steps and know your WHY ? &amp; HOW ?</p><p>QA role is one of those tech roles which has seen a major evolution over the last decade. The expectations, skill requirements as well as the pay packages for quality engineering roles have changed and increased exponentially over a span of 8–10 years</p><p>However, a guided roadmap of upgrading our skillset to live upto these evolved expectations is still a mystery to many engineers serving for years in this role as well as to freshers entering the industry.</p><p>Around 70% of current QA engineers are looking for a perfect course or mentor who can help them to upskill and crack the role of QE or SDET.</p><blockquote><strong><em>There can be many motivational reasons for this quest including -</em></strong></blockquote><ol><li><strong>Higher CTC package</strong> — The salary range for a qualified QE/SDET has gone up and past the levels of all its contemporary roles.</li><li><strong>Better job security</strong> — Yes , being qualified at your work makes you relatively harder to replace.</li><li><strong>More respect and say</strong> — Slightly controversial , but yes, having a better insight of tech, automation &amp; new ways to test is bound to gain high respect from your management &amp; stakeholders helping you to make better decisions and work with autonomy.</li><li><strong>Growth ladder — </strong>The skillset &amp; better insight surely opens the ladder for growth within an organisation for both IC and management roles.</li><li><strong>All of them — </strong>This one being the most common answer.</li></ol><blockquote><strong><em>Now let’s break two common myths before jumping on to the steps to become an SDET.</em></strong></blockquote><ol><li><strong>SDET role = ‘Automation’. </strong><em>No it is not</em><strong><em>.</em> </strong>It is very important to burst this bubble since the buzzword of ‘automation’ has set the wrong context among freshers and QA engineers. SDET is much more than automation.</li><li><strong>QA and SDET are two separate roles . </strong><em>No they are not.</em><strong> </strong>Do not overwhelm yourself by thinking of it as a major transition into a completely new role. You just need to be better at what you have been already doing till now i.e testing.</li></ol><blockquote><strong><em>Okay enough of the build up , now let’s get straight to the point and discuss the steps for a quick and smooth transition into the SDET role.</em></strong></blockquote><h4><strong>1. Change your Mindset</strong> &amp; <strong>be more Curious</strong></h4><ul><li>Be ready to get out of your comfort zone &amp; learn new things! Choose your reason to keep yourself motivated.</li></ul><h4><strong>2. Be a much better ‘tester’</strong></h4><ul><li>The primary role of SDET role is to test and dig out hidden risks and information to ensure best quality. Start testing everything a level deeper to what you have been doing already and connect every new feature/change ticket to 3 buckets :</li></ul><ol><li>How is it working from a tech point of view ?</li><li>How is it helping businesses to generate revenue ?</li><li>How is it enhancing user experience when rolled out to production ?</li></ol><p>Doing the above exercise will give an enormous insight of the product and what is actually expected out of it from <em>tech, business and user</em> point of view thus enabling you to think out of the box test scenarios and enhance the overall product quality you are working on.</p><p>Find new and better ways to test the product, including non-functional types of testing and thinking ahead of functional tests and checks .</p><h4><strong>3. Learn to read and write code</strong></h4><ul><li>Start small with reading and debugging others’ code to understand the logic behind the same. Refer to the developer’s PR which will eventually help you to make better test plans.</li><li>Once you are comfortable with reading code, start with writing small codes for simple logics. You can take help of platforms like leetcode.com for practising your coding and problem solving skills.</li></ul><p>I know it is easier said than done , but believe me ‘ just keep practising and don’t give up’ .</p><h4><strong>4. Advocate for ‘quality’ across cross functional teams</strong></h4><ul><li>Start building communication channels with cross functional teams and enable them to build quality channels in different phases of SDLC.</li><li>Advocate for ‘quality is everyone’s responsibility’ and ‘test in every phase’ by shifting left and right. This will build your credibility and people will start approaching you for discussing the current gaps in quality processes .</li></ul><h4><strong>5. Learn automation tools</strong></h4><ul><li>If you follow the above steps, you surely would be overwhelmed by now and craving for some extra time. Now is the best time to introduce ‘Automation’ for its right purpose , to save your time from repeatable and redundant processes and test case executions.</li><li>Pick up any one automation tool , ideally best suited for your current job role. It can be either a frontend or backend automation tool. Learn the 5W and 1H of automation by building an end to end automation project.</li><li>Do not focus on building the best framework at this point , but clear your concepts regarding automation and focus on the use cases that automation can provide you in your journey.</li><li>Do not get confused about which programming language or tool to pick right now. You can discuss with your mentor and start on any tool as long as it satisfies your requirement &amp; strategy.</li></ul><h4><strong>6. Keep yourself updated</strong></h4><ul><li>This step is a continuous loop to keep yourself updated and upto the benchmark of what is happening across industry in terms of new tools, processes, ways &amp; types of testing etc.</li><li>Build your source of information and network by joining testing communities, watching tech talks , attending conferences &amp; reading blogs, books etc.</li></ul><h4><strong>7. Communication</strong></h4><ul><li>As an SDET engineer , you are required to over-communicate and bridge the gap across all cross functional teams .</li><li>Practice all forms of communications (emails, slack, 1–1s) , send minutes of meeting after every important discussion, share regular test status updated with risks and blockers, and most importantly build relations and trust with stakeholders using the tool of communication.</li></ul><p>And above all , “<strong>Break the invisible virtual walls that you have built around yourself”</strong> and let <strong>NO ONE</strong> underestimate your potential of learning and excelling….no one including yourself.</p><p><strong>The above steps will surely put you on the right path of becoming a skilled SDET engineer &amp; a valuable employee to the organisation bringing much higher value to the table</strong> !</p><p>Practice the above steps for <strong>45 days</strong> and you will build enormous confidence and mindset of carving your own way to your dream role much sooner than ever.</p><p><strong><em>Connect with me on </em></strong><a href="https://topmate.io/sahil_puri"><strong><em>https://topmate.io/sahil_puri</em></strong></a><strong><em> for mock interviews, 1–1 mentoring sessions, SDET role career guidance or a casual chat on testing !</em></strong></p><p>See you next time<br>Sahil Puri.(<a href="https://www.youtube.com/channel/UCwQPYaV-uc0yX3-TFeCpfcQ">Youtube channel</a> , <a href="https://www.linkedin.com/in/sahil-puri2022/">Linkedin</a>)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ac55915c986" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Train your brain with the below algorithms for your coding round interviews!]]></title>
            <link>https://sahilpuri1212.medium.com/train-your-brain-with-the-below-algorithms-for-your-coding-round-interviews-ac6ff144dabb?source=rss-8f96ec4370bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac6ff144dabb</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[test]]></category>
            <category><![CDATA[sdet]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[Sahil Puri]]></dc:creator>
            <pubDate>Sat, 12 Nov 2022 14:39:56 GMT</pubDate>
            <atom:updated>2022-11-13T08:34:12.318Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Algorithms you should cover in your preparation strategy.</strong></h4><p>Coding rounds can be tricky, especially when you are presented with a question you haven’t seen before! But what’s trickier is the preparation strategy you make weeks before attending that one important interview round which can almost change your career path!</p><p>The preparation strategy matters a lot! One such strategy is <strong>how to train your brain wires</strong> with the right set of input data so that it can connect the dots and think of an approach when presented with a fresh problem. This might sound like ML algorithms which are fed with training data to generate correct prediction models. Yes, the same concept applies to our brain mappings as well which require the right set of algorithms to be fed for proper training before it starts auto-generating the solutions for you. In simple words — <strong>What you sow, so shall you reap!</strong></p><p>To cut short and come back to this blog’s agenda, let us now discuss some very important algorithms and problems to be understood and practised as a part of your preparations for SDET coding interview rounds!</p><ol><li><strong>Binary Search Algorithm</strong> — You should be very comfortable with the complexity, prerequisites and implementation of the binary search algorithm. Also, practice all its variations and applications too.</li><li><strong>Sorting Algorithms — </strong>Sorting programs are rarely asked directly in coding rounds but you are expected to know the complexity comparisons and algorithms of all sorting types. <em>Ex — Insertion sort, bubble sort, merge sort, quick sort etc.</em></li><li><strong>Two/Multiple pointers (Variable) algorithms — </strong>These are further categorized below :</li></ol><ul><li><strong>Both variables start from the 0-index.</strong> <em>Ex — Sort an array of 0’s and 1’s, Move zeroes, find a substring inside a string etc.</em></li><li><strong>Both variables are initialized at opposite ends (0 and last index)</strong>. <em>Ex — Two Sum problem, Palindrome check etc.</em></li><li><strong>Fast and slow pointers algorithms</strong>. This is widely used for solving linked-list problems but can be applied to other data structures too. <em>Ex — Find the middle node of a linked list, Find a cycle in a linked list etc.</em></li></ul><p>4. <strong>BFS and DFS — </strong>You are required to be comfortable with both types of traversing algorithms. Practice the same on 2D arrays or trees. <em>Ex — Area/Parameter/Number of islands, Binary Tree related problems.</em></p><p>5. <strong>BST </strong>— Direct implementation and related problems can be asked in some product company rounds, so you can have BST-related questions as part of your strategy. <em>Ex- Validate BST, Search an element in a BST etc.</em></p><p>6. <strong>Valid Parenthesis — </strong>I am pointing out this question separately since it is one of the favourite questions of interviewers since it involved the application of Stack and Hashmap as data structures and a logical solution. Please cover this for sure.</p><p>7. <strong>2D array/matrix traversal and applications</strong> — You need to practise the searching and traversal algorithms for a 2-dimensional array. Getting a deeper understanding of its implementation and initialization will help you with this.</p><p>8. <strong>Sliding Window algorithm</strong> — The sliding window is a very intriguing technique used to solve some complex problems involving an array or a string. It is often used to reduce the time complexity of the problem from O(n²) to O(n). <em>Ex — Find the longest substring of a given string containing k distinct characters, Find the minimum sum subarray of given size k.</em></p><p>Although the above list is not exhaustive but covering the above algorithms and problems will surely help you to form patterns in your mind thus training it sufficiently enough to start connecting the dots and at least show you the possible approaches when presented with a new set of questions in the interview.</p><p>Remember, a strategised approach to preparing for coding interview rounds will help you to make your mark and score well by avoiding a total blackout which can very well happen sometimes.</p><p>See you next time.<br>Sahil Puri</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac6ff144dabb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Multiverse of Testing]]></title>
            <link>https://sahilpuri1212.medium.com/the-multiverse-of-testing-71e9c6c4d03d?source=rss-8f96ec4370bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/71e9c6c4d03d</guid>
            <category><![CDATA[sdet]]></category>
            <category><![CDATA[sdet-training]]></category>
            <category><![CDATA[test]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <dc:creator><![CDATA[Sahil Puri]]></dc:creator>
            <pubDate>Tue, 08 Nov 2022 12:57:43 GMT</pubDate>
            <atom:updated>2022-11-13T07:27:09.140Z</atom:updated>
            <content:encoded><![CDATA[<p>The secret of succeeding in modern-day testing (SDET) role.</p><p><strong>Evolution of testing role a.k.a the past and the present trend of QE role!</strong></p><p>The <em>‘test engineering</em>’ role is one of the tech roles that has evolved a lot over the last decade. The growing competition across the industry, exponentially increasing user base, the number of choices &amp; alternatives available to the user and some incredible innovations are some factors which have made consumers more aware and spoiled for choice!</p><p>This has led to an era where product quality is now seen as the foremost decisive factor for any product’s success. The quality covers usability, learnability, stability, and availability followed by a long list of these -ilities. All the above changes have brought a shift in the prioritisation strategy of leadership teams to focus on quality &amp; focus on hiring well for quality engineering teams.</p><p>With the increase of software product &amp; design complexities and end-user journeys , testing has become a core part of all SDLC phases irrespective of the development model being used. The role of ‘test/quality engineer’ has grown from being seen as a support role to now being the central limelight of the entire lifecycle of product development thus leading to higher rewards, increased responsibilities, high skill requirements and most importantly higher pay packages.</p><p>But with great rewards comes great responsibilities. The role of ‘test/<em>quality engineer’ </em>has gradually turned into what can be compared to a multiverse. Yes,<strong> the multiverse of testing.</strong></p><p><strong>What is a multiverse? How can testing be a multiverse?</strong></p><p>A Multiverse can be imagined as a universe which is beyond the known. You can also consider it as a large number of universes all combining to form a much larger entity called a multiverse.</p><p>Now let’s do a small exercise of answering a few easy questions based on your experience in the testing world.</p><ol><li>Do you ever feel that you know it all (about testing)?</li><li>Are you ever sure when to stop (testing) digging more?</li><li>Does it feel like a combination of multiple universes?</li><li>And last but not the least, do YOU trust testing?</li></ol><p>Your response to the above questions might have helped you to understand how testing can be considered as a ‘multiverse’. Now let’s welcome you all to the ‘Multiverse of Testing’.</p><p><strong>Let’s deep dive into the ‘Multiverse of Testing’</strong></p><p>The below image shows a range of planets in the form of separate roles which are a part of our multiverse. Although these planets a.k.a roles are separate universes in themselves but as test engineers, we are required to land on these planets multiple times in a day as part of our role’s R&amp;Rs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0g_lK7XXYRkRYWmg9AT_6w.png" /></figure><p>Let’s have a walkthrough of these planets -:</p><ol><li>The first planet is the ‘<strong>Product management</strong>’ planet. As a test engineer, you should be a product person and very comfortable around discussing the user journeys, user retention &amp; acquisition metrics and understand the primary metric for the hypothesis of any new feature being rolled out to production.</li><li>The second planet is the fiery one — ‘<strong>the planet of Coding</strong>’. As a test engineer, you should be comfortable with reading and writing code. Reading developer’s code will help in developing better test scenarios and test cases to verify the developer’s code. Writing code will help you to automate processes and tests to focus on tasks that deserve your full focus and intelligence.</li><li>The third planet is the ‘<strong>UI/UX</strong>’ planet. Understanding the designs &amp; related user journeys with awareness of user experience (UX) such as accessibility norms is an important trait of test engineers.</li><li>The fourth planet is the ‘<strong>DevOps tools and culture</strong>’ planet. The secret of a successful automation project lies in the DevOps culture incorporated while developing the automation strategy. As a test engineer, you need to be comfortable with using tools such as Jenkins, docker, AWS, monitoring tools and Linux commands.</li><li>The fifth planet is the ‘<strong>Release engineering</strong>’ planet. Once you are comfortable with DevOps tools, you can start contributing to the planning, management and engineering aspects of your team/org’s release strategy.</li><li>The sixth planet is the ‘<strong>Project Management</strong>’ planet. As a test engineer, we should be using prioritisation and cost &amp; time-saving techniques to juggle multiple tasks &amp; tickets every day of our professional life.</li><li>The seventh planet is the ‘<strong>Data analytics</strong>’ planet. You should be able to understand the dashboards for various production analytics like P0 user journeys, usage patterns, load patterns, etc to test and automate better,</li><li>Last but not least planet is that of ‘<strong>User reviews and concerns</strong>. This is our bread &amp; butter i.e to understand the user and prioritise his/her concerns and feedback. We have to ensure that all these concerns are reaching specific stakeholder teams as a feedback cycle and being prioritised &amp; fixed.</li></ol><p>But wait, where is the planet of ‘testing’ in this <strong>BIG</strong> multiverse? I will leave it to your exploration and request you to comment down the answer if you find one.</p><p>So next time someone asks you to define the ‘test engineering’ role, you can share this blog along with your own experiences to define the never-ending breadth of this great tech role.</p><p>See you next time,<br>Sahil Puri</p><p>P.S — Please follow for more content on testing, automation &amp; leadership.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71e9c6c4d03d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[All about cracking the Coding interviews.]]></title>
            <link>https://sahilpuri1212.medium.com/cracking-the-sdet-coding-interviews-758b25a878e1?source=rss-8f96ec4370bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/758b25a878e1</guid>
            <dc:creator><![CDATA[Sahil Puri]]></dc:creator>
            <pubDate>Sun, 06 Nov 2022 13:05:33 GMT</pubDate>
            <atom:updated>2022-12-03T19:32:43.021Z</atom:updated>
            <content:encoded><![CDATA[<h4>The secret sauce, tips &amp; evaluation scheme.</h4><p>Coding interview rounds can be challenging, unpredictable and scary. These are often the knockout rounds for most interview processes and have become an important pillar of evaluating candidates for almost all technical roles including development and testing.</p><p>Many candidates still cannot understand the purpose of having a coding round in the SDET role interviews. Let’s go a bit deeper into the <strong>WHY</strong> of having a coding interview round for SDET roles.</p><blockquote><strong>Understanding the purpose of coding rounds for the SDET role</strong></blockquote><p>Well, for starters, the coding round helps in evaluating the programming aptitude of the candidate with the level of comfort around the usage of data structures &amp; algorithms. The hiring manager is interested in multiple aspects of your personality -:</p><ol><li><strong>Technical Skills</strong> — This is evaluated by checking your c<strong>ommand over programming language rules/syntax</strong>, the comfort of applying <strong>data structures</strong> to design an efficient algorithm and the ability to design unit-level test cases to verify your code.</li><li><strong>Problem-solving skills</strong> — This is evaluated by checking your <strong>approach</strong> of solving a problem at hand and <strong>fast thinking</strong> under time bound situation (<em>often 45 minutes or even less time allotted to solve a coding question</em>).</li><li><strong>Logical Skills</strong> — This is evaluated by checking your <strong>reasoning ability</strong> in search of the optimised solution and <strong>thinking logically</strong> when trying to solve a problem. The way you justify your approach and use of specific data structures with time and space complexity comparisons play an important role here.</li><li><strong>Pair programming skills — </strong>This is evaluated by the <strong>teamwork</strong> shown by you when trying to solve a problem together with the interviewer as a colleague. A calm, patient &amp; humble attitude with <strong>great listening skills </strong>plays an important role here.</li><li><strong>Communication skills — </strong>This is evaluated by your ability to put your <strong>thoughts, ideas and solutions</strong> in simple words in the interview language (Ex- English).</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*73xZifvfQ70Z5tdBz9wI6A.png" /></figure><p>Considering the day-to-day role &amp; responsibilities of an SDET engineer across the industry, the above skills make up a strong indicator &amp; benchmarking strategy for aspiring SDET candidates. So next time you appear for a coding interview, do remember that you are being judged on multiple levels and different aspects.</p><p>In the hindsight, it is a breather for the candidates too since it provides an opportunity to show your overall skillset &amp; personality traits to the hiring manager thereby offering a balance.</p><p>Now the question arises as to how to score well and clear these coding rounds. The secret sauce lies in understanding the<strong> step-wise marking scheme of these rounds</strong>. Yes you heard it right, there is a step-wise marking scheme and you have the luxury of scoring good marks and cracking the round even if you are not able to reach the optimised solution within the stipulated time.</p><blockquote><strong>Evaluation &amp; Assessment marking scheme in coding rounds</strong></blockquote><p><strong>Step 1:</strong> Queries asked by the candidate when presented with an open-ended problem</p><p><strong>Step 2</strong>: Thinking and sharing the logical approaches with comparison before actually starting to code.</p><p><strong>Step 3</strong>: Agree on an optimised solution and start to code with a loud thinking hat.</p><p><strong>Step 4</strong>: Dry run and test the code before submitting the final solution.</p><p><strong>Step 5</strong>: Able to reach an optimised solution &amp; submit a working code within the allotted time.</p><p><strong>Step 6</strong>: Writing 4–5 unit-level P0 test cases &amp; input data to test the code.</p><p><strong>Step 7 </strong>: Able to debug and fix any bug in the code which is discovered by either party.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*seNE98yEPjqr49DOOdd5lA.png" /></figure><p>Take a deep breath and read the above steps to form a template of your solution and score maximum points in the coding interview.</p><blockquote><strong>Important tips for your preparation</strong></blockquote><ol><li><strong>Focus on logic building and forming patterns </strong>in your mind with regular practice of competitive programming questions.</li><li><strong>Take notes of these logical patterns </strong>and revise them regularly for your brain wires to gradually start applying them to the new set of questions thrown at you.</li><li><strong>Start with the habit of 4 coding programs per day</strong> including writing code, taking notes, designing test cases and logical pattern building.</li><li>Practice different patterns of the <strong>array and string-related questions.</strong></li><li>Understand the <strong>application of data structures</strong> with the language of your choice and <strong>at least cover linked lists, stacks, queues, and trees </strong>in data structures.</li><li>Revise all types of <strong>searching and sorting algorithms.</strong></li><li>Be very confident around the concept of<strong> time and space complexity.</strong></li><li><strong>Try different approaches </strong>to solve a particular problem, this will give you an insight &amp; ability to analyze how one approach can be effective over other approaches especially using time and space Complexity.</li><li><strong>Coding is like mathematics</strong>, there are no shortcuts and consistent practice is the only way to master this art!</li></ol><p>This is all for this blog where we covered the real purpose of coding rounds in SDET role interviews, skills that hiring managers are looking out for, step-wise marking scheme of coding rounds and some useful tips to help with your preparation around cracking these interviews. I hope this will give you a head start in your endeavour and road to success.</p><p><strong>Bonus: FAQs</strong></p><p>Q1. What kind of rounds can we expect in product-based companies?<br>R1. The most common interview rounds for the SDET role are testing, automation and coding rounds. But yes, sometimes there can be design &amp; framework development rounds as well for specific roles and companies depending on your experience.</p><p>Q2. What DS topics you mentioned enough to crack SDET coding rounds? Can we skip advanced DSA like DP, tries etc?<br>R2. You can start giving interviews after practising below DS based programming questions at the beginner level -:</p><ol><li>Array [1D,2D,3D]</li><li>String manipulation and related logical problems</li><li>Stack &amp; Queue</li></ol><p>After the above topics are covered and once you are confident with building logical solutions, start practising the below data structure-based problems</p><ol><li>Linked lists</li><li>Maps &amp; Sets</li><li>Trees</li></ol><p>The Above data structures are enough to get you started and crack most of the interview rounds. You should look for graphs, tries based questions only when you are confident of the above DSA-based questions.</p><p>Q3. Why am I supposed to study DSA? Is there any relevance of my work with it?<br>R3. Yes, of course! DSA knowledge will help to solve real-world problems at your actual job while automating a process or test suite, building a framework, understanding the developer’s code to design a test plan, etc. So be assured, DSA knowledge will help you not only succeed in interviews but in actual job R&amp;R as well.</p><p>Q4. When can I feel confident enough to start applying for jobs and giving interviews?<br>R4. There is no perfect time to start applying and appearing in interviews. Give your preparation a time period of ~3–4 weeks and start applying for jobs. The secret lies in continuous improvement of your skills based on runtime feedback from these interviews and consistent practice with revision.</p><p>See you next time<br>Sahil Puri</p><p>P.S — Please follow for more content on testing, automation &amp; leadership.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=758b25a878e1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>