<?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 Swaroop Nadella on Medium]]></title>
        <description><![CDATA[Stories by Swaroop Nadella on Medium]]></description>
        <link>https://medium.com/@swaroopnadella?source=rss-dd14fdf41792------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*3VSUOhLmuR-h1yJwxjSgpQ.png</url>
            <title>Stories by Swaroop Nadella on Medium</title>
            <link>https://medium.com/@swaroopnadella?source=rss-dd14fdf41792------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 10:14:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@swaroopnadella/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[Prompt Engineering for QA Engineers]]></title>
            <link>https://swaroopnadella.medium.com/prompt-engineering-for-qa-engineers-4f3f54e707db?source=rss-dd14fdf41792------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f3f54e707db</guid>
            <category><![CDATA[generative-ai-tools]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[ai-testing]]></category>
            <category><![CDATA[prompt-engineering]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Swaroop Nadella]]></dc:creator>
            <pubDate>Mon, 15 Jun 2026 16:26:40 GMT</pubDate>
            <atom:updated>2026-06-15T16:26:40.566Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zUB3lDKFHB_ovqQfLDTCHQ.png" /></figure><p>What is Prompt?</p><p>Prompt is the instruction, question, or input you give to an AI model to get a response. Think of a prompt as a way of telling the AI what you want it to do.</p><p>Different AI models (LLMs) available as Web Apps (we can access through browser)</p><p>Web Applications<br>1) ChatGPT — from Open AI<br>2) Claude — from Anthropic<br>3) Gemini — from Google<br>4) Copilot — from Microsoft</p><p>Integrated with IDEs<br>5) GitHub Copilot — from Microsoft (AI Pair programmer — VS Code/IntelliJ/Eclipse IDE)</p><p>Desktop App<br>6) M365 Copilot — use with Microsoft Office Applications<br>(Word/ Excel/ PowerPoint/ Teams/ Outlook)</p><p><strong>Prompt Engineering Techniques</strong></p><p>1. Zero-Shot Prompting</p><p>2. One-Shot Prompting</p><p>3. Few-Shot Prompting</p><p>4. Role-Based Prompting</p><p>5. Constraint-Based Prompting</p><p>6. Chain of Thought (CoT) Prompting</p><p>7. Context-Based Prompting</p><p>— — — — — — — — — — — — — — — — — — — —</p><p><strong>1. Zero-Shot Prompting</strong></p><p>Let’s start with the simplest prompting technique.</p><p>Imagine you need some test case ideas for a Login Page.</p><p>You open ChatGPT (or other LLM) and type:</p><p>Prompt:</p><p>Generate 10 test cases for a Login Page with Username, Password, and Login button.</p><p>— — — — — — — — — — — — — — — — — — — — —</p><p>You don’t provide any examples.</p><p>You don’t explain the format.</p><p>You simply ask a question and AI generates a response.</p><p>This is called Zero-Shot Prompting.</p><p>— — — — — — — — — — — — — — — — — — — — —</p><p>Few simple prompt examples</p><p>Example 1<br>Generate 10 test cases for a Login Page.</p><p>Example 2<br>List possible edge cases for a Date of Birth field.</p><p>Example 3<br>Generate positive and negative test scenarios for a Registration Page.</p><p>Example 4<br>Suggest test data for testing a Password field.</p><p><strong>2. One-Shot Prompting</strong></p><p>Now let’s make the prompt a little smarter.</p><p>Imagine your team follows a specific style for writing test cases.</p><p>Instead of expecting AI to figure out the pattern on its own, you first show it one example.</p><p>Prompt:</p><p>Example:<br>Requirement: User should be able to add a product to the shopping cart.</p><p>Test Case:<br>Verify user can add a product to the shopping cart successfully.</p><p>Generate similar test cases for:<br>Requirement: User should be able to remove a product from the shopping cart.</p><p>— — — — — — — — — — — — — — — — — — —</p><p>Before asking AI to generate a new test case, <br>we’re showing it one example of how a requirement should be converted into a test case.</p><p>This is called One-Shot Prompting.</p><p><strong>3. Few-Shot Prompting</strong></p><p>Now let’s take it one step further.</p><p>In One-Shot Prompting, we provided AI with one example.</p><p>But sometimes one example is not enough.</p><p>If you want AI to better understand a pattern, style, or expected output, you can provide multiple examples before asking it to perform the task.</p><p>Prompt:</p><p>Example 1:<br>Requirement: User should be able to upload a profile picture.</p><p>Possible Edge Case:<br>Uploading a file larger than the allowed size.</p><p>Example 2:<br>Requirement: User should be able to make an online payment.</p><p>Possible Edge Case:<br>Payment session expires before transaction completion.</p><p>Example 3:<br>Requirement: User should be able to search for products.</p><p>Possible Edge Case:<br>Search term contains special characters.</p><p>Generate a possible edge case for:<br>Requirement: User should be able to apply a discount coupon.</p><p>— — — — — — — — — — — — — — — — — —</p><p>We’re providing multiple examples that show the pattern we want it to follow.</p><p>This is called Few-Shot Prompting.</p><p><strong>4. Role-Based Prompting</strong></p><p>Here’s a technique I use quite often.</p><p>Instead of asking AI a question directly, I first tell it what role it should play.</p><p>By assigning a role, we guide AI to respond from a specific perspective.</p><p>Prompt:</p><p>Act as a Senior QA Engineer with 10 years of experience.</p><p>Review the following requirement and identify any missing test scenarios.</p><p>Requirement:<br>User should be able to book a flight ticket by selecting the source, destination, travel date, and number of passengers.</p><p>— — — — — — — — — — — — — — — — — —</p><p>Before asking AI to perform the task, we’re assigning it the role of a Senior QA Engineer.</p><p>We’re also providing a requirement for AI to analyze.</p><p>AI will now review the requirement from the perspective of an Experienced Tester and identify scenarios, validations, and edge cases that might have been overlooked.</p><p>This is called Role-Based Prompting.</p><p>— — — — — — — — — — — — — — — — — — — —</p><p>Some examples of the QA / Testing Roles, you can probably use for your prompting.</p><p>Act as a Manual Test Engineer with 5 years of experience.<br>Act as a Senior QA Engineer with 10 years of experience.<br>Act as a QA Manager responsible for release quality.<br>Act as a Selenium Automation Test Engineer.<br>Act as a Playwright Automation Engineer.<br>Act as a Test Lead managing a QA team.<br>Act as a Performance Testing Engineer.<br>Act as a Accessibility Testing Expert.<br>Act as a Software Test Architect.<br>Act as an API Testing Expert.</p><p><strong>5. Constraint-Based Prompting</strong></p><p>Have you ever asked AI to generate test cases and received a very long response with more information than you actually needed?</p><p>That’s where constraints become useful.</p><p>Instead of only telling AI what task to perform, you also tell it how the output should be generated.</p><p>Prompt:</p><p>Generate test cases for a Login Page.</p><p>Constraints:<br>- Generate exactly 10 test cases<br>- Include only functional test scenarios<br>- Include only negative scenarios<br>- Present the output in a table<br>- Keep each description under 15 words</p><p>We’re not just asking AI to generate test cases.</p><p>We’re also defining clear rules that the response must follow.</p><p>These rules help control the format, length, quantity, and type of output we want.</p><p>This is called Constraint-Based Prompting.</p><p><strong>6. Chain of Thought (CoT) Prompting</strong></p><p>Let’s look at a real-world example.</p><p>Imagine you have an automation test that works perfectly on your local machine.<br>But when the same test runs in Jenkins, it fails with a timeout error.</p><p>Instead of asking AI a broad question like:<br>Why is my test failing?</p><p>you can encourage AI to think through the problem systematically.</p><p>Prompt:</p><p>A Selenium test passes locally but fails in Jenkins with a timeout error.</p><p>Think through the problem step by step.</p><p>Identify possible causes.</p><p>Explain your reasoning.</p><p>Recommend solutions for each cause.</p><p>— — — — — — — — — — — — — — — — — — — — — —</p><p>We’re not just asking AI for an answer.</p><p>We’re asking it to analyze the problem step by step, consider different possibilities, explain its reasoning, and then recommend solutions.</p><p>This often leads to a more structured and thoughtful response.</p><p>This is called Chain of Thought (CoT) Prompting.</p><p><strong>7. Context-Based Prompting</strong></p><p>Let’s look at one more useful technique.</p><p>Sometimes AI gives generic answers because it doesn’t know anything about your application or business rules.</p><p>The solution is to provide the necessary context before asking AI to perform a task.</p><p>Prompt:</p><p>Generate test scenarios for the Checkout feature.</p><p>Context:<br>- This is an e-commerce application.<br>- Only registered users can place orders.<br>- Cash on Delivery is available only for orders below ₹5,000.<br>- Users can apply only one coupon per order.<br>- Orders above ₹1,000 qualify for free shipping.</p><p>Consider the above context while generating test scenarios.</p><p>— — — — — — — — — — — — — — — — — — — — — —</p><p>We’re not simply asking AI to generate test scenarios for a Checkout feature.</p><p>We’re first providing important business rules and application-specific information that AI needs to understand the feature.</p><p>As a result, AI can generate scenarios related to registered users, coupon restrictions, Cash on Delivery limits, and free shipping eligibility instead of producing only generic checkout scenarios.</p><p>This is called Context-Based Prompting.</p><p>In real-world projects, you can also attach requirement “documents”, “user stories”, “acceptance criteria”, or “API specifications” as context instead of typing everything into the prompt.</p><p>Quick Summary on Prompt Engineering</p><p>Zero-Shot → One-Shot → Few-Shot: Progressively add examples.<br>Role-Based: Add a perspective or persona.<br>Constraint-Based: Add rules and boundaries.<br>Chain of Thought: Add reasoning and problem-solving.<br>Context-Based: Add business or application-specific information.</p><p>QA Engineers — <a href="https://swaroopnadella.kit.com/">Join my Email Newsletter (Click here)</a> to stay connected with me, confirm Subscription received on email.</p><p>— — — — — — — — —</p><p><strong>Swaroop Nadella</strong><br>QA Educator, Test Automation Engineer</p><p><a href="https://swaroopnadella.medium.com/subscribe">Subscribe here</a>, to Get an email whenever I publish article on Medium.</p><p><a href="https://academy.swaroopnadella.com/s/store">Swaroop Nadella Academy Store</a> — Quizzes and Courses</p><p><a href="https://www.youtube.com/@swaroopnadella">Swaroop Nadella — YouTube</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f3f54e707db" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Practical Roadmap to Enter Software Testing as a Fresher in 2026]]></title>
            <link>https://swaroopnadella.medium.com/practical-roadmap-to-enter-software-testing-as-a-fresher-in-2026-d6ea66b1f5af?source=rss-dd14fdf41792------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6ea66b1f5af</guid>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[selenium]]></category>
            <category><![CDATA[automation-testing]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <dc:creator><![CDATA[Swaroop Nadella]]></dc:creator>
            <pubDate>Wed, 27 May 2026 03:09:57 GMT</pubDate>
            <atom:updated>2026-05-27T03:09:57.849Z</atom:updated>
            <content:encoded><![CDATA[<h3>Many freshers entering Software Testing feel overwhelmed because there are too many tools, courses, and learning paths available today.</h3><p>Some try to learn everything together:<br>Selenium, Playwright, API Testing, Performance Testing, AI tools, Cloud, DevOps…</p><p>Eventually they get confused and stop learning consistently.</p><p>If someone wants to enter Software Testing in 2026, this is the practical path I would personally suggest.</p><h3>1. Learn Manual Testing Fundamentals First</h3><p>Before jumping into automation tools, understand how testing actually works.</p><p>Focus on basics like:</p><ul><li>SDLC and STLC</li><li>Test case writing</li><li>Bug life cycle</li><li>Defect reporting</li><li>Smoke testing</li><li>Sanity testing</li><li>Regression testing</li></ul><p>Strong fundamentals make automation learning much easier later.</p><h3>2. Practice on Real Websites</h3><p>Do not learn only theory.</p><p>Take any ecommerce, banking, or demo application and practice:</p><ul><li>writing test scenarios</li><li>identifying bugs</li><li>preparing bug reports</li><li>thinking like a tester</li></ul><p>Practical exposure matters more than memorizing definitions.</p><h3>3. Learn SQL Basics Properly</h3><p>Many QA freshers ignore SQL, but database validation is common in real projects.</p><p>At least learn:</p><ul><li>SELECT</li><li>WHERE</li><li>ORDER BY</li><li>basic JOINS</li><li>COUNT</li><li>validating whether data is correctly stored in database tables</li></ul><p>You do not need advanced database knowledge initially, but basic query understanding is very useful during interviews and projects.</p><h3>4. Learn API Testing Basics</h3><p>Modern applications heavily depend on APIs.</p><p>Start with tools like Postman and understand:</p><ul><li>GET, POST, PUT, DELETE requests</li><li>status codes</li><li>request and response validation</li><li>headers</li><li>authentication basics</li></ul><p>Even basic API knowledge can improve your profile significantly.</p><h3>5. Learn One Automation Stack</h3><p>Choose one path initially:</p><ul><li>Selenium with Java<br>or</li><li>Playwright with JavaScript/TypeScript</li></ul><p>Do not try to learn every automation tool together.</p><p>Depth is more useful than collecting too many beginner-level skills.</p><h3>6. Learn Version Control</h3><p>Basic Git and GitHub knowledge is becoming a common expectation in QA roles.</p><p>At least understand:</p><ul><li>repositories</li><li>commits</li><li>push/pull</li><li>branches</li><li>basic collaboration workflow</li></ul><h3>7. Build Small Projects</h3><p>Even simple practice projects help during interviews.</p><p>A small automation framework or API testing project is enough to demonstrate hands-on learning.</p><h3>8. Improve Communication Skills</h3><p>Many freshers ignore this part.</p><p>In QA roles, you will regularly:</p><ul><li>explain bugs</li><li>discuss issues with developers</li><li>share test results</li><li>communicate project updates</li></ul><p>Clear communication is an important skill for testers.</p><h3>Final Thoughts</h3><p>You do not need to become an expert in everything before applying for jobs.</p><p>Start with:</p><ul><li>strong fundamentals</li><li>hands-on practice</li><li>consistency</li></ul><p>That combination still works well for entering Software Testing in 2026.</p><p>Which of these steps are you focusing on right now in your QA journey?</p><p>QA Engineers — <a href="https://swaroopnadella.kit.com/">Join my Email Newsletter (Click here)</a> to stay connected with me, confirm Subscription received on email.</p><p>— — — — — — — — —</p><p><strong>Swaroop Nadella</strong><br>QA Educator, Test Automation Engineer</p><p><a href="https://swaroopnadella.medium.com/subscribe">Subscribe here</a>, to Get an email whenever I publish article on Medium.</p><p><a href="https://academy.swaroopnadella.com/s/store">Swaroop Nadella Academy Store</a> — Quizzes and Courses</p><p><a href="https://www.youtube.com/@swaroopnadella">Swaroop Nadella — YouTube</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6ea66b1f5af" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automation Test Engineer vs SDET: Same Job, Different Expectations]]></title>
            <link>https://swaroopnadella.medium.com/automation-engineer-vs-sdet-same-job-different-expectations-73e3b1456b89?source=rss-dd14fdf41792------2</link>
            <guid isPermaLink="false">https://medium.com/p/73e3b1456b89</guid>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[selenium]]></category>
            <category><![CDATA[playwright-automation]]></category>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[automation-testing]]></category>
            <dc:creator><![CDATA[Swaroop Nadella]]></dc:creator>
            <pubDate>Wed, 25 Mar 2026 04:17:20 GMT</pubDate>
            <atom:updated>2026-03-27T06:42:02.150Z</atom:updated>
            <content:encoded><![CDATA[<h3>Both roles write automation. The difference shows up in what they’re expected to own.</h3><p>“Automation Test Engineer” and “SDET” sound different.<br> In many teams, the work overlaps.</p><p>SDET: Software Development Engineer in Test</p><p>The difference shows up in expectations.</p><h3>Automation Test Engineer</h3><p>Typically expected to handle:</p><ul><li>UI/API automation (Selenium/Playwright/Cypress)</li><li>Test scripts maintenance</li><li>Debugging failures</li><li>Stable test execution in CI/CD</li></ul><p>Common stack (Taking example of Java language):</p><ul><li>Java (strong programming fundamentals)</li><li>TestNG or Cucumber (BDD) based frameworks</li><li>Postman + Rest Assured (API testing)</li></ul><p>If you’re learning Java for this role, focus on:</p><ul><li>Writing clean, readable test code</li><li>Understanding how your framework is structured</li><li>Making tests stable and maintainable</li></ul><p>Focus:</p><ul><li>Tests should run reliably in CI-CD (Jenkins / GitHub Actions, etc.)</li><li>Tests should give confidence</li></ul><h3>SDET (Software Development Engineer in Test)</h3><p>Works with the same tools - but expectations go further:</p><ul><li>Framework design / improvements</li><li>Changes that impact multiple teams</li><li>Reusable components and standards</li><li>Solving flaky tests, slow execution, test data issues</li><li>CI/CD and infrastructure involvement</li></ul><p>If you’re moving toward this role, start thinking about problems like:</p><ul><li>Why do tests break frequently when UI changes?</li><li>How can we reduce execution time across the entire suite?</li><li>How do we make tests independent and avoid data conflicts?</li><li>What part of the framework is causing most maintenance?</li><li>How can multiple teams reuse the same components?</li></ul><p>Focus:</p><ul><li>Testing should scale</li><li>Testing should not become a bottleneck</li></ul><p>Titles don’t always reflect this clearly.</p><p>You’ll see:</p><ul><li>SDETs doing basic scripting</li><li>Automation Engineers doing framework-level work</li></ul><p>What matters is:</p><ul><li>What you own</li><li>The level of problems you solve</li></ul><p>QA Engineers — <a href="https://swaroopnadella.kit.com/">Join my Email Newsletter (Click here)</a> to stay connected with me, confirm Subscription received on email.</p><p><strong>Swaroop Nadella</strong><br>QA Educator, Test Automation Engineer</p><p><a href="https://swaroopnadella.medium.com/subscribe">Subscribe here</a>, to Get an email whenever I publish article on Medium.</p><p><a href="https://academy.swaroopnadella.com/s/store">Swaroop Nadella Academy Store</a> — Quizzes and Courses</p><p><a href="https://www.youtube.com/@swaroopnadella">Swaroop Nadella — YouTube</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=73e3b1456b89" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[20 Software Testing terms with simple analogies]]></title>
            <link>https://swaroopnadella.medium.com/20-software-testing-terms-with-simple-analogies-382c42e7d565?source=rss-dd14fdf41792------2</link>
            <guid isPermaLink="false">https://medium.com/p/382c42e7d565</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[software-quality-engineer]]></category>
            <category><![CDATA[quality-engineering]]></category>
            <dc:creator><![CDATA[Swaroop Nadella]]></dc:creator>
            <pubDate>Thu, 15 Jan 2026 09:21:39 GMT</pubDate>
            <atom:updated>2026-01-15T09:21:39.531Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3ez3BQEVZuna6G_5zqu5Ig.png" /></figure><p>1. Test Case: <br>Think of it as a recipe in a cookbook. It tells you the exact steps, ingredients (inputs), and what the final dish (outcome) should look like.</p><p>2. Test Coverage: <br>Like checking how much of a wall you’ve painted. It measures how much of your application has been tested.</p><p>3. Test Plan: <br>Like a blueprint for building a house. It outlines the strategy, scope, resources, and schedule for your testing activities.</p><p>4. Test Scenario: <br>A real-world situation you want to test. Like checking if you can order food, pay for it, and get it delivered — that’s one complete scenario.</p><p>5. Test Data: <br>Like the ingredients you keep ready before cooking. It’s the information you prepare beforehand to use during testing.</p><p>6. Smoke Testing: <br>Before a long drive, you just check if the car starts. A quick check to see if the most important features are working at a basic level.</p><p>7. Sanity Testing: <br>After fixing a bug, you quickly verify that specific fix works. Like checking if the repaired door lock actually locks now.</p><p>8. Integration Testing: <br>Testing if different parts work together. Like checking if your phone charger works with your phone — individual parts are fine, but do they connect properly?</p><p>9. Functional Testing: <br>Like testing if all buttons on a remote control actually do what they’re supposed to do. Each feature works as expected.</p><p>10. Usability Testing: <br>Watching someone try an app for the first time. Is it easy to use or confusing? This tests the user’s experience.</p><p>11. Performance Testing: <br>Imagine how many people can safely stand on a bridge before it starts to shake. This checks software under heavy load.</p><p>12. Regression Testing: <br>After you change one ingredient in a recipe, you try it again to make sure the change didn’t break anything else.</p><p>13. Exploratory Testing: <br>Exploring a new city without a map. You test by following your curiosity, without predefined scripts.</p><p>14. Defect: <br>A crack in a vase. It means the software is not working the way it should.</p><p>15. Severity: <br>How serious is the damage? A small scratch on a car vs. a broken engine — both are issues, but impact is different.</p><p>16. Priority: <br>What needs to be fixed first based on business needs? A typo on the homepage might be low severity but high priority.</p><p>17. Test Environment: <br>Like a practice kitchen before opening a restaurant. It’s a setup that mimics production where you safely test without affecting real users.</p><p>18. Retesting: <br>After a mechanic fixes your car’s brakes, you test those specific brakes again. Retesting verifies that the reported defect is now fixed.</p><p>19. User Acceptance Testing: <br>Like letting customers taste a dish before adding it to the menu. End users validate if the software meets their actual needs.</p><p>20. Traceability Matrix: <br>Like a map connecting requirements to test cases. It ensures every requirement has been tested and nothing is missed.</p><p>QA Engineers — <a href="https://swaroopnadella.kit.com/">Join my Email Newsletter (Click here)</a> to stay connected with me, confirm Subscription received on email.</p><p>— — — — — — — — —</p><p><strong>Swaroop Nadella</strong><br>QA Educator, Test Automation Engineer</p><p><a href="https://swaroopnadella.medium.com/subscribe">Subscribe here</a>, to Get an email whenever I publish article on Medium.</p><p><a href="https://academy.swaroopnadella.com/s/store">Swaroop Nadella Academy Store</a> — Quizzes and Courses</p><p><a href="https://www.youtube.com/@swaroopnadella">Swaroop Nadella — YouTube</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=382c42e7d565" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Practical Roadmap for Software Testers in 2026]]></title>
            <link>https://swaroopnadella.medium.com/practical-roadmap-for-software-testers-46dc83409408?source=rss-dd14fdf41792------2</link>
            <guid isPermaLink="false">https://medium.com/p/46dc83409408</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[automation-testing]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[selenium]]></category>
            <category><![CDATA[test-automation]]></category>
            <dc:creator><![CDATA[Swaroop Nadella]]></dc:creator>
            <pubDate>Wed, 31 Dec 2025 12:37:13 GMT</pubDate>
            <atom:updated>2025-12-31T13:35:25.137Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’re a QA fresher or have a few years of experience in Software Testing and feel your career isn’t growing as fast as you expected, don’t worry — you’re not alone.<br>Many testers feel stuck at some point, and that’s completely normal.</p><p>Here’s a simple and practical roadmap that can help you move forward and find better opportunities in the QA world!</p><p>1. Strengthen Your Core<br> Revisit the basics — Test case design, Defect life cycle, SDLC, STLC, Test Plan, and Test Strategy.<br> A strong foundation always stands out in interviews.</p><p>2. Learn a Programming Language<br> Start with Java, JavaScript or Python.<br> Focus on understanding variables, loops, methods, classes, and debugging.<br> Strong coding skills make automation easier and help you grow faster as a test engineer.</p><p>3. Be Great at One Automation Tool<br> Pick one: Selenium with Java, Playwright or Cypress (with TypeScript).<br> You don’t need to know everything — just master one tool really well.</p><p>4. Learn to Build Frameworks<br> Don’t just run test scripts — learn to design frameworks using TestNG, Maven, and Page Object Model.<br> That’s what makes you a real automation engineer.<br> Design patterns to understand: Singleton, Factory, Builder and use them in framework building.</p><p>5. Learn API Testing<br> Pick up Postman / RestAssured.<br> Most modern applications depend on APIs — this skill opens more job roles.</p><p>6. Understand CI/CD and DevOps<br> Learn Jenkins, Git, and a bit of Docker.<br> Knowing how automation fits into pipelines gives you a big edge.</p><p>7. Build a GitHub Portfolio<br> Upload your projects.<br> Even a small Selenium-TestNG framework shows recruiters your hands-on skills.</p><p>8. Share Your Learnings on LinkedIn<br> Write short posts about what you learn or fix.<br> Visibility creates opportunities — people notice consistent learners.</p><p>9. Think Like a User, Not Just a Tester<br> Understand why a feature exists before testing it.<br> That mindset shift from tester to quality advocate changes everything.</p><p>10. Keep Learning and Networking<br> Join testing communities, attend meetups, and talk to peers.<br> Most career jumps come through people, not portals.</p><p>11. Understand How AI is Changing Testing<br> Start exploring how AI tools can assist in testing.<br> You don’t need to become a data scientist, but learn how tools like ChatGPT, Copilot, Claude, LLMs, MCPs can help in writing test cases, generating data, or improving automation scripts.<br> AI is not replacing testers — it’s helping smart testers work faster and think bigger.</p><p>Be curious, stay consistent, and make your work visible — the right opportunity will find you.</p><p>Which of these steps are you focusing on right now in your QA journey?</p><p>QA Engineers - <a href="https://swaroopnadella.kit.com/">Join my Email Newsletter (Click here)</a> to stay connected with me, confirm Subscription received on email.</p><p>— — — — — — — — —</p><p><strong>Swaroop Nadella</strong><br>QA Educator, Test Automation Engineer</p><p><a href="https://swaroopnadella.medium.com/subscribe">Subscribe here</a>, to Get an email whenever I publish article on Medium.</p><p><a href="https://academy.swaroopnadella.com/s/store">Swaroop Nadella Academy Store</a> — Quizzes and Courses</p><p><a href="https://www.youtube.com/@swaroopnadella">Swaroop Nadella — YouTube</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=46dc83409408" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automation Tester Portfolio]]></title>
            <link>https://swaroopnadella.medium.com/automation-tester-portfolio-c1389caab6a8?source=rss-dd14fdf41792------2</link>
            <guid isPermaLink="false">https://medium.com/p/c1389caab6a8</guid>
            <category><![CDATA[sdet]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[selenium-webdriver]]></category>
            <category><![CDATA[automation-testing]]></category>
            <category><![CDATA[selenium]]></category>
            <dc:creator><![CDATA[Swaroop Nadella]]></dc:creator>
            <pubDate>Sun, 08 Dec 2024 05:37:38 GMT</pubDate>
            <atom:updated>2024-12-08T05:38:07.426Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CJftT54xRGGvwBAKvM-T3Q.png" /><figcaption>Prompt in ChatGPT by Swaroop Nadella</figcaption></figure><p>I had asked ChatGPT one simple question: “Automation Tester Portfolio”.</p><p>It has given me the below results, which has some useful points.</p><p>I had modified the Certifications part, which is optional in most cases.</p><p>— — — — — — — — — — — — — —</p><p>Creating a strong portfolio as an automation tester is crucial to showcasing your skills, projects, and technical expertise.</p><p>Here’s how to build a compelling <strong>Automation Tester Portfolio</strong>:</p><p><strong>1. Personal Details and Profile Summary</strong></p><ul><li><strong>Name and Contact Information:</strong> Include your name, email, LinkedIn profile, and GitHub/portfolio links.</li><li><strong>Professional Summary:</strong> A brief overview of your expertise and experience.</li><li>Example:<br> <em>“Automation Tester with 3+ years of experience in designing, developing, and maintaining test automation frameworks using Selenium WebDriver, TestNG, and Maven. Proficient in Agile testing methodologies and experienced in implementing CI/CD pipelines with Jenkins and Docker.”</em></li></ul><p><strong>2. Key Skills</strong></p><p>Highlight your technical skills:</p><ul><li><strong>Test Automation Tools:</strong> Selenium WebDriver, Cypress, Playwright, Appium.</li><li><strong>Programming Languages:</strong> Java, Python, JavaScript.</li><li><strong>Frameworks:</strong> TestNG, JUnit, RestAssured.</li><li><strong>Build Tools:</strong> Maven, Gradle.</li><li><strong>Version Control:</strong> Git, GitHub.</li><li><strong>CI/CD Tools:</strong> Jenkins, GitLab CI, Docker.</li><li><strong>Test Management Tools:</strong> JIRA, TestRail.</li><li><strong>Others:</strong> API testing, Performance testing with JMeter.</li></ul><p><strong>3. Technical Projects</strong></p><p>Showcase your practical work with detailed descriptions. Include:</p><ul><li><strong>Project Title</strong></li><li><strong>Objective:</strong> The goal of the project.</li><li><strong>Technologies Used:</strong> List tools, frameworks, and languages.</li><li><strong>Description:</strong> Highlight challenges faced, solutions implemented, and the impact.</li><li><strong>GitHub/Link to the Repository (if applicable)</strong></li></ul><p><strong>Example Projects:</strong></p><ol><li><strong>E-commerce Website Automation</strong></li></ol><ul><li><strong>Objective:</strong> Automated functional and regression testing for an e-commerce platform.</li><li><strong>Technologies Used:</strong> Selenium WebDriver, Java, TestNG, Maven, Jenkins.</li><li><strong>Description:</strong> Developed a robust data-driven framework to execute test cases across multiple browsers. Integrated with Jenkins for continuous testing.</li><li><strong>Outcome:</strong> Reduced manual testing efforts by 70% and ensured zero critical defects in production.</li></ul><ol><li><strong>API Testing for Banking Application</strong></li></ol><ul><li><strong>Objective:</strong> Validated RESTful APIs for a banking application.</li><li><strong>Technologies Used:</strong> RestAssured, Postman, TestNG, Jenkins.</li><li><strong>Description:</strong> Automated API testing with RestAssured and set up CI pipelines.</li><li><strong>Outcome:</strong> Detected and resolved API response inconsistencies, improving system reliability.</li></ul><p><strong>4. Certifications</strong></p><p>Add certifications to validate your expertise:</p><ul><li>ISTQB Foundation/Advanced Level.</li><li>AWS, Azure Cloud Certifications.</li><li>Certified Java Programmer (Oracle).</li></ul><p><strong>5. Portfolio Website or GitHub Profile</strong></p><p>Create a portfolio website or GitHub repository that hosts:</p><ul><li>Automation frameworks you’ve built.</li><li>Sample test scripts with proper documentation.</li><li>Demo videos showing automation execution.</li><li>Blog posts explaining your approach to automation challenges.</li></ul><p><strong>6. LinkedIn Profile</strong></p><ul><li>Update your LinkedIn profile with your automation projects, skills, and achievements.</li><li>Post regularly about test automation trends, solutions, or your project experiences.</li></ul><p><strong>7. Blog or YouTube Channel</strong></p><ul><li>Share your knowledge by writing blogs or creating videos on:</li><li>Best practices in test automation.</li><li>Setting up frameworks from scratch.</li><li>Solving real-world testing challenges.</li></ul><p><strong>8. Soft Skills</strong></p><p>Mention skills like:</p><ul><li>Problem-solving.</li><li>Collaboration in Agile teams.</li><li>Communication with stakeholders.</li><li>Continuous learning and adaptability.</li></ul><p><strong>9. Recommendations</strong></p><p>Include testimonials or LinkedIn recommendations from colleagues or mentors that highlight your expertise in test automation.</p><p>— — — — — — — — — — — —</p><p><strong>Swaroop Nadella</strong><br>Test Automation Engineer, Tech Educator</p><p><a href="https://swaroopnadella.medium.com/subscribe">Subscribe here</a>, to Get an email whenever I publish article on Medium.</p><p><a href="https://www.udemy.com/course/core-java-and-coding-for-automation-testers-for-beginners/?referralCode=15EA484AC2E9ED171724">Core Java and Coding for Automation Testers — Udemy Course</a></p><p><a href="https://academy.swaroopnadella.com/s/store">Swaroop Nadella Academy Store</a> — Quizzes and Courses</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c1389caab6a8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Software Defect Life Cycle with Storytelling!]]></title>
            <link>https://swaroopnadella.medium.com/software-defect-life-cycle-with-storytelling-11b2a8d4595f?source=rss-dd14fdf41792------2</link>
            <guid isPermaLink="false">https://medium.com/p/11b2a8d4595f</guid>
            <category><![CDATA[defect]]></category>
            <category><![CDATA[defect-management]]></category>
            <category><![CDATA[software-defect]]></category>
            <category><![CDATA[defect-life-cycle]]></category>
            <category><![CDATA[software-testing]]></category>
            <dc:creator><![CDATA[Swaroop Nadella]]></dc:creator>
            <pubDate>Mon, 07 Oct 2024 13:44:11 GMT</pubDate>
            <atom:updated>2024-10-07T13:44:11.848Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SXik8sm3cAM2EbQaAFPSJg.png" /><figcaption>created by Swaroop Nadella using Microsoft Designer</figcaption></figure><p>In the land of Software Development, there was a Team of Testers known as “The Bug Busters.”</p><p>Their mission? <br>To hunt down defects and make the software world a better place.</p><p>Let me tell you the journey of a defect,</p><p>from its discovery to its final fate:</p><p>- New Bug Found (Discovery): <br>During their daily explorations, a Bug Buster spotted something strange — a defect lurking in the code. They captured it, recorded its details, and marked it as “New.” The journey of the defect had just begun.</p><p>- Assigned (The Bug is Chained): <br>The Bug Buster didn’t keep the defect to themselves. Instead, they handed it over to the Developer, the warrior skilled in fixing. The developer now had the responsibility to handle this new threat.</p><p>- Open (Preparing for the Battle): <br>The developer examined the defect, acknowledging its presence and preparing to fix it. This was the moment the defect officially became “Open,” ready to be worked on.</p><p>- Fixed (Battle Won): <br>After a fierce struggle, the developer emerged victorious. The defect was defeated, and the code was repaired. The developer proudly marked the defect as “Fixed,” but the Bug Busters knew their work wasn’t done yet.</p><p>- Retest (Double-Check): <br>The Bug Busters returned to the scene of the battle, testing the same area of the software to ensure the defect was truly gone. If everything worked as expected, they could declare victory.</p><p>- Reopen (The Comeback, if Needed):<br>Sometimes, the Bug Busters discovered that the defect had resurfaced or wasn’t completely fixed. In those cases, they “Reopened” the defect, sending it back to the developer for another round.</p><p>- Closed (End of the Journey): <br>Finally, if the retest was successful and the defect was completely defeated, it was marked as “Closed.” The defect’s journey ended here, never to return.</p><p>And so, with teamwork and vigilance, the Bug Busters ensured that every defect was properly handled, and the software was free from flaws.</p><p>This is how defects lived and died in the world of testing.</p><p><strong>Swaroop Nadella</strong><br>Test Automation Engineer, Tech Educator</p><p><a href="https://swaroopnadella.medium.com/subscribe">Subscribe here</a>, to Get an email whenever I publish article on Medium.</p><p><a href="https://www.udemy.com/course/core-java-and-coding-for-automation-testers-for-beginners/?referralCode=15EA484AC2E9ED171724">Core Java and Coding for Automation Testers — Udemy Course</a></p><p><a href="https://academy.swaroopnadella.com/s/store">Swaroop Nadella Academy Store</a> — Quizzes and Courses</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11b2a8d4595f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simple steps to create a GitHub profile]]></title>
            <link>https://swaroopnadella.medium.com/simple-steps-to-create-a-github-profile-e0ecb89d1927?source=rss-dd14fdf41792------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0ecb89d1927</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[automation-tester]]></category>
            <category><![CDATA[practice-in-public]]></category>
            <category><![CDATA[automation-testing]]></category>
            <dc:creator><![CDATA[Swaroop Nadella]]></dc:creator>
            <pubDate>Sun, 06 Oct 2024 05:15:49 GMT</pubDate>
            <atom:updated>2024-10-06T05:15:49.828Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ukXxgILha3dSkWyulbJR4A.png" /></figure><p>Is GitHub profile important as a Software Tester?</p><p>If you are into Automation Testing and looking to showcase your skill set with practical hands-on projects — having a GitHub profile definitely helps.</p><p>In this blog we will explore the Steps you can follow to create an GitHub Account, creating new repositories and adding ReadMe file to the repo.</p><p>If you intend to learn from other people’s work, do checkout the GitHub profiles using search feature on the website and learn from their work. There are many existing projects, frameworks and practice portfolios published for free on GitHub which you can utilize for learning purpose.</p><p>GitHub portfolio work helps to add some value to your skills listed in the Resume. You could also confidently talk about these hands-on projects during the Interviews.</p><p>Create and publish your practice projects (Web or API Automation practice), don’t need to be perfect, start something and keep going in Iterations.</p><p>~~~~~~~~~~~~~~</p><p>Some Steps are listed below which can be useful for creating new GitHub profile.</p><p>1. Sign Up for a GitHub Account</p><p>Go to GitHub’s website.</p><p>Click on “Sign Up” and enter your email, create a password, and choose a username.</p><p>Confirm your email address through the verification link sent to your inbox.</p><p>2. Set Up Your Profile</p><p>Once signed in, click on your profile icon at the top right and select “Your Profile.”</p><p>Add a profile picture, bio, and relevant information such as your location or website link to personalize your profile.</p><p>3. Create Your First Repository</p><p>Click the “+” icon at the top right and select “New Repository.”</p><p>Give your repository a name, choose whether it will be public or private, and add a README file.</p><p>A README file is important as it allows you to introduce your project and provide instructions to visitors.</p><p>4. Customize Your README Profile</p><p>To make your profile more personal, create a special repository with the exact same name as your GitHub username.</p><p>GitHub will automatically display the README file from this repository on your profile page.</p><p>In this README, you can include a brief introduction, your skills, projects, and links to your social media profiles or portfolio.</p><p>5. Explore and Contribute</p><p>Explore other repositories to see how developers structure their projects.</p><p>Start by forking or cloning open-source projects, contributing to them, or just starring them to follow updates.</p><p>As you contribute, your profile will show your activity and contributions to the open-source community.</p><p>Refer to my GitHub profile — Starred repositories for some useful Automation Testing framework content: <a href="https://github.com/swaroopnadella">https://github.com/swaroopnadella</a></p><p><strong>Swaroop Nadella</strong><br>Test Automation Engineer, Tech Educator</p><p><a href="https://swaroopnadella.medium.com/subscribe">Subscribe here</a>, to Get an email whenever I publish article on Medium.</p><p><a href="https://www.udemy.com/course/core-java-and-coding-for-automation-testers-for-beginners/?referralCode=15EA484AC2E9ED171724">Core Java and Coding for Automation Testers — Udemy Course</a></p><p><a href="https://academy.swaroopnadella.com/s/store">Swaroop Nadella Academy Store</a> — Quizzes and Courses</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0ecb89d1927" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What does ‘public static void main’ mean in Java?]]></title>
            <link>https://swaroopnadella.medium.com/what-does-public-static-void-main-mean-in-java-0b6a60070257?source=rss-dd14fdf41792------2</link>
            <guid isPermaLink="false">https://medium.com/p/0b6a60070257</guid>
            <category><![CDATA[java]]></category>
            <category><![CDATA[java-automation-testing]]></category>
            <category><![CDATA[basics-of-programming]]></category>
            <category><![CDATA[java-programming]]></category>
            <category><![CDATA[automation-testing]]></category>
            <dc:creator><![CDATA[Swaroop Nadella]]></dc:creator>
            <pubDate>Thu, 03 Oct 2024 18:22:04 GMT</pubDate>
            <atom:updated>2024-10-03T18:22:04.344Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RUoYfDOQtiZX_BOPk3NAVg.png" /><figcaption>created by Swaroop Nadella using Microsoft Designer</figcaption></figure><p>In Java, the main method is the entry point of any standalone Java application.</p><p>Here’s a breakdown of the basic components:</p><p>Syntax:</p><p>public static void main(String[ ] args) {<br> // code to be executed<br>}</p><p>Explanation:</p><p>1. public: This means the method is accessible from outside the class. It must be public because the JVM needs to call it from outside.</p><p>2. static: This means the method belongs to the class itself rather than an instance of the class. The JVM can call this method without creating an object of the class.</p><p>3. void: This specifies that the method does not return any value.</p><p>4. main: This is the name of the method that is predefined in Java. The JVM looks for this method as the starting point for execution.</p><p>5. String[ ] args: This is an array of strings that stores command-line arguments passed to the program. If no arguments are passed, the array is empty.</p><p>Example:</p><p>public class Main {<br> public static void main(String[ ] args) {<br> System.out.println(“Hello Swaroop”);<br> }<br>}</p><p>In this example, <br>System.out.println(“Hello Swaroop”); is the code that gets executed when you run the program.</p><p>Output: <strong>Hello Swaroop</strong> is printed on the Console window.</p><p>Would you like to try this out in a Java Coding IDE?</p><p><strong>Swaroop Nadella</strong><br>Test Automation Engineer, Tech Educator</p><p><a href="https://swaroopnadella.medium.com/subscribe">Subscribe here</a>, to Get an email whenever I publish article on Medium.</p><p><a href="https://www.udemy.com/course/core-java-and-coding-for-automation-testers-for-beginners/?referralCode=15EA484AC2E9ED171724">Core Java and Coding for Automation Testers — Udemy Course</a></p><p><a href="https://academy.swaroopnadella.com/s/store">Swaroop Nadella Academy Store</a> — Quizzes and Courses</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0b6a60070257" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What to learn as QA Fresher in 2024?]]></title>
            <link>https://swaroopnadella.medium.com/what-to-learn-as-qa-fresher-in-2024-71fceb22977f?source=rss-dd14fdf41792------2</link>
            <guid isPermaLink="false">https://medium.com/p/71fceb22977f</guid>
            <category><![CDATA[freshers]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[automation-testing]]></category>
            <category><![CDATA[selenium]]></category>
            <dc:creator><![CDATA[Swaroop Nadella]]></dc:creator>
            <pubDate>Mon, 30 Sep 2024 05:52:51 GMT</pubDate>
            <atom:updated>2024-09-30T05:52:51.175Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xaa1MeuLJXWbL7lnEpzZfg.jpeg" /><figcaption>created by Swaroop Nadella using Microsoft Designer</figcaption></figure><p>As an Beginner into Software Testing and Automation, often QA Freshers are confused on what to learn.</p><p>So this article helps to create an guide or roadmap, to help them navigate the Preparation and help to standout in the crowded Job market in 2024 and beyond.</p><p>There is no single course which will have everything on the topics listed below.</p><p>Internet is your playground and Google search; YouTube is the first place you could get most of the answers on each topic, if you intend to learn at zero cost.</p><p>Practice is your magic wand to skill up, as an QA Fresher or even for Experienced folks.</p><p>1) Software Testing Fundamentals — understand basics<br>2) API Testing with Postman — learn Rest API fundamentals</p><p>3) Core Java programming — important for automation test learnings.<br>4) Beginner to Intermediate level coding — logic building and interviews</p><p>5) Selenium UI automation, hand’s on with TestNG framework + Selenium Grid + Docker + Git + Jenkins is good to have.</p><p>Some awareness of Automation is needed.</p><p>Saying I don’t know anything doesn’t help.</p><p>6) SQL basics and writing SQL queries — database testing awareness helps<br>7) Good communication skills — able to present effectively.</p><p>Maintain One Personal Technical Blog. Any website — Medium, Blogspot, Wordpress, etc.</p><p>You can also publish the same blogs as LinkedIn article as an additional post for increasing the visibility on LinkedIn feed.</p><p>Write some content regularly every week in your blog, Two micro topics (Testing and Automation). Content ideas are unlimited as you learn each topic.</p><p>Maintain GitHub personal Account with Practice work projects, publish the code into a new Git Repository.</p><p>Include the Practice portfolio projects work in your Resume.</p><p>Having only skills listed doesn’t help to get shortlisted or standout when there are 1000s of people applying to same job opportunity.</p><p>Do you have any other comments or suggestions? do share for helping other folks reading this article.</p><p><strong>Swaroop Nadella</strong><br>Test Automation Engineer, Tech Educator</p><p><a href="https://swaroopnadella.medium.com/subscribe">Subscribe here</a>, to Get an email whenever I publish article on Medium.</p><p><a href="https://www.udemy.com/course/core-java-and-coding-for-automation-testers-for-beginners/?referralCode=15EA484AC2E9ED171724">Core Java and Coding for Automation Testers — Udemy Course</a></p><p><a href="https://academy.swaroopnadella.com/s/store">Swaroop Nadella Academy Store</a> — Quizzes and Courses</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71fceb22977f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>