<?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 Product Panda on Medium]]></title>
        <description><![CDATA[Stories by Product Panda on Medium]]></description>
        <link>https://medium.com/@productpizzazz?source=rss-8b53772ebc51------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*tBTbA0cr9v2LPHyNXzvMXg.png</url>
            <title>Stories by Product Panda on Medium</title>
            <link>https://medium.com/@productpizzazz?source=rss-8b53772ebc51------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 11:18:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@productpizzazz/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[Signs That Your Founders Are Awesome]]></title>
            <link>https://medium.com/@productpizzazz/signs-that-your-founders-are-awesome-3d8e85d7f8c8?source=rss-8b53772ebc51------2</link>
            <guid isPermaLink="false">https://medium.com/p/3d8e85d7f8c8</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[employee-engagement]]></category>
            <category><![CDATA[founders]]></category>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[opinion]]></category>
            <dc:creator><![CDATA[Product Panda]]></dc:creator>
            <pubDate>Sun, 04 Jan 2026 16:42:44 GMT</pubDate>
            <atom:updated>2026-01-04T16:42:44.126Z</atom:updated>
            <content:encoded><![CDATA[<h3>Signs That Your Founders is Awesome</h3><h4>It is never about just money, free goodies, and flashy perks; it’s about the experience and inclusiveness that keep talent invested, loyal, and willing to grow with the company.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7uC8fUM_gL79RYhz" /><figcaption>Photo by <a href="https://unsplash.com/@shannonrowies?utm_source=medium&amp;utm_medium=referral">Shannon Rowies</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Founders are visionaries — navigators who show the path to 250 individuals working together to solve problems. While there are countless qualities that make a great founder, I’ve observed some that make me confident we’re in the hands of amazing and honest leaders.</p><p>Working closely with them, participating in their meetings, and getting to know them better has been a learning opportunity I cherish. Let me share some characteristics that have impressed me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RvzhuhHTxqgy6XVF" /><figcaption>Photo by <a href="https://unsplash.com/@lacyec?utm_source=medium&amp;utm_medium=referral">Lacyec</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Make it 50–50</h3><p>It was a simple rule to eliminate waste in the company: nothing is free. Initiatives like bulk-purchased WiFi extenders and gym passes are split 50–50 between the company and employees. This wasn’t an arbitrary decision — it came from experience with excess inventory of company goodies that became difficult to manage. The policy ensures that only those who truly need these items request them.</p><h3>Discuss How Company is Doing</h3><p>MIS reports are shared to maintain transparency. This could be controversial — it requires trusting employees to keep confidential information to themselves. Every employee learns how the company is performing and its future potential.</p><p>Management information systems (MIS) reports are shared openly across the organization to build trust and transparency. Some might see this as risky since it involves sharing sensitive financial and operational data with everyone. However, our leadership believes in the power of information sharing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*44xmPEBAnKHCD9sA" /><figcaption>Photo by <a href="https://unsplash.com/@art_maltsev?utm_source=medium&amp;utm_medium=referral">Artem Maltsev</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Every team member gains insights into the company’s performance, metrics, and strategic direction. This understanding helps employees align their work with company goals, see the impact of their contributions, and connect more deeply with where we’re heading.</p><h3>Accepting mistakes</h3><p>People make mistakes, but the stakes are much higher when they come from someone in a position of importance. During a difficult period, the company had to undergo a round of layoffs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*s77IanpayO9u2w27" /><figcaption>Photo by <a href="https://unsplash.com/@framesforyourheart?utm_source=medium&amp;utm_medium=referral">Frames For Your Heart</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Many employees were sad and confused as time passed, watching their colleagues leave one by one. Though the founders weren’t obligated to address the situation, they showed true leadership the next day. They rolled up their sleeves, gathered everyone together, and transparently explained the circumstances behind the layoffs — discussing both the impact of the recession and the challenge of over-hiring.</p><p>This kind of honest communication, especially during tough times, demonstrated their commitment to transparency and respect for their employees.</p><h3>Data Driven</h3><p>Nothing is taken into account without data.</p><p>We are experiencing bandwidth crunch.</p><p>Bring me proof show me story points assigned to each individual. If you can’t show them change the process to track them numbers matter the most. And even when they clarifying each and every charts during MRM (monthly review meetings) are out of the world.</p><p>Data removes biases and they do that exactly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VMq8tIh-pF2q9z8V" /><figcaption>Photo by <a href="https://unsplash.com/@austindistel?utm_source=medium&amp;utm_medium=referral">Austin Distel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Value People Hired</h3><p>As a QA myself, I witnessed the company’s decision to remove dedicated QA roles in favor of full-stack engineers proficient in front-end, back-end, and DevOps. The goal was to leverage AI tools to maximize each person’s potential. It was similar to the Matrix movie. I was given a choice to either shift companies or take up development. I chose the development path because I knew I was flexible, and I would be able to take it up.</p><p>It was not a direct shift. I had to commit to a six-month period where my development skills would be tested. Based on my performance, I would then be promoted. I’m grateful for this approach — it felt like my decision, even though there were plenty of developers in the market who could have easily replaced me. Instead of simply hiring someone new, they chose to invest six months in transitioning a QA engineer to a developer role. That says something powerful about how much they value their people.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zKW1QnGGeK9tmXg1" /><figcaption>Photo by <a href="https://unsplash.com/@silverkblack?utm_source=medium&amp;utm_medium=referral">Vitaly Gariev</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>My goals are clearly defined and reviewed every three months, giving me a clear view of what I should accomplish over the next six months. These practices make me feel deeply connected to the company and motivated to do better!</p><h3>Experimenting with AI</h3><p>AI is the new oil — harness it or be left behind. AI skills have become essential for every employee to maximize their potential and output. We were early adopters of Cursor, even when their payment system wasn’t fully polished.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*C5JzfHydIfVQzgIz" /><figcaption>Photo by <a href="https://unsplash.com/@diana_pole?utm_source=medium&amp;utm_medium=referral">Diana Polekhina</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>We experimented with multiple AI tool subscriptions, scratching some and keeping others. Each subscription was carefully tracked to ensure it was removed if not being used effectively.</p><p>Happy Testing!</p><p>Author: <a href="https://in.linkedin.com/in/m2kishore">M M Kishore</a></p><p>Stay connected and stay informed with ProductPanda! If you’re a recent graduate who’s hungry for tech-knowledge, make sure to follow us 🎉 on our journey 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d8e85d7f8c8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning Isn’t Free: The 3-Phase Journey That Transformed My Skills]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@productpizzazz/learning-isnt-free-the-3-phase-journey-that-transformed-my-skills-ae5244a25c9e?source=rss-8b53772ebc51------2"><img src="https://cdn-images-1.medium.com/max/640/1*vZsWvSWFPAn0OX64X6RlhQ.jpeg" width="640"></a></p><p class="medium-feed-snippet">From free tutorials to paid meetups and mentors&#x200A;&#x2014;&#x200A;how passion, money, and guidance reshaped my learning and career journey</p><p class="medium-feed-link"><a href="https://medium.com/@productpizzazz/learning-isnt-free-the-3-phase-journey-that-transformed-my-skills-ae5244a25c9e?source=rss-8b53772ebc51------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@productpizzazz/learning-isnt-free-the-3-phase-journey-that-transformed-my-skills-ae5244a25c9e?source=rss-8b53772ebc51------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae5244a25c9e</guid>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[mentorship]]></category>
            <dc:creator><![CDATA[Product Panda]]></dc:creator>
            <pubDate>Wed, 09 Apr 2025 17:43:47 GMT</pubDate>
            <atom:updated>2025-04-16T02:23:22.271Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[I spent 2000 on ChatGPT — here’s my verdict as a QA]]></title>
            <link>https://medium.com/@productpizzazz/i-spent-2000-on-chatgpt-heres-my-verdict-as-a-qa-dcc6633827ad?source=rss-8b53772ebc51------2</link>
            <guid isPermaLink="false">https://medium.com/p/dcc6633827ad</guid>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[chatgpt]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Product Panda]]></dc:creator>
            <pubDate>Tue, 18 Feb 2025 02:29:10 GMT</pubDate>
            <atom:updated>2025-03-01T12:20:25.269Z</atom:updated>
            <content:encoded><![CDATA[<h3>I spent 2000 on ChatGPT — here’s my verdict as a QA</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ELJXBhg5lR8KhizW" /><figcaption>Photo by <a href="https://unsplash.com/@jpvalery?utm_source=medium&amp;utm_medium=referral">Jp Valery</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I met this guy named <a href="https://in.linkedin.com/in/ajaybalamurugadas">Ajay Balamurugadas</a>.</p><p>He was a veteran tester. He presented a talk on “Career Chakravyuh”. His view on career progression was not performing bad ass rather that small habits which will improve ourselves and those improve ments keep us relevant in the market. His approach made me realize that the goal is to <strong>make sufficient money without sacrificing hobbies and health while being a valuable person</strong>.</p><p>By the end of the talk he pulled out his browser running chatGPT and he prompted chatGPT such a way that it was able to bring out his bare minimum idea into a full fledged speech that brought a different dimension on looking at work. He took the speech and put it into <a href="http://napkin.ai/">napkin.ai</a> and</p><p>Boom !!</p><p>He created a PDF file with cool flow charts and bullet points on what he is going to present.</p><p>He only spent 3 hours for a stella performance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nKbMhdoVYK3V28pEeRSBgw.png" /></figure><p>He used chatGPT plus version and recommended us to get a subscription which will help us save a lot of time.</p><p>I have been using a bit of GitHub copilot, cursor(exploratory phase), and chatGPT on my day to day basis and constantly shifting the accounts to get the limited chatDPT 4o. I have also been using it to check grammar on my writing as well and rewriting some of my ideas to better suited my audience.</p><p>I pulled out my debit card took a deep breath and stripped away 2000rs including 18 percentage GST. That was 7 birianis or 20 movies in total.</p><p>News Flash!</p><p>I brought the coolest tool but didn’t know how to use it to its full potential.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vwhfcYMQ8ad9tez4w-9wyA.png" /></figure><h3>Week 1</h3><p>Using my ChatGPT subscription, I started noticing how much time I was actually saving:</p><p>• <strong>Instagram Captions:</strong> Friends began asking me for ideas, and I found myself generating decent ones quickly.</p><p>• <strong>Health &amp; Wellness:</strong> I uploaded a picture of my dad’s diagnostic report and was able to put together a basic meal plan and exercise routine — something that would have taken much longer on my own.</p><p>• <strong>Content Creation:</strong> Instead of spending time searching for stock photos, I experimented with generating images for my blog, which was surprisingly effective.</p><p>It made me wonder — was I really becoming more efficient, or just relying on AI in new ways?</p><h3>Month 1</h3><p>I also started using it to streamline my learning:</p><p>• During presentations and workshops, I would take quick <strong>screenshots</strong> and later turn them into structured <strong>notes</strong> for future reference.</p><p>• Instead of just passively listening, I was actively <strong>building a knowledge base</strong> for myself.</p><p>• I prompted ChatGPT for <strong>relevant examples</strong>, making my learning deeper and more practical.</p><p>The best part?</p><p>It felt effortless.</p><p>I had always wanted to be more efficient with my time, and now I had the ultimate tool. Looking back, that subscription wasn’t just an expense — it was an <strong>investment</strong> that was already paying off in ways I hadn’t expected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VQuD3xlzAKnmyFfG" /><figcaption>Photo by <a href="https://unsplash.com/@amseaman?utm_source=medium&amp;utm_medium=referral">Andrew Seaman</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>When learning about a new product created by my company, I realized that my current product had dependencies on it. To <strong>devise effective end-to-end tests</strong>, I needed to understand how the new product functioned and how it interacted with our existing system. This was crucial to ensuring that the <strong>flow was properly verified before release</strong>.</p><p>However, as I dug deeper, I encountered business-centric terminology and features that didn’t initially make sense to me.</p><p>For example:</p><p>• <strong>“You can send more products than the ordered quantity”</strong> — Why was this even a feature? It seemed counterintuitive at first, but I later realized there could be specific business cases where over-delivery was intentional, such as handling supply chain shortages or fulfilling bulk orders.</p><p>• <strong>What is ERP?</strong> — This term kept popping up, and I had to dive into understanding <strong>Enterprise Resource Planning (ERP) systems</strong> — software used to manage and automate core business processes like inventory, procurement, and order fulfillment.</p><p>These questions helped me bridge the gap between <strong>technical functionality and business logic</strong>, ensuring that my tests weren’t just verifying workflows but also aligning with real-world use cases.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3KENOCl-GPJyuNMC" /><figcaption>Photo by <a href="https://unsplash.com/@roadtripwithraj?utm_source=medium&amp;utm_medium=referral">Road Trip with Raj</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Month 2</h3><p>I ventured out looking for a good course to <strong>enhance my prompting techniques</strong> and stumbled upon a gem on Coursera. The best part? It was <strong>free if you audit the course</strong>!</p><p>🎉 <strong>Drum roll!</strong> 🎉</p><p>🔗 <a href="https://www.coursera.org/learn/prompt-engineering/home/welcome">Prompt Engineering for ChatGPT — Coursera</a></p><p>The course covered <strong>various prompting techniques</strong>, and the funny realization was that with what I learned, I could <strong>ask ChatGPT to teach me anything</strong> or even <strong>write a prompt to make the best use of itself</strong>! It felt like unlocking a secret mode where I could continuously refine my interactions with AI for better results.</p><p>As I got better at prompting, I noticed a surprising improvement in my <strong>communication skills</strong> as well.</p><p>• I started <strong>giving more context</strong> when asking others for help, reducing friction and making it easier for them to assist me.</p><p>• I began structuring my questions <strong>like ChatGPT prompts</strong>, making conversations clearer and eliminating ambiguity.</p><p>• This not only made my interactions more efficient but also helped me <strong>learn faster and collaborate better</strong>.</p><p>It turns out, learning to <strong>ask better questions</strong> doesn’t just improve AI interactions — it makes <strong>real-world conversations more meaningful too</strong>!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ls6S6T_g1vIDvmPK" /><figcaption>Photo by <a href="https://unsplash.com/@carrier_lost?utm_source=medium&amp;utm_medium=referral">Ian Taylor</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>How am I planning to get better?</h3><p>Joining <strong>The Test Tribe Finer Circle</strong> has been a game-changer for me. It gives me access to <strong>courses on Testing, AI masterclasses, and a strong community</strong> where I can stay accountable for my goals. This is not just about learning; it’s about actively applying new skills and pushing myself to improve. One of the areas I’m excited to explore is <strong>AI APIs</strong> — understanding how they work and how I can integrate them into my daily workflow for better efficiency. I’m also keeping an eye on <strong>AI agents and operators</strong>, especially if they become more affordable, as they could significantly enhance automation and decision-making in my work.</p><p>At the same time, my company is looking to <strong>transition testers like me into developers</strong>, so I’ve started diving into AI-assisted coding tools like <strong>GitHub Copilot and Cursor</strong>. These tools are helping me bridge the gap between testing and development, making it easier to write and understand code. It’s a shift that feels both challenging and exciting, and I’m looking forward to seeing how AI can enhance my ability to build and test software more effectively.</p><p>Happy Testing!</p><p>Author: <a href="https://in.linkedin.com/in/m2kishore">M M Kishore</a></p><p>Stay connected and stay informed with ProductPanda! If you’re a recent graduate who’s hungry for tech-knowledge, make sure to follow us 🎉 on our journey 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dcc6633827ad" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How APM Turns Load Testing from Meh to Magic]]></title>
            <link>https://medium.com/@productpizzazz/how-apm-turns-load-testing-from-meh-to-magic-8c1f6d774160?source=rss-8b53772ebc51------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c1f6d774160</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[qa]]></category>
            <dc:creator><![CDATA[Product Panda]]></dc:creator>
            <pubDate>Sat, 04 Jan 2025 06:24:07 GMT</pubDate>
            <atom:updated>2025-01-04T08:33:56.444Z</atom:updated>
            <content:encoded><![CDATA[<p>APM + Load Testing = The Ultimate Performance Power Couple</p><p>Before I start my TED Talk on load testing nightmares and the so-called ‘learnings’ along the way, can we at least agree on what load testing is?</p><p>Load testing is a way to see how well a system (like a website or app) can handle a large number of users simultaneously. It’s like seeing if a bridge can handle heavy traffic without collapsing. The goal is to find the breaking point and fix any weaknesses before real users face issues.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X1vr-lWwvjL85vaqjOzVkA.png" /></figure><p>I only stumbled upon load testing six months into my job as a QA. My definition of it has evolved over the last 1.5 years. My first attempt at load testing? I watched a random YouTube video on JMeter(an application used to load tests), threw in 3–4 APIs, bombarded the app with 10,000 requests, and declared it a success because the machine didn’t explode(just exaggerated “stopped running”).</p><p><strong>Classic, right?</strong></p><p>It worked, so I thought I had aced load testing. Now, I know I was missing about 99% of what load testing is supposed to check. I felt that as long as there were no errors in the response or I didn’t see any 500 errors(the backend server is not running status), the load testing was a success.</p><p>However, this approach is insufficient to ensure the application under test is truly robust and reliable.</p><p>The Vitals in the JMeter summary were useful with information on:</p><ul><li><strong>Error</strong> <strong>%</strong> — The percentage of requests that failed during the test.</li><li><strong>Throughput</strong> — The number of requests processed by the server per second or minute</li><li><strong>Average</strong>: The average response time (in milliseconds) for the samples collected.</li><li><strong>Min</strong>: The minimum response time observed for the samples.</li><li><strong>Max</strong>: The maximum response time recorded during the test.</li><li><strong>Std. Dev.</strong>: The standard deviation of the response times, showing how much the response times deviate from the average. A higher value indicates more variability.</li><li><strong>Received KB/sec</strong>: The amount of data received from the server per second, measured in kilobytes.</li><li><strong>Sent KB/sec</strong>: The amount of data sent to the server per second, also in kilobytes.</li><li><strong>Avg. Bytes</strong>: The average size of responses in bytes.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/596/1*JJQ2Tv5vknmD6DltGaV1aA.png" /></figure><h3>Why JMeter’s Summary is not Enough?</h3><p>We gathered quite a bit of information from JMeter, but as a tester, it wasn’t enough for me to truly understand how the application performs in the wild(real world).</p><p>The information that JMeter provides is specific to API performances but, there is more than just API performance to be monitored. Here is where APM comes into the picture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/1*kgBhjGyMHL_XsItxBcNmtg.jpeg" /></figure><h3>What is APM?</h3><p>APM stands for Application Performance Monitor/Management. It’s like a health tracker for your app, showing you how well it’s running in real time. APM tools help you:</p><ul><li>See how fast your app responds to users</li><li>Find and fix slow parts of your app</li><li>Understand how different parts of your app work together</li><li>Get alerts when something’s not working right</li></ul><p>APM gives you a fuller picture of your app’s performance than just looking at API stats.</p><p>The stats include:</p><ul><li><strong>CPU %</strong> : The percentage of CPU resources utilized at a specific point in time</li><li><strong>Memory Usage</strong> : The amount of RAM currently in use.</li><li><strong>Heap Memory Usage</strong> : This refers to the amount of RAM consumed from the allocated memory for the application. Once the heap memory is exhausted, the application cannot exceed the allocated memory, thus avoiding interference with the memory allocated to other applications.</li><li><strong>Garbage Collection</strong> : The process in which the Java Virtual Machine (JVM) automatically reclaims memory by identifying and removing objects that are no longer in use, freeing up space for new object allocations and improving application performance.</li><li><strong>Thread Pool Utilisation</strong> : For applications with multi-threading (like Java), monitoring thread pool usage helps ensure there are enough available threads to handle requests efficiently and avoid bottlenecks.</li><li><strong>Latency </strong>: Measures the time taken for data to travel from the client to the server and back. High latency can result in slow application response times.</li><li><strong>Apdex Score (Application Performance Index) </strong>: A user satisfaction measurement based on response times. It scores app performance as satisfactory, tolerating, or frustrating.</li><li><strong>Database Query Performance </strong>: Tracks the time taken for database queries and the number of queries executed per request. Slow or frequent queries can impact overall application performance.</li></ul><h3>Let me share some conditions I have come across in my journey:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*soS3dFejFlgSm-WbIXywJQ.png" /></figure><h4><strong>The CPU:</strong></h4><p>The CPU usage should remain below 80%, but it can peak up to 90% during high-demand periods.</p><p>It’s also crucial to check the alerting systems during load testing to ensure that when thresholds are reached, there’s sufficient time to scale up the CPU and minimize potential downtime. In cases like upcoming sales, we typically double the server capacity during the first and last few days, especially when working within a tight budget.</p><p>While these practices are common in established companies, in startups, it’s important to communicate the expected maximum throughput (number of calls per unit time) to stakeholders so they can take the necessary precautions for a smooth workflow.</p><h4><strong>Memory:</strong></h4><p>RAM plays a vital role in boosting application performance without the high expense of upgrading the CPU.</p><p>Not always but only when the application needs some extra space during unforeseen circumstances like high memory-consuming API calls like synchronization data calls which are not triggered very often. Increasing RAM is not the only solution that will solve memory consumption there is another elephant in the room I found</p><p>which is…</p><h4><strong>Heap Memory:</strong></h4><p>Heap memory is the memory an application can use Even though the virtual machine or the on-prem machine has tons of memory if the heap memory is set to a lower value by default, the application will only be able to utilize the allocated portion of memory.</p><p>This constraint can lead to <strong>OutOfMemoryError</strong> if the application tries to use more memory than allocated in the heap.</p><h4><strong>Garbage Collection:</strong></h4><p>If it occurs in a regular rhythm, the system is mostly stable.</p><p>However, if it becomes erratic or irregular, there may be a memory leak that needs to be addressed. We can still dive deep into the rabbit hole of different garbage collector algorithms but those are for another day. When there is an anomaly in the garbage collector the developer usually gets a dump of the data and analyses it. You can also take part in finding the root cause.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*cbqma6euF7hq_J7wX8Z9rQ.png" /><figcaption>A Good Performing Garbage Collector Graph</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*PsjnKHCSX7aVw1mdC8fBUg.png" /><figcaption>A Struggling Garbage Collector due to Memory Leak</figcaption></figure><h4><strong>Thread Pool Utilization:</strong></h4><p>When working with a Java-based web application, multiple threads are created to handle incoming requests. In scenarios involving high demand or memory leaks, the number of threads can grow excessively, potentially causing the server to crash. To mitigate this, it is recommended to configure proper timeouts to terminate threads that remain idle or unresponsive for too long. While increasing the thread pool size is a cost-effective way to handle sudden traffic spikes, this solution is temporary. If the traffic surge persists, the CPU may struggle to process tasks as fast as they accumulate in memory. This imbalance can lead to performance bottlenecks, eventually requiring a CPU upgrade to maintain stability and responsiveness.</p><h4><strong>Latency:</strong></h4><p>The acceptable latency varies depending on the type of application.</p><p>For example: Stock exchanges and gaming platforms require extremely low average latency (around 17 milliseconds) for optimal performance. • Internal communications between microservices in certain applications might demand latency measured in nanoseconds. • For typical web-based applications, a latency of 30–40 milliseconds is considered ideal, while latencies below 1000 milliseconds are generally acceptable during peak demand periods.</p><p>While increasing the CPU capacity can help reduce latency, the improvement is not always linear. Additionally, user location plays a significant role in determining latency, as physical distance and network conditions can impact response times.</p><h4><strong>Apdex Score</strong>:</h4><p>I was unfamiliar with this score until I researched the topic. It provides an overall assessment of how well an application performs.</p><p>The score ranges from 0 to 1, with 1 representing perfect user satisfaction. For example, if your application consistently responds within the defined threshold (typically under 4 seconds), it will achieve a higher Apdex score. This metric is especially valuable during load testing as it offers a clear, numerical representation of user satisfaction levels.</p><p>An excellent score ranges from 1.00 to 0.94, a good score falls between <strong>0.93 and 0.85</strong>, a fair score is between 0.84 and 0.70, and a poor score is between 0.69 and 0.49. Any value lower than this is considered unacceptable. These thresholds may vary depending on the context of the application.</p><pre>              SatisfiedCount + (ToleratingCount * 0.5) + (FrustratedCount * 0)<br>Apdex t =    ----------------------------------------------------------------<br>	                          		TotalSamples</pre><h4><strong>Database Query Performance:</strong></h4><p>Slowness in the application might be caused by database queries taking too long to execute. You can identify these issues by monitoring the query execution times. For database-intensive applications, analyze the queries to identify opportunities for optimization and improve overall performance.</p><p>As a tester, having a foundation in computer science fundamentals and understanding application architecture can be invaluable. This knowledge enables more meaningful conversations with developers and DevOps teams when discussing performance optimization strategies.</p><p>When you understand concepts like memory management, threading, and database optimization, you can:</p><ul><li>Provide more specific and actionable feedback during performance testing</li><li>Better interpret performance metrics and identify potential bottlenecks</li><li>Contribute meaningful suggestions for performance improvements</li><li>Collaborate more effectively with technical teams during optimization discussions</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*qlrjWP993pCqU5vMixddPA.jpeg" /></figure><p>Remember, the goal isn’t to become an expert in development or DevOps, but to build enough technical knowledge to be a more effective bridge between quality assurance and technical teams. This collaborative approach leads to better performance outcomes for the application.</p><p>Happy Testing!</p><p>Author: <a href="https://in.linkedin.com/in/m2kishore">M M Kishore</a></p><p>Stay connected and stay informed with ProductPanda! If you’re a recent graduate who’s hungry for tech-knowledge, make sure to follow us 🎉 on our journey 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c1f6d774160" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is Your Software Testing Approach Flawed? Here’s the Right Way to Do It!]]></title>
            <link>https://medium.com/@productpizzazz/is-your-software-testing-approach-flawed-heres-the-right-way-to-do-it-79c002f63dc8?source=rss-8b53772ebc51------2</link>
            <guid isPermaLink="false">https://medium.com/p/79c002f63dc8</guid>
            <category><![CDATA[software]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Product Panda]]></dc:creator>
            <pubDate>Sat, 17 Aug 2024 07:22:49 GMT</pubDate>
            <atom:updated>2024-08-17T07:25:24.471Z</atom:updated>
            <content:encoded><![CDATA[<h4>Get to know the industrial standards of software testing — helping you avoid the mistakes that you might be making during software testing.</h4><p>I am on a unique journey in the realm of software testing, a path less traveled and certainly less defined. Unlike the well-established standards in software development, software testing lacks clear industrial benchmarks, largely due to the high demand for developers. When I joined my company as an intern, I was the lone QA engineer on the team, navigating an unstructured and evolving process. I didn’t know how to test or even what to test. I was the only QA engineer on the team, and whatever I did was called Testing 🙃</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*Uml4_X85hbJgagFMVaQdIw.jpeg" /></figure><p>I kicked off by manually testing new additions and squashing bugs in the application. Jotted everything down in Google Sheets and later moved it to Confluence. With over 10 developers handling 14 internal products, my bandwidth was very limited due to all the manual testing. Once our critical internal apps got more stable, we decided to whip up an automated test suite for one of our key applications, the Retail Micro Service (RMS). Teaming up with 2 other developers and some testers, we managed to build a solid test suite that had more test cases than the unit tests in the app (which shouldn’t be according to industrial standards).</p><p>If you would like to know more about our badass test suite👉<a href="https://medium.com/@productpizzazz/manual-testing-to-automation-mastery-in-qa-85759015a4f7">Click here</a>👈.</p><p>Any experienced tester would laugh at the process we were following. Testing was conducted at the far-right end (after development was completed) of the software development process, which led to the recognition of significant issues during the testing phase. These issues included:</p><ul><li>Adding unnecessary complexity to the application, making further development more challenging.</li><li>Reducing the ability to make changes as the deadline approached.</li><li>There was a lack of input from testers, which could have refined the proposed solution and helped determine a realistic due date.</li></ul><h3>How did we solve these issues?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*XaDqR8MfUS3_1papb4p-yA.png" /></figure><h4>Shifting left</h4><p>As the first step, I was relieved from all manual testing and a large chunk of automation testing i.e., adding only cases that resonate with the actual user interactions with the application. I started to take part in the solutioning phase of any feature or architectural changes where I will be critically questioning the proposed solution making sure the solution is less error-prone. I will also know what the new version of the application will do so that I can add test cases parallelly while the developer is coding the solution. I can further make the test suite updated so that a lot of testing bandwidth is used along with the development phase leading to faster testing and release.</p><h3>What wrong did we do?</h3><p>Initially, the reliability of the test suite put more pressure on the testers to catch bugs rather than the unit tests and integration tests of the applications.</p><p>What did the old approach cost us?</p><ul><li>Long wait time for the test suite to run because the end-to-end tests are very slow to run.</li><li>Rewriting/Overlapping of test cases between developers and testers which wasted time.</li><li>QA availability for performance testing was limited.</li></ul><p>Let me try to simplify different testings which are the industry standards that we are adopting:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NgeTz1TNWPm9tgXz.jpg" /></figure><p>We are implementing the test pyramid by Mike Cohn. He introduced the Testing Pyramid in his 2009 book <em>Succeeding with Agile: Software Development Using Scrum</em>. There are 3 main types of tests stacked based on the number of test cases that have to be written.</p><h3>Unit Test:</h3><p>These tests are written by developers themselves, testing the new code at the time of writing. Unit tests ensure that the changes made in the application don’t affect the existing functionality. These tests often test single functions and also require very little time to run making them the most reliable form of test which ensures everything works fine every time new code is pushed or refactored.</p><h3>Integration Test:</h3><p>Even these tests are written by developers. These tests included mocking external dependencies such as databases, other micro-services, and third-party service applications. We will be mocking the responses from these applications and services to observe and check how each response is processed by the application.</p><h3>End-to-End Test (E2E):</h3><p>Testers come into play in this aspect of testing. We write tests that can be deployed in a test environment, using an actual database and separate mock services with sample responses that mimic real-world calls. Since these tests take time to execute, we need to ensure that we use fewer tests while still covering 90% of the actual real-world calls. These tests are generally very slow as they are a series of calls made to the application from making an order to creating a return order.</p><p>These tests generally catch errors like:</p><ul><li>Security configuration bugs in the application</li><li>Duplicate entries in the database as it is mocked in the other 2 phases of testing</li><li>Inconsistent or wrong values are stored in the database or transmitted to other micro-service or third-party applications.</li><li>Backward compatibility issues as well can be spotted.</li><li>A combination of different APIs may result in data changes which can be caught in E2E tests.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*D3NGGz04HVPGmrg7" /><figcaption>Photo by <a href="https://unsplash.com/@campaign_creators?utm_source=medium&amp;utm_medium=referral">Campaign Creators</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>It is more important to ensure that the normal flow of the application works as intended. Prioritizing the main functionalities and user interactions helps in delivering a reliable product. On the other hand, focusing on finding bugs with a very low probability or low priority (causing minimal damage) does not add much value. It is crucial to allocate resources efficiently, emphasizing the stability and usability of the application rather than spending excessive time on edge cases that are unlikely to affect the overall user experience.</p><p>Though manual testing is important, automation is essential for testing applications. The confidence our automated test cases provide is unparalleled compared to manual testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*k4Ar2Wg8igGC7ScTIsgVaQ.jpeg" /></figure><h3>Final Thoughts</h3><p>There could be bottlenecks in tester bandwidth when most efforts go into manual testing or duplicating tests already done by the developer. We realized this in our company after 7 years! It might be happening in your company as well. Proper E2E automation with only the needed test cases can save significant time. Testers can then focus on performance testing, sharing their perspective in solution design, and contributing to CI/CD development, which provides higher ROI (Return on Investment). Additionally, having time to sharpen knowledge and build more robust testing.</p><p>Happy Testing!</p><p>Author: <a href="https://in.linkedin.com/in/m2kishore">M M Kishore</a></p><p>Stay connected and stay informed with ProductPanda! If you’re a recent graduate who’s hungry for tech-knowledge, make sure to follow us 🎉 on our journey 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=79c002f63dc8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Manual Testing to Automation Mastery in QA]]></title>
            <link>https://medium.com/@productpizzazz/manual-testing-to-automation-mastery-in-qa-85759015a4f7?source=rss-8b53772ebc51------2</link>
            <guid isPermaLink="false">https://medium.com/p/85759015a4f7</guid>
            <category><![CDATA[testing-tools]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[Product Panda]]></dc:creator>
            <pubDate>Wed, 03 Jul 2024 16:37:10 GMT</pubDate>
            <atom:updated>2024-07-03T16:37:10.508Z</atom:updated>
            <content:encoded><![CDATA[<h4>How we managed to create an automation test suite that significantly enhanced our QA process and boosted efficiency tenfold, overcoming initial challenges and delivering robust, reliable testing solutions.</h4><p>I joined QA because I Googled it during college placement season and found a link claiming it was the happiest job.</p><p>Turns out, it was a sponsored ad.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/507/1*uLd6oZ16p51uCiRn1odM6w.png" /></figure><p>I applied for a QA job, not meant for computer science students, mainly to dodge the competition. Plus, the pay was double what SDE roles at mass recruitment companies in India offered.</p><p>Turns out, money does talk — and it told me to test software!</p><p>The job turned out to be pretty interesting, especially with the random bugs like API responses mysteriously setting to null, chipping away at the developer’s confidence, one bug at a time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HfB29wbK-EtWtzTL" /><figcaption>Photo by <a href="https://unsplash.com/@pauleinerhand?utm_source=medium&amp;utm_medium=referral">Paul Einerhand</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Life improved as I discovered new tools and created my own framework to fast-track manual testing.</p><p>I got better at finding all sorts of bugs, not just the null errors. My documentation speed more than doubled, and testing tasks that used to take all day were now done in less than an hour.</p><p>This sounds like a great improvement but, what if I told you I was able to 100x both my documenting and testing using automation!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wirLNaVGmduu9m53" /><figcaption>Photo by <a href="https://unsplash.com/@gillyberlin?utm_source=medium&amp;utm_medium=referral">Gilly</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>One fine day I was asked to build software that is twice the size of the actual software to test the actual software!</p><p>The internet was void of code to test APIs. My testing doesn’t stop at checking responses.</p><p>It did not stop at checking the database.</p><p>Since the product I was working with is an integration-type product (it gets values from the user and sends the same values in different formats to other applications)</p><p><em>For example</em>: the client provides the order details to our shipping label (label that you see on your Amazon packages) generating software. The values are restructured to other formats so that logistic aggregators (companies that associate with multiple courier and shipping companies to provide e-commerce logistics solutions) can process the order and assign courier partners to deliver the package.</p><p>How do I test that?</p><p>I even found that the software needs to be designed in some way so that it should be testable or should be easier to automate.</p><h3>Version 1 (Noob-ocalypse: The Ultimate Beginner’s Battle):</h3><p>With little knowledge and taking reference from an already stable test suite, an MVP of the test suite was created. There wasn’t even a proper plan for automation test cases.</p><h4>Tools and Frameworks used:</h4><ul><li>Junit4 (framework for writing testcases)</li><li>RestAssure (framework for API call)</li></ul><h4>Features it had</h4><ul><li>The application made POST calls to API and the response was validated</li><li>Assert statements(checks in if the expected value and the actual value are the same) were added. Works well for tax calculation calls</li></ul><h4>What was it lacking?</h4><ul><li>DB checks — We did not know whether the values stored in the database were the same as what was sent in the payload</li><li>There are calls made to third-party applications. We need to check if whatever the values sent are the same as what is sent by the client</li></ul><h3>Version 2 (Noob-ocalypse Reloaded: Database Disaster)</h3><p>There was already a Testsuite which was built and maintained by seniors of my company. The application was using a dump file which was getting restored every time before each test case.</p><p>What a waste of time 🕰️ (But…I regretted this decision to the core).</p><p>I was too confident enough that I could create a better architecture that would delete only the required added values in the DB to save time in loading the dump.</p><h4>Tools and Frameworks used:</h4><ul><li>java.sql package which provided APIs to execute database queries and retrieve query results for asserting</li></ul><h4>Useless feature it had:</h4><ul><li>Manually created a dump for constant values like default GST percentages, country, zip codes, etc, and ran it before running the automation test suite.</li><li>There were functions that only checked the corresponding tables whether there was data present but not the value of the data. For example: assertNotNull(result.next()) 🤦🏻‍♂️</li></ul><h4>What was it lacking?</h4><ul><li>The suite was able to test the software but when one test failed, pretty much every case following it failed because when the case failed the delete queries did not run leading to failure of other cases 😩.</li><li>The request and response data should be the same as what is in the database. But that was missing in this version of the test suite.</li><li>There were 3rd party application calls made. Those calls need to be mocked and find ways to cross-check the values being sent to those applications.</li></ul><h3>Version 3 (Zen-ocalypse PDF checks and Log checks)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NKmWdIbDEVZsi9CKluap4A.png" /></figure><p>The robustness began to take shape after this version. With the given coordinates along with a library called PDFBox, we were able to verify whatever that was provided in the database was printed properly in the invoice PDF. The <a href="https://mockoon.com/">Mockoon</a> app was used to mock API calls made to logistic aggregators. The request and response logged to ELK (Elastisearch- a place where information about all API and their response are stored for debugging purposes) was retrieved.</p><h4>Tools and framework used</h4><ul><li><strong>PDFBox</strong> is used to values from a particular coordinate. This helped in cross-checking the values printed in the invoice with the values sent to generate the invoice.</li><li><strong>Rectangle2D</strong> to create a red box to represent the area the PDF box is converting the portion of PDF to text.</li></ul><h4>Features:</h4><ul><li>Check the values in an invoice PDF file</li><li>Checks on the same values sent to 3rd party were a game-changing feature of the test suite</li></ul><h4>Improvements needed</h4><ul><li>The Test Suite seemed to be functional but quite far from complete with the absence of database validations.</li><li>Remember, when one test failed, it often resulted in subsequent tests also failing due to the unexecuted delete queries. It could have been easily addressed with @AfterMethod(testng) or @Before(junit4) annotations.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/581/1*Xx9kaN7OgJhoCy_dZH9ZKA.png" /><figcaption>A very very high-level diagram of the application/microservice</figcaption></figure><h3>Version 4 (Dump and Better Dump-ocalypse)</h3><p>In this version, we created separate dump (just a copy of the whole database in a file) files for each major scenario and restored the dump every time a test case was run.</p><p>Each case will be executed on the same database with the same values as the previous case, resolving the major issue of dependent test cases failing caused by unexecuted delete queries.</p><p>But there was an elephant sized performance issue in the test suite. Each case took ~1 min to run, by this time the suite had ~400 cases which resulted in ~6.5hrs 🤯 of running time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lmow3GQp5PFWqKuj0WMSzg.png" /></figure><h4>A Piece of Code to the Rescue</h4><p>There was some odd piece of code in the test suite built by our seniors called the “<strong><em>db_connect</em></strong>” which was a micro-service running in the machine that was running the application.</p><p>This micro-service received some instructions from the test suite running and based on the instructions it restored dump files hosted in a GCP Bucket (A Google-owned place for storing files) in the database after each test-case.</p><p>The dump restoration was very fast as the network GCP instances were in the same network which reduced the restoration from 1 min to just 4 freaking seconds!</p><h3>Version 5 (Reporting and Automating the Automation-ocalypse)</h3><p>Here was the birth of true automation took shape with some help from a paid testing tool for keeping record of automation cases, generating test reports before each release of software.</p><p>We did choose a software that was quite pricy costing 35 dollars per month per person. We are sharing 5 accounts among 10 QA engineers since sharing is caring right 😉.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cZKkBDc1ZkurUlGw" /><figcaption>Photo by <a href="https://unsplash.com/@campaign_creators?utm_source=medium&amp;utm_medium=referral">Campaign Creators</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>We have also managed to include the testing process in Jenkins, so that we have automated not only the testing but also the deployment of the application in the test environment.</p><p>This saves more time for a quick TT match with colleagues while my electronic companion does my job.</p><p>Well, this is my automation journey. But we are not done yet, we still need to figure out how to get the code coverage of the test suite. New requirements pop up and I am shifting left (taking part in the solution phase, which is the phase before the actual coding takes place) and looking forward to learning more and sharing my experiences with you all.</p><p>Happy Testing!</p><p>Author: <a href="https://in.linkedin.com/in/m2kishore">M M Kishore</a></p><p>Stay connected and stay informed with ProductPanda! If you’re a recent graduate who’s hungry for tech-knowledge, make sure to follow us 🎉 on our journey 🚀 .</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85759015a4f7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Everything About Bugs a QA should know]]></title>
            <link>https://medium.com/@productpizzazz/everything-about-bugs-a-qa-should-know-64bf639b4643?source=rss-8b53772ebc51------2</link>
            <guid isPermaLink="false">https://medium.com/p/64bf639b4643</guid>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Product Panda]]></dc:creator>
            <pubDate>Mon, 18 Mar 2024 16:14:32 GMT</pubDate>
            <atom:updated>2024-03-18T16:15:11.686Z</atom:updated>
            <content:encoded><![CDATA[<h4>From the Perspective of a Tester: What Is a Bug? And How is it Navigated in their Life?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pUSFHvPYk1yPvg7a" /><figcaption>Photo by <a href="https://unsplash.com/@brucebmax?utm_source=medium&amp;utm_medium=referral">Bruce Warrington</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>What is a bug🐞?</h3><p>If you are someone who is already a part of the Tech workforce, you will have some knowledge for sure. For those who are new:</p><blockquote>A bug is an error or flaw in an application that causes it to behave in unintended ways or produce incorrect results.</blockquote><p>Not every bug is a bug!</p><p>Being a QA, before reporting a bug it is highly recommended to look for bug attributes or bug characteristics before proceeding to show off your new findings to the developers or whoever it may concern.</p><p>If a bug is reported from the end-users, it may not be the first time it is occurring. Therefore, it should be analyzed for some attributes associated with the bug so that it can be rectified accordingly.</p><p>We will discuss well-described examples in the later section of the blog.</p><h3>What are Some Attributes of Bugs?</h3><p>Or how do we describe a bug? Does it have wings?</p><p>A software bug has a variety of characteristics that will be useful for different people in the organization. Being a QA, it is very important to identify the attributes of the bugs and report them, which will provide the most information to anyone who reads it, thus ensuring that it will be resolved as soon as possible. Let’s dive deep into very common attributes:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ILgYpKJK_FQNTY1E" /><figcaption>Photo by <a href="https://unsplash.com/@alex_andrews?utm_source=medium&amp;utm_medium=referral">Alexander Andrews</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Severity</strong></p><p>The severity of the bug is determined by the impact that its occurrence has on the system. The severity of a bug can be largely categorized as:</p><p><strong>Critical</strong></p><p>These kinds of bugs have a severe impact on the system. Impacts like system crash (application not working), data corruption(change/leakage of information), or critical failures. These bugs are given the highest priority while giving attention and resolution.</p><p>A simple example:</p><p>Upon entering valid credentials, instead of gaining access to their account, they are logged into someone else’s account without their consent.</p><p>This bug is a real deal. It needs to be solved as soon as possible to prevent unwanted breaches and to protect users’ confidentiality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/527/1*0RswQxAVvzCNbVQtCYIRyw.jpeg" /></figure><p><strong>High</strong></p><p>These bugs have a high negative impact on the system as critical bugs. But the main difference between a critical issue and a high-priority issue is that high-severity bugs have a high impact, and the possibility of them occurring is very low, therefore they might not need high attention as critical bugs.</p><p>A simple example:</p><p>When a customer adds items to their cart and proceeds to checkout, the system fails to apply discounts.</p><p>Here there is a potential to lose customers due to the frustration of not being able to redeem their discount which contributes to the high priority of the bug.</p><p><strong>Medium</strong></p><blockquote>Bugs that cause noticeable but non-critical issues, such as minor functionality failures or usability problems do not significantly hinder the user&#39;s ability to use the software.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZbvH6SKfAfw6R1UmLKnFcw.jpeg" /></figure><p>A simple example:</p><p>In a messaging application, users are unable to send messages containing special characters such as “&amp;” or “$”. However, the application does not provide any error message or indication to the user that their message failed to send due to these characters.</p><p>Here the bug affects the usability of the application as it restricts users from sending messages containing certain characters without providing proper feedback. While it doesn’t completely prevent users from using the application, it significantly hampers their ability to effectively communicate, potentially leading to frustration and confusion.</p><p><strong>Low</strong></p><p>These bugs can easily be overlooked even by the clients as well. They could be a slight alignment issue in certain pages of the software, spelling mistakes, or low-impact usability issues like adding keyboard shortcuts for frequently used features, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1aEzafa62Q7B3zUM" /><figcaption>Photo by <a href="https://unsplash.com/@ian_barsby?utm_source=medium&amp;utm_medium=referral">Ian Barsby</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Other low-priority issues also encompass non-essential features or those that are rarely utilized within an application. Documentation inconsistencies and non-critical edge cases, although rare, can often be resolved with straightforward workarounds, placing them in the category of low-priority bugs.</p><p><strong>Reproducibility</strong></p><blockquote>It is the ability to consistently replicate an issue’s occurrence in a specific condition.</blockquote><p>It is easier for developers to fix it when the bug is reproducible. There could be several conditions depending on the size of the application and the influence of the multiple conditions can contribute to the bug.</p><p>It is important to provide detailed information to the developer on what exactly is happening from the perspective of QA.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/1*-5g0PiX5ytxsITKWvlKkVw.jpeg" /></figure><p>The information could be:</p><ul><li>Version of the Software</li><li>Specific logs when the error occurred.</li><li>API logs in log management tools like (ElastiSearch, Graylog, etc)</li><li>Log files in the machine where the application is running.</li><li>Specific configuration in which the error is occurring.</li><li>Platform in which the software is running. It could be a web-based application, mobile app, desktop app, or any platform.</li></ul><p>With the information provided, the product managers can decide whether it’s truly a bug or a hidden gem, uncovering any quirks in the requirements. The developer can easily use the information in the bug report to swiftly spot it, squash it, and get back to their coffee break!</p><p><strong>Description</strong></p><p>A clear and detailed description of the bug is essential for developers to understand its behavior and potential causes.</p><p>This includes information such as the steps to reproduce the bug(reproducibility), expected versus actual outcomes, inputs, and any relevant error messages or logs.</p><p>Think of bug descriptions as the gossip column of the software world. These descriptions of the bug collectively contribute to the bug report, which in turn helps everyone associated with the piece of software become aware of the bug and aids in finding solutions to it.</p><p><strong>Frequency</strong></p><p>The frequency of a bug is the number of times the bug occurs or the number of people it impacts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mLIMKjeI2CDAosQo" /><figcaption>Photo by <a href="https://unsplash.com/@luis_arias?utm_source=medium&amp;utm_medium=referral">luis arias</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>A bug’s frequency can influence its priority. High-frequency bugs that occur frequently or affect a large number of users are typically prioritized over those that are sporadic or affect only a small subset of users. To understand this better:</p><p>Let’s consider a bug in a web application where clicking on a specific button sometimes results in the application crashing. Based on the frequency:</p><ul><li><strong>If the application crashes every time the button is clicked, it should be placed in high priority</strong>, given that the button is part of an important feature in the software.</li><li>If the application crashes only when multiple users click the button at the same time, this would be a less frequent occurrence but still a significant issue. Considering the application has a few hundred users, this could be marked as a medium-priority bug.</li><li>If the app only crashes when lots of people click the button at the same time, it’s still a problem, but not as urgent. Imagine if you’re at a party and everyone tries to go through the same door at once — it’s a mess, but not a disaster. In this case, the issue might be given medium priority because it affects quite a few users.</li><li>If the application crashes only when the button is clicked by a user using a particular browser (the place where web-based application works) version or if the button is an infrequently used part of the application. It’s like if you have a toy that only breaks if you play with it in a certain way or if you barely play with it at all — it’s not a problem most of the time. It could be marked as a low-priority bug.</li></ul><p>There are other attributes like Environment (the place where the application is run), Attachments (screenshots or screen records) related to the bug, Assigned To (person/team the bug is reported to), Status (current state of the bug “assigned”, “in progress”, “fixed”, etc) and Comments/Notes (other observations, possible workarounds, root cause). When this information is collected from the QA, a bug report is filed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JK3ZYCHjyoxOQJzP" /><figcaption>Photo by <a href="https://unsplash.com/@lukechesser?utm_source=medium&amp;utm_medium=referral">Luke Chesser</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Bug Report</h3><p>Now we know what a bug is and we delved deep into it to find more information about it to provide a helping hand to our colleagues. We QAs collect these attributes of the bug and construct a document called “The Bug Report”. Bug reports are created only when we are sure that what we have found is a bug.</p><p>Note: Only submit a bug report if you are certain about the issue. If unsure, always seek approval from the responsible party beforehand.</p><blockquote>The point of writing a problem report (bug report) is to get bugs fixed” — Cem Kaner.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vuPdlrOKOtkI236K" /><figcaption>Photo by <a href="https://unsplash.com/@cookiethepom?utm_source=medium&amp;utm_medium=referral">Cookie the Pom</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Let’s have a look at a sample bug report!</p><p><strong>Bug Description:</strong></p><p><em>Issue:</em> <strong>Duplicate Notifications</strong></p><p><strong><em>Scenario:</em></strong> The college student relies on a scheduling app to receive timely notifications for upcoming classes and assignment deadlines. However, they notice that they are receiving duplicate notifications for the same event, which can be confusing and overwhelming.</p><p><strong><em>Steps to Reproduce:</em></strong></p><ol><li>Add a new class or assignment to the schedule.</li><li>Set a reminder/notification for the added event.</li><li>Wait for the scheduled time to receive the notification.</li></ol><p><strong><em>Expected Result:</em></strong> The user should receive a single notification for the scheduled event.</p><p><strong><em>Actual Result:</em></strong> The user receives multiple notifications for the same event, causing confusion and potential annoyance.</p><p><strong><em>Additional Information:</em></strong> This bug could be a result of a programming error in the notification system, where the app is triggering multiple notifications for a single scheduled event. It might be related to how the app handles and manages scheduled events and reminders.</p><p><strong><em>Possible Impact on User:</em></strong> The user might miss important notifications due to the flood of duplicate alerts, leading to potential issues like missing classes or deadlines.</p><p><strong><em>Possible Solution:</em></strong> The software developers should investigate and fix the issue in the notification system, ensuring that each scheduled event triggers only one notification at the specified time.</p><p><em>End of sample report</em></p><p>To ensure a successful bug-reporting pipeline, it is important to have a clear and concise process in place.</p><p>This includes comprehending the bug, authenticating its existence, reporting it, and ensuring that it is received by the appropriate team or individual.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZBqzJ0-krcunHdrt" /><figcaption>Photo by <a href="https://unsplash.com/@mybbor?utm_source=medium&amp;utm_medium=referral">Robby McCullough</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>However, the ultimate determination of whether a bug truly matters depends on various factors such as industry standards (bug reporting in hardware is different from software), customer expectations (a bug for s), and the level of risk tolerance.</p><blockquote><strong>QA Advice 01</strong>: To maximize what you observe you can test in pairs, perform tests more than once, video your testing so that you can play it back, don’t test when you are sleepy, or at the very least: be aware of how easily you can miss important bugs that you see only once.</blockquote><p>Embrace the learnings and grow professionally.</p><p>Happy Testing :)</p><p>Author: <a href="https://in.linkedin.com/in/m2kishore">M M Kishore</a></p><p>Stay connected and stay informed with ProductPanda! If you’re a recent graduate who’s hungry for tech-knowledge, make sure to <strong>follow us 🎉 </strong>on our journey 🚀 .</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=64bf639b4643" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Harnessing Your Development Team for Quality Assurance: A Strategic Guide to Effective Inquiry]]></title>
            <link>https://medium.com/@productpizzazz/harnessing-your-development-team-for-quality-assurance-a-strategic-guide-to-effective-inquiry-a1070aa4121b?source=rss-8b53772ebc51------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1070aa4121b</guid>
            <category><![CDATA[testing-tools]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Product Panda]]></dc:creator>
            <pubDate>Mon, 29 Jan 2024 16:49:21 GMT</pubDate>
            <atom:updated>2024-03-18T16:15:45.826Z</atom:updated>
            <content:encoded><![CDATA[<p>Questions you need answers to before starting to test. Understand the product for smarter questions and better testing speed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*V0SzIGneocovewX0" /><figcaption>Photo by <a href="https://unsplash.com/@rohitfarmer?utm_source=medium&amp;utm_medium=referral">Rohit Farmer</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>After successfully completing 100 tickets in Jira (although I’m unsure if this is the right metric to evaluate my testing journey), I’ve identified a major problem that is often overlooked by QA professionals, or perhaps many of them are simply accepting the issue.</p><h3>Ambiguity: the mother of creativity, confusion, and diverse perspectives.</h3><p>The first time I heard about this word was when I was in my Bachelor’s.</p><p>My computer teacher who had experience working in IT was stressing about ambiguity. He mentioned ambiguity 10000 times staring at every one of our eyes instilling an important lesson for life.</p><p>“Avoid ambiguity at all costs when you become a part of the workforce and also in your daily life” still rings as a reminder to make sure whatever I do is clear and explicit. But we cannot expect the same from our fellow developers as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*B4K-prOubr7ZfnDO" /><figcaption>Photo by <a href="https://unsplash.com/@seffen99?utm_source=medium&amp;utm_medium=referral">Sven Brandsma</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Therefore I have devised a framework that guarantees a better understanding of the features added or the bug rectified when the developer gives you KT (Knowledge Transfer).</p><p>This framework goes hand in hand with deep knowledge of the product you are working on stonks the quality of the product you are testing.</p><h3>Question 1: What happened earlier and why are we doing this in the first place?</h3><p>The answer to this may not even lie with the developer himself! A feature normally goes like this:</p><ul><li>Requirements arise from the customers</li><li>The seniors in the team decide whether or not to adopt the feature in the application or not</li><li>The requirement is conveyed to the developers verbally or in the form of documentation.</li><li>The developers develop the requirement and give it for testing</li><li>We as testers who aren’t aware of anything that happened earlier should be testing.</li></ul><p>That’s why we need to ask the right questions.</p><p>I strongly feel that it is the responsibility of QA engineers to ask the developers or product managers why a feature or a particular approach was adopted for fixing a bug. We can even go the extra mile further by questioning approaches when we are familiar with the product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*A3n6tRhhUU33Oy6t" /><figcaption>Photo by <a href="https://unsplash.com/@77hn?utm_source=medium&amp;utm_medium=referral">The 77 Human Needs System</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Finding the real reason behind the code change and knowing the business aspects throws light on the client’s requirements as well which is what we are supposed to make sure it is met.</p><p>I happened to test a printing application that was optimized to print at half the time it used to take. The solution was a very interesting one! The solution included C++ and Java combined. Yes, I did not know different languages could work hand in hand to arrive at a solution that was mind-blowingly fast!</p><p>Knowing some history of the product and why some changes are being made will give you a sense of credibility while testing it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FrAmThU9QR-L_VbD" /><figcaption>Photo by <a href="https://unsplash.com/@museumsvictoria?utm_source=medium&amp;utm_medium=referral">Museums Victoria</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Also, it is nice to know and appreciate a clever solution to a problem.</p><p>Who knows you might find a flaw in the solution🤷.</p><h3>Question 2: How to test? Or how did you verify that it is working as expected?</h3><p>When we get the answer to the first question, we become clear on what to test but not necessarily how to test.</p><p>Aren’t we aware of how we used to test?</p><p>Why do I have to ask that to the developer?</p><p>If you do not know how it was tested by the developer, we might spend a significant amount of time figuring out how to test rather than testing it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*t6_wriniVzs7ZUIW" /><figcaption>Photo by <a href="https://unsplash.com/@jannerboy62?utm_source=medium&amp;utm_medium=referral">Nick Fewings</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This doesn’t mean blindly following what the developer did to test, It is highly recommended to put on your thinking caps and figure out ways this could go wrong.</p><h3>Question 3: What are the edge cases?</h3><p>Developers are trained to consider edge cases during their interviews they are asked about questions and find edge cases for those questions as well.</p><p>They pose a valuable input for your testing.</p><p>Even though what we are testing is straightforward, the moment we ask the question you and your developer friend think of ways the product could be broken. 2 minds are thinking of ways to refine the product we are building.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bx1IXrzC3Tvod-tF" /><figcaption>Photo by <a href="https://unsplash.com/@accuray?utm_source=medium&amp;utm_medium=referral">Accuray</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Recently I was testing an API that will calculate tax for shipping charges. Though it might sound very straightforward forward it had very peculiar test cases where:</p><ul><li>There could be items whose selling price could be 0 but they would have shipping charges</li><li>How do you charge for gifts?</li><li>Sometimes there are 0 taxes calculated on items. I didn’t know there was no tax on some items in India.</li><li>Will it go with 0 downtime (not stopping the production server/ application)</li><li>Will the application work as expected even when a migration script (a program that changes the database compatible with the current version of the software) is running?</li></ul><p>Keeping in mind these scenarios, we strive to make this software foolproof and reliable, ensuring a robust solution for diverse situations. There might be different scenarios in different work environments but working collaboratively with fellow developers to find situations that might arise and making sure nothing goes wrong gives our users an efficient software experience.</p><h3>Right Questions Lead to Better Products</h3><p>Questioning opens up different perspectives on existing solutions, finds loopholes, and also brings QAs and developers closer to providing a robust solution that makes customers’ lives easier and error-free.</p><p>Not all the questions are relevant in all the scenarios it depends on the size of the company and the nature of the testing task we are provided with.</p><p>To ask better questions learning more about the product’s functionality by reading the documentation properly or setting up meetings with product experts and clarifying the flows and doubts arising during the discussion can help in extending the questions in the framework discussed to test better.</p><p>Happy Testing :)</p><p>Author: <a href="https://in.linkedin.com/in/m2kishore">M M Kishore</a></p><p>Stay connected and stay informed with ProductPanda! If you’re a recent graduate who’s hungry for tech-knowledge, make sure to <strong>follow us 🎉 </strong>on our journey 🚀 .</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1070aa4121b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Master these tools to overtake your QA peers!]]></title>
            <link>https://medium.com/@productpizzazz/master-these-tools-to-overtake-your-qa-peers-e8c46f43b208?source=rss-8b53772ebc51------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8c46f43b208</guid>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[testing-tools]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Product Panda]]></dc:creator>
            <pubDate>Sat, 30 Sep 2023 07:14:47 GMT</pubDate>
            <atom:updated>2024-01-29T16:23:15.249Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Master these tools to overtake your QA peers</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TK-k4xGL4s8K3DCa" /><figcaption>Photo by <a href="https://unsplash.com/@jjjordan?utm_source=medium&amp;utm_medium=referral">JJ Jordan</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Often QA needs to check whether all the criteria should be satisfied while testing a feature. It starts from:</p><ul><li>Checking the UI functionality</li><li>Checking the data being stored in the db properly in the right table</li><li>Checking if the same data is retrieved properly</li><li>Checking the request payload and the expected response for the API<br>and much more….</li></ul><p>Manually testing them is quite a tedious job when there is not much automation created. Also, some portions of testing cannot be automated easily because of the lack of knowledge and training.</p><p>By experimenting with various tools to aid my testing process.</p><p>I have come up with 3 tools that I have been using every day to fast-pace my testing without compromising on the quality of testing. I have reserved the most underrated tool at the last.</p><p>You will quickly discover that the first tool a QA needs is:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LUJlcLkuFPKY59Xm" /><figcaption>Photo by <a href="https://unsplash.com/@rubaitulazad?utm_source=medium&amp;utm_medium=referral">Rubaitul Azad</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Postman</h3><p>Postman has evolved significantly with numerous features beyond its original purpose of executing API requests. In addition to the traditional usage, there are several other features available.</p><h4>Creating Collections</h4><p>Creating separate collections for different scenarios/tickets is a great way to quickly hit those APIs without needing to create them from scratch for different scenarios.</p><p>Naming them accordingly and modularising the API calls will act as a great record of your work which you can admire later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/806/1*vVZNZpQk7SwQ4-j11K4aEw.png" /></figure><h4>Creating Workspace with your testing peers</h4><p>This is a great way to share knowledge with your peers, and these collections can also be reused by your peers for similar testing by making a copy of them.</p><p>Since my QA team is small with 3 persons we enjoy the workspace features for free. This would cost some money when the QA team is larger than 3 members.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_p67tyRVtLjdBvCi" /><figcaption>Photo by <a href="https://unsplash.com/@mmcgregor?utm_source=medium&amp;utm_medium=referral">Mark McGregor</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Creating Mock Servers</h4><p>Mocking is the process of creating a fake/mock response based on the type of request, string present in the request, URL path of the request<br>Often we mock the API call from some proprietary servers so that we are not using them which in turn costs us money or unwanted data into the production servers.</p><p>Therefore for testing purposes, QAs have a mock server which I did not know until I wrote this piece of text.</p><p>You can learn more about creating a mock server by clicking this <a href="https://learning.postman.com/docs/designing-and-developing-your-api/mocking-data/mock-with-api/">link</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oPYOuWEJMnSdCYjW" /><figcaption>Photo by <a href="https://unsplash.com/@mrakityanskiy?utm_source=medium&amp;utm_medium=referral">Misha Rakityanskiy</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Setting up custom proxy server</h4><p>Let me explain to you in simple terms.</p><p>I have 2 APIs, one API has a server configured, and the other one there is not an actual server and it has to be mocked. On configuring the proxy, the requests with <strong>no</strong> mock response for the particular call, the call is made to the actual server configured in it while if the mock is configured the mock is received in the response.</p><p>more <a href="https://learning.postman.com/docs/getting-started/installation/proxy/#using-a-custom-proxy-for-requests">here</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/1*5dG-Y2fzk_MAXy_G92auAw.jpeg" /></figure><h3>Mockoon</h3><p>Mockoon is a mocking server app.</p><p>I used this very recently which had a very good user experience. running it in was a breeze. The mock server could be configured using docker on a hosted VM(Virtual Machine) with just copying a JSON file to the VM. It had features like configurable responses for the same request, setting up custom timing for responses, and much more.</p><p>Skipping this as Postman has this inbuilt mock server that could be replaced.</p><h3>Dbeaver</h3><p>This open-source gem makes you feel like a Superman.</p><p>You can just query, edit, or visualize your data with a series of clicks. It has support for many famous databases to easily look for data. The UI could look a bit old school but not the features that reside in the software.</p><p>Let me share some features I use daily as a QA to 100x my productivity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8CSva5EE3ol8a-HA" /><figcaption>Photo by <a href="https://unsplash.com/@mana5280?utm_source=medium&amp;utm_medium=referral">mana5280</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Multiple Database Connection</h4><p>You can simultaneously connect to multiple databases with ease with a single tap.</p><p>If you are testing multiple microservices that are dependable even though they are of different databases all together tables in each of them could be viewed simultaneously. In my case I had a worker moving data from one database in a service to another and I had to check if a worker was running properly. The data was moved to another database. With Dbeaver, I simply connected to both the database and opened the tables where the data sync happens turned on automatic refresh, and manually triggered the worker through an API.</p><p>I could easily verify the changes and took screenshots for the test cases in a jiffy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hbpyMsTkrnOoMnTS" /><figcaption>Photo by <a href="https://unsplash.com/@mullyadii?utm_source=medium&amp;utm_medium=referral">Mulyadi</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>CRUD operations are easy as breeze.</h4><p>Do you want to quickly change a value for a configuration, delete a single or multiple rows, or insert a row that resembles the row above with dbeaver it is very easy. It is nothing more different than operating with Excel.</p><ul><li>Create — Click on the duplicate button to make a duplicate row and make the necessary changes easily without needing to create a query</li><li>Read — This is the easiest of all! You can use the search box on the top to filter out queries. To order them click on the inverted triangle on the column on which you want to order and select the apt option to order the data. You can also group them or use DB functions like SUM(), COUNT(), etc. available in the right panel.</li><li>Update — Double click on the cell update the value and save by using the shortcut ctrl+s or command+s or click save at the bottom of the table</li><li>Delete — To delete just select the cell that is part of the row click the delete button and save the database to persist the changes</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0vv4WZdQE3Ie5K7b" /><figcaption>Photo by <a href="https://unsplash.com/@izzyfisch_?utm_source=medium&amp;utm_medium=referral">Isabella Fischer</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>With some learning curve associated with learning DBeaver, mastering the tool has all the potential to lessen the time spent in the database scavenging through data and updating them with complex queries.</p><h4>Advance Copy</h4><p>You have your data displayed after filtering them. How would you migrate the same data to a database a CSV file or even HTML?</p><p>DBeaver has got you covered.</p><p>Just right-click and select advanced copy and select the type of copy you need from the plethora of copy commands. As a tester, I often copy the insert statement and share it with developers to debug some anomalies so that when they use their debuggers(a tool that shows the state of the program what was the variable when the program is run at a certain line of code).</p><p>You can also export the data in the form of CSV, HTML, SQL, etc. based on your requirements without much heed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EUXKLeg7kBiTQOc9" /><figcaption>Photo by <a href="https://unsplash.com/@helloimnik?utm_source=medium&amp;utm_medium=referral">Nik</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Search Columns</h4><p>Have you ever faced a situation where you remember the column name but not the table that is associated with it?</p><p>Worry no more DBbever has also got that covered as well. You can search the Database Metadata(1. a set of data that describes and gives information about other data.) which contains info about column names, constraints, table names, procedures, or functions(I have no idea what these are).</p><p>To initiate your search:</p><ul><li>Click on search in the task bar</li><li>Select DB Metadata from the dropdown</li><li>In the dialog box enter the search string or regex(regular expression) by checking on the right boxes.</li><li>And hit Enter Voila! you just found the table name!</li><li>Now go flex your skills</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4xq01K6W2ZRFw1U7" /><figcaption>Photo by <a href="https://unsplash.com/@benwhitephotography?utm_source=medium&amp;utm_medium=referral">Ben White</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Not only mastering these tools is important.</p><p>What is more important is the thirst for new technology and the ability to adapt to new technologies. Whatever tools that we discussed will evolve or even get depricated with time. Gain more knowledge impliment them to test better and faster.</p><p>And of course you are not racing agains anyone other than you and the better you.</p><p>Embrace the learnings and grow professionally.</p><p>Happy Testing :)</p><p>Author: <a href="https://in.linkedin.com/in/m2kishore">M M Kishore</a></p><p>Stay connected and stay informed with ProductPanda! If you’re a recent graduate who’s hungry for knowledge, make sure to <strong>follow us 🎉 </strong>on our journey 🚀 .</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8c46f43b208" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thriving in Startup Realities QA Mindsets for Long-Term Success and Resilience]]></title>
            <link>https://medium.com/@productpizzazz/thriving-in-startup-realities-qa-mindsets-for-long-term-success-and-resilience-a5e597a3e145?source=rss-8b53772ebc51------2</link>
            <guid isPermaLink="false">https://medium.com/p/a5e597a3e145</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[advice]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[mindset]]></category>
            <dc:creator><![CDATA[Product Panda]]></dc:creator>
            <pubDate>Thu, 17 Aug 2023 01:32:22 GMT</pubDate>
            <atom:updated>2023-08-17T01:32:22.888Z</atom:updated>
            <content:encoded><![CDATA[<p>Unveiling the 4 Realities of Being Newbie QA in a Startup: Embracing and Preparing for a Future-Proof Journey</p><figure><img alt="a group of startup engineers laughing and having fun during a brainstorming session" src="https://cdn-images-1.medium.com/max/1024/0*UJxZ-NQ-QXNCnLZk" /><figcaption>Photo by <a href="https://unsplash.com/@priscilladupreez?utm_source=medium&amp;utm_medium=referral">Priscilla Du Preez</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Working at a startup? Get ready for a rollercoaster ride of excitement!</p><p>Imagine the buzz of a college campus, but with real-world challenges and rewards. Now, let’s talk about the real deal — I went through a nail-biting mass layoff in the startup I was part of. Picture this: out of 330 employees, 60 got the boot in a single day. Talk about high-stakes drama!</p><p>But hey, don’t let that scare you off. I’ve got some golden nuggets to share — stuff you need to know to ace the startup game.</p><figure><img alt="a giraffe’s neck depicting long term investing in startup" src="https://cdn-images-1.medium.com/max/1024/0*gh12CD7jfZr4IHCX" /><figcaption>Photo by <a href="https://unsplash.com/@jeremiahdelmar?utm_source=medium&amp;utm_medium=referral">Jeremiah Del Mar</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Think Long Term</h3><p>You know what’s cooler than a quick buck🤑?</p><p>Long-term growth, my friend.</p><p>Sure, hopping from job to job might give your wallet a short-term boost. But, let’s play the long game. Ever heard of Sathya Nadella? Guy stuck with one company and rocked it. Same goes for Sundar Pichai. These legends became masters in their fields, not by hopping around, but by diving deep. So, think big picture. Stick with a startup, dive into your domain, and watch your value skyrocket.</p><p>Trust me, it’s not just about cash — it’s about becoming a problem-solving guru and owning your expertise.</p><figure><img alt="A dog catching a frisbee depicting chasing money" src="https://cdn-images-1.medium.com/max/1024/0*lhdDhw0yAEGyDLSM" /><figcaption>Photo by <a href="https://unsplash.com/@rodeutsch?utm_source=medium&amp;utm_medium=referral">Robin Jonathan Deutsch</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Chasing That Paper</h3><p>Yeah, startups mean hard work, but they also mean potential for big money.</p><p>Climbing the ladder? Easier.</p><p>Promotions? Quicker.</p><p>Plus, ever heard of stock options? They might not mean much now, but down the road, they could be the golden ticket.</p><p>Imagine being a QA whiz and owning a slice of the company. Sounds sweet, right? And guess what? Money’s not the only motivation. Some big shots keep working even after hitting the jackpot.</p><p>Why? Because life’s about more than just moolah.</p><figure><img alt="a hand blocking a punch depicting “rolling with the punches”" src="https://cdn-images-1.medium.com/max/1024/0*uaTWptYG8YL-oKtN" /><figcaption>Photo by <a href="https://unsplash.com/@enginakyurt?utm_source=medium&amp;utm_medium=referral">engin akyurt</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Rolling with the Punches</h3><p>Buckle up — here’s the reality check.</p><p>Startups are wild. They can be as unpredictable as a teenage mood swing. Layoffs? Yeah, they happen. But here’s the trick: be ready. It’s like being the hero in a video game — level up your skills, keep your network strong, and stay adaptable. If you hit a setback, bounce back even stronger. And guess what? While developers might have a safety net, us QA folks might feel the heat more.</p><p>Embrace change, and you’ll snag opportunities when others are stuck in panic mode.</p><figure><img alt="a black dog wearing groucho glasses(glasses with fake big nose attached to look funny)" src="https://cdn-images-1.medium.com/max/1024/0*vdNy_8hp2QL5IfaW" /><figcaption>Photo by <a href="https://unsplash.com/@braydona?utm_source=medium&amp;utm_medium=referral">Braydon Anderson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Adapt or Bye-Bye</h3><p>Picture this: the startup universe is like a high-speed train.</p><p>Blink…</p><p>and things change.</p><p>Code?</p><p>Evolving faster than your favorite meme!</p><p>So, be the chameleon of tech.</p><p>Adaptability is your superpower. Codebase shifts? New packages? No problem! Stay flexible, explore new tools, and you’ll save time without sacrificing quality.</p><p>To wrap it up, startups are like a crazy adventure ride.</p><p>Yeah, there are twists and turns, but the journey is worth it. Embrace the long-term hustle, chase growth, and be ready for curveballs. Flexibility? Your secret weapon😉.</p><p>Hungry for more insights? Check out our other blogs as well:</p><ul><li><a href="https://medium.com/@productpizzazz/you-will-not-be-celebrated-how-being-a-qa-is-unconventionally-awesome-c2253bb350e"><em>You Will not Be Celebrated! How Being a QA is Unconventionally Awesome 🤩</em></a></li><li><a href="https://medium.com/p/non-tech-skills-you-ignore-in-quality-assurance-enhancing-performance-beyond-technical-expertise-ae6f73246862"><em>Non-Tech Skills You Ignore in Quality Assurance- Enhancing Performance Beyond Technical Expertise</em></a><em>🍕</em></li><li><a href="https://medium.com/p/the-art-of-testing-how-i-plan-and-prioritize-tasks-for-effective-and-quality-results-tech-1559bcfb38b6"><em>The Art of Testing: How I Plan and Prioritize Tasks for Effective and Quality Results (Tech)</em></a><em>🍕</em></li></ul><p>Stay connected and stay informed with ProductPanda! If you’re a recent graduate who’s hungry for insights and knowledge, make sure to follow us on our journey. 🚀 Subscribe to our weekly newsletter to get the latest updates directly in your inbox.</p><p><a href="https://productpizzazz.substack.com/?r=2dk0fg&amp;utm_campaign=pub-share-checklist">Product Panda&#39;s Substack | Substack</a></p><p>Don’t miss out on our engaging content — sign up for Product Panda’s Substack today. 📬 And if you’re feeling extra generous, you can also buy us a virtual coffee ☕️. Your support not only fuels our knowledge hub but also contributes 0.5% of your purchase towards a greener planet.</p><p><a href="https://buy.stripe.com/7sIaGa8qa90hadOfYY">Stripe Checkout</a></p><p>Happy Testing :)</p><p>Author: <a href="https://in.linkedin.com/in/m2kishore">M M Kishore</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5e597a3e145" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>