<?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 Pratik Thorve on Medium]]></title>
        <description><![CDATA[Stories by Pratik Thorve on Medium]]></description>
        <link>https://medium.com/@pratikthorve?source=rss-8ab3bc23ab6d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*W_aAuwX00iPeE9DhmK4FaQ.jpeg</url>
            <title>Stories by Pratik Thorve on Medium</title>
            <link>https://medium.com/@pratikthorve?source=rss-8ab3bc23ab6d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 09:36:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pratikthorve/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[Building a Quality Culture]]></title>
            <link>https://pratikthorve.medium.com/building-a-quality-culture-20a4d04a6485?source=rss-8ab3bc23ab6d------2</link>
            <guid isPermaLink="false">https://medium.com/p/20a4d04a6485</guid>
            <category><![CDATA[software-testing]]></category>
            <dc:creator><![CDATA[Pratik Thorve]]></dc:creator>
            <pubDate>Thu, 07 Dec 2023 12:09:28 GMT</pubDate>
            <atom:updated>2023-12-07T12:09:28.240Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xThX2JP_7h4hjGKXb-476A.jpeg" /></figure><p>Delivery high quality software is a goal that all companies live by in todays world , its a goal that is necessary for survival of a company. Remember the feeling you had when you encountered a poor peice on software that did not do what it was supposed to do. We cannot change Quality culture overnight, it requires a dedicated effort to develop a quality culture in a software organization. A culture of quality is not only about catching bugs before release; it’s about fostering an environment where quality is imprinted in every aspect of the development process, right from ideation to deployment , its about building a foundation for a long term success.</p><p><strong>A quality culture offers numerous benefits:</strong></p><p><strong>Reduced bugs / errors</strong>: Proactive quality practices lead to fewer bugs and issues, resulting in a stable product.</p><p><strong>Increased customer satisfaction</strong>: Delivering high-quality software leads to happy customers, a happy customer is a loyal customer and a advocate of the product.</p><p><strong>Reduced costs</strong>: Quality issues are expensive to fix after release. By investing in quality throughout the development process, you can save money in the long run.</p><p><strong>Improved team morale and productivity</strong>: When developers feel invested in delivering quality work, they are more motivated and engaged.</p><p><strong>What can be done to build a Quality Culture:</strong></p><p><strong>Define and communicate your quality standards</strong>: Clearly define what quality means for your organization in measurable standards. Communicate these standards to everyone involved in the software development process. This standards can performance, security, reliability, user experience, and anything that you consider is important and is mesurable, please see that you align yourself with industry standards as benchmark.</p><p><strong>Shift left testing / Early integration</strong>: Integrate testing activities earlier in the development cycle at each stage of the development process , allowing for early detection and correction of defects.</p><p><strong>Encourage ownership</strong>: Encourage developers to take ownership of the quality of their work. Give them the resources and autonomy they need to make quality decisions.</p><p><strong>Collaboration and knowledge sharing</strong>: Foster a culture of collaboration and knowledge sharing between developers, testers, and other stakeholders. This helps to break down silos and ensure everyone is working towards a common goal. Remember the Tester is not your enemy.</p><p><strong>Invest in automation</strong>: Automating repetitive will free up developer time for more strategic activities. Automated testing tools help to improve efficiency and consistency. But just don`t go ahead and automate everything , think of ROI first.</p><p><strong>Celebrate successes and learn from failures</strong>: Recognize and reward teams for achieving quality goals. Encourage open collaboration and communication, learning from both successes and failures.</p><p><strong>Provide continuous feedback and training</strong>: Offer regular feedback and opportunities for professional development to help developers improve their skills and knowledge.</p><p><strong>Use data to drive decision-making</strong>: Leverage data from testing and other sources to identify areas for improvement and track progress over time. Track how your test are performing , are the test flaky , are you not getting results from the test ? are the test not helping while making decision ?</p><p><strong>Lead by example</strong>: Leadership Team plays a critical role in setting the roadmap for a quality culture. Leaders must be dedicated to this initiative and demonstrate this commitment through their words and actions.</p><p><strong>Be patient and persistent</strong>: Building a quality culture takes time and effort it`s not a one day process. Don’t get discouraged by setbacks. Be persistent and continue to invest in your quality initiatives.</p><p><em>Remember quality is a not a 1 person job , it&#39;s a shared responsibility !</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=20a4d04a6485" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 lessons from a Decade in Test Automation]]></title>
            <link>https://pratikthorve.medium.com/5-lessons-from-a-decade-in-test-automation-eb33d63bded0?source=rss-8ab3bc23ab6d------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb33d63bded0</guid>
            <category><![CDATA[software]]></category>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Pratik Thorve]]></dc:creator>
            <pubDate>Mon, 01 Nov 2021 11:08:22 GMT</pubDate>
            <atom:updated>2021-11-01T11:08:22.159Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lIFhfz5Il-mdbi7MdDOvEQ.jpeg" /></figure><p>September 2011 , I started as a Systems Engineer with Infosys , a Decade later today I am with Priceline working as a SDET.</p><p>Working in the test automation space for 10 years , across multiple organisations and projects with different background made me jot down the below points which serve as guiding force me everyday , I have listed them below so that all of us can benefit from it.</p><p><strong>1 Independent Test :</strong></p><p>The most important criteria I believe in , all test are independent of each other , they do not touch , interact or have no dependency on other test cases.At start this looks as a burden but in future when the test automation suite grows then this is the saviour for you.</p><p><strong>2 Clear and Concise Reporting :</strong></p><p>There is no point in running test automation if you cannot report it well. The report should be precise it should be well documented and explain what was tested, which environment was used , how many test cases passed , how many failed. For failure ensure you are reporting the point of failure the expected and actual output.</p><p>If you can add graphics , screenshots, logs that is well appreciated !</p><p><strong>3 Distribute you Test :</strong></p><p>There is a reason that we have test pyramid and we need all should follow it, every application comes with layer and we need to ensure that the test are distributed across all the layers. This results in faster feedback and better control for test execution. The general layer can be Unit , API and then E2E , we can further subdivide them as needed.</p><p><strong>4 Clear Test Cases :</strong></p><p>Each test case should be clear and pin point what it’s going to do. The less the number of validations the better is the resultant test case for future maintenance.There is no point in adding random stuff in test cases which will be difficult to figure out down the line. In a ideal world the test name should describe what its doing and it should do what it describe no surprises when you look under the code !</p><p><strong>5 Automation That adds Value :</strong></p><p>The most important , when you are automating think about ROI not short term but about long term. Automation should ease you job and not complicate it right :)</p><p>And the most important , Automation is a TEAM effort , involve your developers , your product owner , involve everyone , each of team member should understand what we are doing, why we are doing it and the role it will play towards the success of the project in the long term , we do it as a Team !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb33d63bded0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>