<?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 Faisal Khan on Medium]]></title>
        <description><![CDATA[Stories by Faisal Khan on Medium]]></description>
        <link>https://medium.com/@faisal-khan?source=rss-f968014ee8b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*9GqHsNAtXNbbHk8HpsvcQQ.png</url>
            <title>Stories by Faisal Khan on Medium</title>
            <link>https://medium.com/@faisal-khan?source=rss-f968014ee8b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 23:25:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@faisal-khan/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[-  .      ]]></title>
            <link>https://medium.com/@faisal-khan/-9172db9d57c4?source=rss-f968014ee8b------2</link>
            <guid isPermaLink="false">https://medium.com/p/9172db9d57c4</guid>
            <dc:creator><![CDATA[Faisal Khan]]></dc:creator>
            <pubDate>Mon, 25 May 2026 16:44:34 GMT</pubDate>
            <atom:updated>2026-05-25T16:44:34.908Z</atom:updated>
            <content:encoded><![CDATA[<p>We keep hearing about shift-left, and rightly so. Quality should be considered early, not only when development is complete.<br>But modern delivery needs a broader view. Quality does not belong only at the beginning of the lifecycle. It belongs across the entire lifecycle:<br>Discovery and design — where risks, assumptions, and gaps can be challenged early.<br>Build and validation — where checks need to be continuous, reliable, and close to the code.<br>Release readiness and production — where real-world behavior tells us what our tests may have missed.</p><p>That is why the conversation needs to move from shift-left to 𝐬𝐡𝐢𝐟𝐭-𝐞𝐯𝐞𝐫𝐲𝐰𝐡𝐞𝐫𝐞.<br>Because today, quality is not just about finding defects earlier. It is about preventing risks before they are built, validating confidence before release, learning from production, and feeding those learnings back into how teams build next.</p><p>QA belongs wherever risk exists. And in modern software delivery, risk exists everywhere. So the real question is not whether QA should shift left. It is whether your quality practices are shifting with the risks.</p><p>I’d love to hear how you are moving beyond shift-left and building quality into every part of delivery.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9172db9d57c4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Hidden Skill Behind QA Transformations]]></title>
            <link>https://medium.com/@faisal-khan/the-hidden-skill-behind-qa-transformations-53e7cc5ded49?source=rss-f968014ee8b------2</link>
            <guid isPermaLink="false">https://medium.com/p/53e7cc5ded49</guid>
            <dc:creator><![CDATA[Faisal Khan]]></dc:creator>
            <pubDate>Mon, 16 Mar 2026 04:37:47 GMT</pubDate>
            <atom:updated>2026-03-16T04:37:47.411Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/952/1*7WMbdWTkSBg5wR-TXavBsA.png" /></figure><p>Today, there is a gold rush across QE teams to adopt the latest AI driven testing tools, and rightly so. –There is a lot of focus to figure out AI assisted tools, MCP based Agentic Automation and Auto-Healing functionalities</p><p>Much of the conversation is about which tools to adopt and how quickly teams can start using them. But sometimes in that rush towards tooling, we overlook a capability that often determines whether these transitions actually succeed.A capability that rarely appears in job descriptions or skill matrices.</p><p><strong>Attitude.</strong></p><p>Not the motivational-poster version of attitude, but the real one — the willingness to learn, adapt, and step outside your comfort zone. Because every major shift in QA has required exactly that.</p><h3>Automation Didn’t Just Change Tools — It Changed Mindsets</h3><p>About a decade ago, QA went through one of its biggest transitions — moving from manual testing to automation driven testing.</p><p>Naturally, organizations approached this shift in a predictable way.</p><p>Train manual testers in automation tools.<br>Introduce frameworks like Selenium, Cypress, or Playwright.<br>Expect teams to start writing automated tests.</p><p>Some teams made that transition smoothly. Others struggled.</p><p>Over time, a pattern became clear. The testers who succeeded weren’t always the ones with the strongest technical starting point. They were often the ones who showed the right attitude toward learning.</p><p>They debugged when scripts failed. They asked questions when things didn’t make sense. They kept experimenting even when progress was slow.</p><p>The difference wasn’t just skill. It was their approach to learning.</p><h3>The Same Pattern Is Happening Again — This Time With AI</h3><p>Today QA is entering another major transition — from automation centric testing to AI assisted and agent driven testing.</p><p>AI tools can generate tests. Agents can execute functional flows. Systems are beginning to make decisions during execution.</p><p>Naturally, the first question many organizations ask is:</p><p><em>“Do our testers have the right technical skills?”</em></p><p>It’s a fair question. But an equally important one is:</p><p><strong>“Do they have the mindset to keep learning as the role evolves?”</strong></p><p>Because the tools we are learning today may not be the ones we use tomorrow.</p><h3>The Skill We Don’t Talk About Enough</h3><p>Automation skills matter. AI literacy will matter even more.</p><p>But the capability that enables both is something harder to measure.</p><p><strong>Attitude toward continuous learning.</strong></p><p>Because the pace of change in QA has fundamentally shifted.</p><p>There was a time when you could build a career around a single tool — Selenium, for example — and remain relevant for years.</p><p>That world is gone.</p><p>Today, new testing tools, AI assistants, and agentic systems appear every few months — sometimes every few weeks.</p><p>What matters is no longer <strong>which tool you know</strong>, <strong>but</strong> <strong>how quickly you can learn the next one.</strong></p><p>The testers who will thrive in this environment won’t be defined by a framework on their résumé. They’ll be defined by something simpler:</p><p>The willingness to say — <strong><em>“I don’t know this yet — but I’ll figure it out.”</em></strong></p><p>That mindset helped QA professionals evolve through automation.<br>And it will help them evolve through the AI driven future of testing.</p><h3>What This Means for QA Leaders</h3><p>As leaders, we often focus heavily on building technical capability within our teams.</p><p>That’s important — teams need strong engineers who understand systems, testing strategy, and the evolving technology landscape. But in a world where that technology landscape is changing rapidly, technical capability alone can’t be the only focus.</p><p>We also need to pay attention to how people approach learning and problem solving. Because the strongest QE teams aren’t simply the ones with the best tech stack. They’re the ones with people who evolve as the technology evolves.</p><p>And that has implications not just for how we train teams, but also for how we hire and evaluate talent. In a rapidly evolving technology landscape, the most valuable QA professionals aren’t just the ones who know today’s stack. They’re the ones who can adapt quickly, solve unfamiliar problems, and keep moving forward.</p><p>Which means interviews should go beyond checking familiarity with latest technologies. We should also look for curiosity, resilience, and a problem-solving mindset — people who take ownership when things break and are willing to explore unfamiliar territory.</p><p><strong>Because technologies can be learned. But the attitude to keep learning is what ultimately determines who thrives in a constantly evolving QA landscape.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53e7cc5ded49" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The career trap no one talks about in QA: always busy, always there and yet invisible]]></title>
            <link>https://medium.com/@faisal-khan/the-career-trap-no-one-talks-about-in-qa-always-busy-always-there-and-yet-invisible-9cf5ade18d82?source=rss-f968014ee8b------2</link>
            <guid isPermaLink="false">https://medium.com/p/9cf5ade18d82</guid>
            <category><![CDATA[career-trap]]></category>
            <category><![CDATA[growth-mindset]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[software-testing]]></category>
            <dc:creator><![CDATA[Faisal Khan]]></dc:creator>
            <pubDate>Sun, 01 Mar 2026 10:09:02 GMT</pubDate>
            <atom:updated>2026-03-01T10:09:02.512Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4-N185BX5xESsG0E2fBUQw.png" /></figure><p>You’re showing up every day. You’re writing test cases, you are automating, you are finding bugs, you are slogging late hours to ensure release is certified. <br>But you’re not growing. You’re not getting noticed. And slowly, you’re starting to wonder:</p><p><strong>“What am I doing wrong?”</strong></p><p>You’re not alone. This is the career trap many testers fall into — constantly busy, yet rarely seen.</p><p>Over the last decade, software delivery has changed faster than QA roles have evolved. Agile accelerated delivery cycles. Automation standardized execution. And now AI is beginning to automate parts of testing itself.</p><p>The result? Execution work is more necessary than ever — but less visible as a differentiator.</p><h3>Busy Doesn’t Mean Valuable</h3><p>You’re the go-to person. You finish your tasks. You find bugs. You never miss a deadline.</p><p>But here’s the tough part: being reliable isn’t the same as being impactful. If all you do is deliver what’s assigned, people may appreciate you — but they won’t necessarily see you. If you’re only seen as someone who executes — not someone who shapes quality — you’re replaceable.</p><p>The uncomfortable reality is this: modern QA careers don’t stagnate because testers lack skill or they don’t put in enough effort — they stagnate because execution alone no longer creates visibility or influence.</p><h3>You’re Delivering — But on Someone Else’s Terms</h3><p>You wait for a ticket. You test what’s written. You pass or fail the story. You move on.</p><p>But QA isn’t just about validating what’s built. It’s about questioning what’s being built in the first place.</p><p>You can’t expect to grow if you’re stuck operating at the tail-end of the process.</p><h3>You’ve Outgrown the Role — But You Haven’t Changed the Way You Show Up</h3><p>You’re capable of more. But you’re still showing up like a junior. Quiet. Head down. Waiting for work.</p><p>If you want to be seen as a senior QA or a future leader, you have to start acting like one before you’re given the title.</p><p>Growth doesn’t start when someone promotes you. It starts when you change how you show up.</p><h3>How Do You Break Out of the Trap?</h3><h4>Start Asking Better Questions</h4><p>Shift from <em>“What needs to be tested?”</em> to:</p><ul><li>What assumptions are we making here?</li><li>Where could this break in production?</li><li>How can we test the intent behind the feature — not just the output?</li></ul><p>Testers who ask these kinds of questions get pulled into conversations earlier. They’re seen. They’re heard. They’re respected.</p><h3>Be Present Before Testing Begins</h3><p>Refinement isn’t optional. It’s your entry point to influence. Don’t just focus on how the feature is getting developed, but rather understand why it’s being developed. Ask questions. Challenge the assumptions.</p><p>That’s enough to shift how people see you.</p><h3>Upskill With Purpose</h3><p>Don’t learn tools in panic because someone said “AI agents” in a meeting. Learn with context. Learn what helps your current team. Learn what helps you show up more effectively.</p><p>Have a learning plan documented for yourself — Short term, that helps for next 1–3 months, and a long term for 6–12 months.</p><p>And remember: learning doesn’t mean only coding. It also means understanding domain, debugging logs, or pairing with developers to gain clarity.</p><h3>Make Your Thinking Visible</h3><p>Share what you learn — inside your team and outside it. If you follow a best practice that has helped you, share it with wider team. Your visibility grows when your thinking becomes visible, not just your execution.</p><h3>Breaking the Trap</h3><p>The trap isn’t about lack of effort. It’s about operating in a narrow lane — and not realizing how much more you’re capable of.</p><p>You don’t need to work harder. You need to work smarter and show up with more intent.</p><p>Because the career trap in QA isn’t about working too little — it’s about working in ways that remain invisible.</p><p>The testers who grow aren’t just the ones who test well. They’re the ones who influence earlier, think broader, and make quality a shared conversation — not a final checkpoint.</p><p>Because in today’s world, being busy is common.<br><strong>Being visible through impact is what takes you to the next level.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9cf5ade18d82" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[QA Isn’t Being Replaced — It’s Being Reimagined]]></title>
            <link>https://medium.com/@faisal-khan/qa-isnt-being-replaced-it-s-being-reimagined-f942d289e757?source=rss-f968014ee8b------2</link>
            <guid isPermaLink="false">https://medium.com/p/f942d289e757</guid>
            <dc:creator><![CDATA[Faisal Khan]]></dc:creator>
            <pubDate>Sat, 14 Feb 2026 16:15:44 GMT</pubDate>
            <atom:updated>2026-02-15T05:56:45.004Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BbrFnw50OhMjlDQSv3tgFg.png" /></figure><p>The way we test software is transforming faster than ever — but what does that mean for the future of QA professionals ?</p><p>Every few years, a new wave of technology changes how testing is done and every time, the same concern resurfaces:</p><p><strong>“Is this the end of the QA role as we know it?”</strong></p><p>After 20+ years in QA, I’ve learned the answer never changes:<br><strong>QA evolves. Always.</strong><br>And each evolution redefines what QA professionals must deliver.</p><h3><strong>From Manual Execution to Automation</strong></h3><p>When automation arrived, it didn’t remove testers — it removed repetition.</p><p>Manual testing didn’t vanish — it evolved. The testers who learned to express their testing craft in code were the ones who truly flourished.</p><p>We shifted from doing testing to engineering how testing happens.</p><h3><strong>From Automation to AI-Assisted Testing</strong></h3><p>Then came AI code assistants like ChatGPT and Copilot — making automation easier and faster to build.</p><p>A well-crafted prompt could generate a script in minutes. The value of QA shifted again: Not how fast we automate — But how intelligently we choose what to test.</p><p>Coverage, Risk, Business relevance and User experience. QA moved up the value chain once more.</p><h3><strong>The Rise of AI Agents in QA</strong></h3><p>We’re now seeing AI QA agents that execute tests with context and adaptability:</p><p>AI QA agents today can:</p><ul><li>Execute functional test flows directly in the application — and automate those flows as they execute</li><li>Adapt to state conditions and make run-time decisions (e.g., continue if already logged in, recover intelligently)</li><li>Self-heal locator issues instead of failing</li></ul><p>AI agents don’t just run steps — they interpret them.</p><p>This isn’t the future — it’s the present.</p><h3><strong>The Future QA Team: Humans + Agents</strong></h3><p>The next evolution isn’t agents that run tests — it’s agents that learn what they’re testing.</p><p>Over the next few years, AI agents will:</p><ul><li>Learn product workflows through repeated execution</li><li>Identify risk from patterns and usage signals</li><li>Recommend what to test based on change impact</li><li>Evolve coverage as the product evolves</li></ul><p>Which leads to a new QA team structure:</p><p><strong>Future QA teams = Humans + Agents</strong> working together inside Scrum teams, every day.</p><p>It may feel far-fetched today, but given how quickly the AI landscape is evolving, it may arrive sooner than we expect.</p><h3><strong>How QA Must Adapt</strong></h3><p>The next evolution of QA isn’t just stronger automation skills, it’s understanding how intelligent systems work.</p><p>AI systems don’t fail like traditional software. They drift, hallucinate, generalize incorrectly, or succeed in ways that hide risk.</p><p>The QA must learn to work with AI, not around it — guiding agents, validating their conclusions, understanding how the underlying models influence outcomes and ensuring their interpretation of quality aligns with business outcomes.</p><p>Because even when AI is testing the product, someone still has to test the AI.</p><p>Human judgment remains irreplaceable: understanding customer intent, risk, and trust — the things no model can fully infer.</p><p>That’s why, even as AI takes center stage, QA professionals will remain at the center of quality — adapting, leading, and ensuring trust every step of the way.</p><p><strong>The future belongs to QA professionals who keep evolving — in skills, in thinking, and in how they deliver quality.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f942d289e757" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>