<?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 Ana Nur Rani on Medium]]></title>
        <description><![CDATA[Stories by Ana Nur Rani on Medium]]></description>
        <link>https://medium.com/@ananur.rani?source=rss-e8874f2fff2d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*d0-aHgaB7lTuq-gwoPtufA.jpeg</url>
            <title>Stories by Ana Nur Rani on Medium</title>
            <link>https://medium.com/@ananur.rani?source=rss-e8874f2fff2d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 13:27:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ananur.rani/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[How AI Helps QA Engineers Create Better Test Scenarios]]></title>
            <link>https://medium.com/@ananur.rani/how-ai-helps-qa-engineers-create-better-test-scenarios-e3016cc6f62b?source=rss-e8874f2fff2d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e3016cc6f62b</guid>
            <dc:creator><![CDATA[Ana Nur Rani]]></dc:creator>
            <pubDate>Mon, 25 May 2026 12:31:01 GMT</pubDate>
            <atom:updated>2026-05-25T12:31:01.343Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UqFUUkvrLTGZRejPSbDO2A.png" /><figcaption>AI Help QA</figcaption></figure><p>Creating test scenarios is one of the most important responsibilities in software testing. A good test scenario helps teams identify risks early, improve software quality, and reduce production issues.</p><p>Traditionally, QA Engineers created test scenarios manually by analyzing requirements, user flows, and business logic.</p><p>Today, AI is changing that process.</p><p>AI is not replacing QA Engineers — but it is helping them create test scenarios faster, broader, and smarter.</p><h3>Why Test Scenario Creation Takes Time</h3><p>Creating high-quality test scenarios is not just about writing “click this button and verify the result.”</p><p>QA Engineers must think about:</p><ul><li>User behavior</li><li>Business rules</li><li>Edge cases</li><li>Invalid inputs</li><li>Risk areas</li><li>System integration</li><li>Performance impact</li></ul><p>For complex applications like fintech or banking systems, this process can take hours or even days.</p><h3>How AI Helps Generate Test Scenarios</h3><p>Modern AI tools can analyze:</p><ul><li>User stories</li><li>Acceptance criteria</li><li>API documentation</li><li>Existing test cases</li><li>Application flows</li></ul><p>Then AI can quickly generate:</p><ul><li>Positive scenarios</li><li>Negative scenarios</li><li>Boundary test cases</li><li>Edge cases</li><li>Regression scenarios</li></ul><p>For example, from a simple login requirement, AI may instantly suggest:</p><ul><li>Invalid password attempts</li><li>Empty input validation</li><li>Session timeout checks</li><li>Multi-device login testing</li><li>Rate-limiting scenarios</li></ul><p>This significantly reduces the initial brainstorming effort.</p><h3>AI Helps QA Think Broader</h3><p>Sometimes, QA Engineers focus too much on expected flows.</p><p>AI can help uncover scenarios humans may overlook, especially for:</p><ul><li>Input combinations</li><li>Data variations</li><li>Retry behaviors</li><li>Unexpected user actions</li><li>Large-scale permutations</li></ul><p>This is especially useful during:</p><ul><li>Regression planning</li><li>Exploratory testing</li><li>Risk analysis</li><li>Requirement review</li></ul><p>AI acts like an additional brainstorming partner.</p><h3>AI Improves Productivity</h3><p>Instead of spending hours writing repetitive scenarios, QA Engineers can:</p><ul><li>Generate draft scenarios quickly</li><li>Refine and prioritize them</li><li>Focus on critical business risks</li><li>Spend more time on exploratory testing</li></ul><p>This shifts QA work from repetitive documentation into higher-value analysis.</p><h3>But AI Still Needs Human Validation</h3><p>AI-generated scenarios are not always correct.</p><p>AI may:</p><ul><li>Miss business context</li><li>Suggest unrealistic cases</li><li>Ignore system limitations</li><li>Produce duplicate scenarios</li><li>Misunderstand requirements</li></ul><p>That is why human review remains essential.</p><p>Experienced QA Engineers still need to:</p><ul><li>Validate relevance</li><li>Prioritize risks</li><li>Adjust based on business impact</li><li>Ensure coverage quality</li></ul><p>AI accelerates the process, but humans provide the judgment.</p><h3>Best Use Cases for AI in Scenario Creation</h3><p>AI is especially helpful for:</p><ul><li>Large applications</li><li>Repetitive feature testing</li><li>Regression preparation</li><li>Requirement analysis</li><li>API testing ideas</li><li>Edge case brainstorming</li></ul><p>It becomes even more powerful when combined with domain knowledge from experienced QA Engineers.</p><h3>The Future of QA Scenario Design</h3><p>In the future, QA Engineers will likely work alongside AI daily.</p><p>Instead of manually writing every scenario from scratch, QA Engineers may become:</p><ul><li>Scenario reviewers</li><li>Risk analysts</li><li>Quality strategists</li><li>AI-assisted testers</li></ul><p>The focus will shift from “writing more test cases” to “creating smarter testing coverage.”</p><h3>Final Thoughts</h3><p>AI is transforming how QA Engineers create test scenarios.</p><p>It helps teams move faster, explore broader coverage, and reduce repetitive work.</p><p>However, effective testing still depends on human understanding, business context, and critical thinking.</p><p>The best QA Engineers will not compete against AI.</p><p>They will learn how to use AI to create better quality, faster than ever before.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e3016cc6f62b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Banking QA Is More Difficult Than Regular App Testing]]></title>
            <link>https://medium.com/@ananur.rani/why-banking-qa-is-more-difficult-than-regular-app-testing-151f18a5e2df?source=rss-e8874f2fff2d------2</link>
            <guid isPermaLink="false">https://medium.com/p/151f18a5e2df</guid>
            <dc:creator><![CDATA[Ana Nur Rani]]></dc:creator>
            <pubDate>Sun, 24 May 2026 12:31:00 GMT</pubDate>
            <atom:updated>2026-05-24T12:31:00.702Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5e3s3sjr2tGGPcD50f1wpg.png" /><figcaption>Banking QA</figcaption></figure><p>Testing a regular application can already be challenging. But testing a banking or fintech application is an entirely different level of responsibility.</p><p>In most apps, a bug may cause inconvenience.</p><p>In banking systems, a bug can cause:</p><ul><li>Financial loss</li><li>Duplicate transactions</li><li>Failed settlements</li><li>Security risks</li><li>Regulatory issues</li><li>Loss of customer trust</li></ul><p>That is why Banking QA requires much more than simply checking whether a feature works.</p><h3>Every Transaction Must Be Accurate</h3><p>In social media or entertainment apps, a minor display issue might be acceptable temporarily.</p><p>In banking applications, even a small calculation mismatch can become a serious incident.</p><p>Imagine:</p><ul><li>A balance was deducted twice</li><li>A delayed transfer status</li><li>A payment marked “successful” but not received</li><li>Incorrect currency conversion</li></ul><p>One tiny defect can affect thousands of users within minutes.</p><p>Accuracy is everything.</p><h3>Banking Systems Are Highly Integrated</h3><p>Most banking applications are connected to many external systems:</p><ul><li>Core banking</li><li>Payment gateways</li><li>E-wallet providers</li><li>QR payment systems</li><li>Fraud detection services</li><li>Third-party APIs</li></ul><p>This means QA Engineers often test across multiple environments and dependencies.</p><p>Sometimes the frontend works perfectly, but the issue actually comes from:</p><ul><li>Callback failures</li><li>Timeout handling</li><li>Queue delays</li><li>Settlement mismatches</li><li>External API instability</li></ul><p>Testing becomes much more complex because the system is rarely standalone.</p><h3>Edge Cases Matter More Than Happy Paths</h3><p>In banking QA, happy path testing is never enough.</p><p>The real challenge comes from edge cases like:</p><ul><li>Duplicate requests</li><li>Retry mechanisms</li><li>Partial transaction failures</li><li>Slow network conditions</li><li>Session expiration during payment</li><li>Reversed transactions</li><li>Currency rounding issues</li></ul><p>Many critical production bugs happen in scenarios that occur only rarely — but when they happen, the impact is huge.</p><h3>Performance and Reliability Are Critical</h3><p>A regular application might survive occasional slowness.</p><p>Banking systems often cannot.</p><p>Users expect:</p><ul><li>Real-time balances</li><li>Fast transfers</li><li>Immediate confirmations</li><li>Stable transaction processing</li></ul><p>Even a few seconds of delay can create panic, duplicate attempts, or customer complaints.</p><p>That is why Banking QA often works closely with:</p><ul><li>Performance testing</li><li>Monitoring systems</li><li>Logging validation</li><li>Transaction tracing</li></ul><h3>Security Is a Constant Concern</h3><p>Banking applications handle extremely sensitive data:</p><ul><li>Personal information</li><li>Account numbers</li><li>Transaction history</li><li>Authentication credentials</li></ul><p>QA Engineers must also think about:</p><ul><li>Authorization</li><li>Data exposure</li><li>Session security</li><li>Access control</li><li>OTP validation</li><li>Encryption behavior</li></ul><p>Security testing becomes part of the quality mindset.</p><h3>Regulations Add Another Layer of Complexity</h3><p>Unlike many consumer apps, banking systems must comply with strict regulations and audit requirements.</p><p>Sometimes a feature is technically correct but still cannot be released because it violates:</p><ul><li>Compliance rules</li><li>Financial regulations</li><li>Internal audit standards</li></ul><p>QA in fintech is not only about software quality — it is also about operational and regulatory confidence.</p><h3>Banking QA Requires a Different Mindset</h3><p>Good Banking QA Engineers do not only test features.</p><p>They think about:</p><ul><li>Risk</li><li>Trust</li><li>Financial impact</li><li>System stability</li><li>Real-world transaction behavior</li></ul><p>They understand that every bug may affect actual money and real customers.</p><p>That responsibility is what makes Banking QA far more demanding than regular application testing.</p><p>That responsibility is what makes Banking QA far more demanding than regular application testing.</p><h3>Final Thoughts</h3><p>Banking QA is challenging because the stakes are higher.</p><p>The systems are more complex, the integrations are deeper, and the consequences of failure are far more serious.</p><p>But that is also what makes it valuable.</p><p>Behind every successful digital payment, transfer, or transaction, there is usually a QA Engineer helping ensure everything works safely, accurately, and reliably.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=151f18a5e2df" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI Won’t Replace QA, But QA Who Use AI Will]]></title>
            <link>https://medium.com/@ananur.rani/ai-wont-replace-qa-but-qa-who-use-ai-will-b23310847896?source=rss-e8874f2fff2d------2</link>
            <guid isPermaLink="false">https://medium.com/p/b23310847896</guid>
            <dc:creator><![CDATA[Ana Nur Rani]]></dc:creator>
            <pubDate>Sat, 23 May 2026 13:05:34 GMT</pubDate>
            <atom:updated>2026-05-23T13:05:34.717Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JBBIWFXeo1tkwODM4Aoz3w.png" /><figcaption>AI VS QA</figcaption></figure><h4>Artificial Intelligence is changing the software industry faster than ever. Developers now use AI to generate code, product teams use AI for analytics, and testers are starting to integrate AI into their daily workflows.</h4><p>This raises one big question: <em>Will AI replace QA Engineers?</em></p><p>The short answer: not entirely.</p><p>But QA Engineers who refuse to adapt to AI may struggle to stay relevant in the future.</p><h3>The Rise of AI in Software Testing</h3><p>AI tools can now:</p><ul><li>Generate test cases automatically</li><li>Create automation scripts</li><li>Detect flaky tests</li><li>Suggest edge cases</li><li>Analyze logs and failures</li><li>Perform self-healing automation</li></ul><p>Tools like Playwright AI, GitHub Copilot, and other AI-assisted testing platforms are helping teams move faster than before.</p><p>For repetitive tasks, AI can significantly improve productivity.</p><h3>What AI Does Better Than Humans</h3><p>AI is extremely good at:</p><ul><li>Repetitive validation</li><li>Large-scale data analysis</li><li>Fast script generation</li><li>Pattern recognition</li><li>Regression coverage</li></ul><p>Instead of spending hours creating basic test scenarios, QA Engineers can now generate initial drafts within minutes.</p><p>This saves time and allows teams to focus on higher-value testing activities.</p><h3>What AI Still Struggles With</h3><p>Despite its advantages, AI still has major limitations.</p><p>AI cannot fully understand:</p><ul><li>Real user behavior</li><li>Business context</li><li>Product intuition</li><li>Emotional user experience</li><li>Ambiguous requirements</li><li>Risk prioritization</li></ul><p>For example, an AI might confirm that a payment flow technically works, but it may fail to identify confusing UX, risky transaction behavior, or business logic inconsistencies.</p><p>This is where human QA remains critical.</p><h3>QA Is Evolving Into Quality Engineering</h3><p>The role of QA is no longer just “finding bugs.”</p><p>Modern QA Engineers are expected to:</p><ul><li>Prevent issues early</li><li>Collaborate with developers</li><li>Understand business impact</li><li>Improve release confidence</li><li>Monitor production quality</li><li>Integrate testing into CI/CD pipelines</li></ul><p>This shift is why many companies now use the term <em>Quality Engineer</em> instead of simply <em>QA Tester</em>.</p><h3>The Real Threat Is Not AI</h3><p>AI itself is not the real threat.</p><p>The real threat is staying static while the industry evolves.</p><p>A QA Engineer who understands:</p><ul><li>AI-assisted testing</li><li>Automation fundamentals</li><li>API testing</li><li>CI/CD</li><li>Risk-based testing</li></ul><p>will likely outperform someone relying only on traditional manual testing.</p><p>AI should be viewed as a productivity partner, not a competitor.</p><h3>Final Thoughts</h3><p>AI will continue transforming software testing, and many repetitive QA activities may become increasingly automated.</p><p>However, software quality is still deeply connected to human judgment, critical thinking, and business understanding.</p><p>QA Engineers are not disappearing.</p><p>The role is simply evolving.</p><p>And in this new era, the most valuable testers will not be the ones competing against AI — but the ones learning how to work alongside it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b23310847896" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beyond Test Cases: How to Prepare for a QA Interview in Banking & Fintech Industry]]></title>
            <link>https://medium.com/@ananur.rani/beyond-test-cases-how-to-prepare-for-a-qa-interview-in-banking-fintech-industry-c665d23495bc?source=rss-e8874f2fff2d------2</link>
            <guid isPermaLink="false">https://medium.com/p/c665d23495bc</guid>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[job-seekers]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[banking]]></category>
            <dc:creator><![CDATA[Ana Nur Rani]]></dc:creator>
            <pubDate>Sat, 16 May 2026 12:55:15 GMT</pubDate>
            <atom:updated>2026-05-16T12:55:15.708Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-nwV-umCPvpxY7sJnpOzOA.png" /></figure><p>Hi, I’m Ana. I currently work as a QA Engineer in Indonesia’s banking industry, focusing on fintech and super app ecosystems. In this article, I want to share some insights from my experience about QA interviews and the skills that are commonly expected in banking technology projects.</p><p><em>first, let’s talk about QA?</em></p><p>Quality Assurance roles in banking and fintech applications are very different from testing regular applications.</p><p>In financial systems, QA Engineers are not only responsible for validating features, but also ensuring transaction accuracy, system reliability, security validation, and smooth user experience. Even a small issue can impact customer trust and business operations.</p><p>From my experience working around fintech and super app ecosystems, I realized that banking QA interviews usually evaluate much more than basic testing knowledge. Interviewers often want to know whether candidates understand business flows, transaction lifecycles, integrations, and real-world risk scenarios.</p><h3>Why QA Is Critical in Banking Applications</h3><p>Banking and fintech applications handle highly sensitive operations such as:</p><ul><li>Money transfers</li><li>QR payments</li><li>Virtual account payments</li><li>Deposits</li><li>Investments</li><li>Account onboarding</li><li>OTP verification</li><li>Transaction history</li><li>Financial reporting</li></ul><p>Because of this complexity, QA Engineers play an important role in maintaining product quality and user trust.</p><p>For example, issues such as:</p><ul><li>duplicate transactions</li><li>incorrect balance updates</li><li>delayed transaction status</li><li>failed payment synchronization</li></ul><p>It can create serious business impact if not properly tested.</p><p>That is why QA interviews in banking companies often focus heavily on analytical thinking and business understanding.</p><h3>What Interviewers Usually Assess</h3><h3>1. Understanding of QA Fundamentals</h3><p>This is still the foundation.</p><p>Interviewers commonly ask about:</p><ul><li>Test scenarios</li><li>Test cases</li><li>Regression testing</li><li>Smoke testing</li><li>Bug lifecycle</li><li>Severity and priority</li><li>UAT support</li><li>Agile/Scrum process</li></ul><p>Example question:</p><blockquote><em>“How do you create test scenarios for a transfer feature?”</em></blockquote><p>A good answer should explain:</p><ul><li>positive scenarios</li><li>negative scenarios</li><li>edge cases</li><li>validation rules</li><li>transaction flow</li></ul><p>Not just “I follow requirements.”</p><h3>2. Understanding of Banking Business Flow</h3><p>This is where fintech QA becomes different.</p><p>Interviewers often expect QA Engineers to understand:</p><ul><li>transaction lifecycle</li><li>payment flow</li><li>OTP verification</li><li>reconciliation</li><li>timeout handling</li><li>transaction status synchronization</li></ul><p>For example, in a transfer feature:</p><ol><li>User inputs transfer details</li><li>System validates account and balance</li><li>OTP verification occurs</li><li>Backend processes transaction</li><li>Transaction history updates</li><li>Notification is sent</li></ol><p>From a QA perspective, all these steps must be validated carefully.</p><h3>3. API and Integration Awareness</h3><p>Modern banking applications rely heavily on APIs and interconnected services.</p><p>Even for Manual QA roles, understanding API behavior is becoming increasingly important.</p><p>Interviewers may ask:</p><ul><li>Have you tested APIs?</li><li>How do you validate backend responses?</li><li>What happens if API response is delayed?</li><li>How do you test integration failures?</li></ul><p>Knowing tools like Postman can become a huge advantage.</p><h3>4. Risk and Edge Case Thinking</h3><p>One thing I learned from fintech projects is that edge cases matter a lot.</p><p>QA Engineers should think beyond normal user behavior.</p><p>Examples:</p><ul><li>unstable internet connection during payment</li><li>duplicate transaction requests</li><li>expired OTP</li><li>interrupted transaction process</li><li>session timeout</li><li>delayed backend response</li></ul><p>These scenarios often become important discussion points during interviews.</p><h3>Common QA Interview Questions in Banking Industry</h3><h3>“How do you prioritize bugs?”</h3><p>A common approach:</p><ul><li>Critical issues affecting transactions or payments become highest priority</li><li>UI cosmetic issues become lower priority</li><li>Business impact and user risk should always be considered</li></ul><h3>“How do you test OTP functionality?”</h3><p>Possible testing scenarios:</p><ul><li>valid OTP</li><li>invalid OTP</li><li>expired OTP</li><li>resend OTP</li><li>multiple failed attempts</li><li>timeout scenarios</li><li>network interruption</li></ul><h3>“How do you perform regression testing?”</h3><p>Regression testing ensures existing features still work after new changes or deployments.</p><p>In banking systems, regression usually focuses heavily on:</p><ul><li>transactions</li><li>login/authentication</li><li>payment flows</li><li>account balances</li><li>notifications</li><li>integrations</li></ul><p>Because these are critical business areas.</p><h3>“What challenges have you faced during testing?”</h3><p>Some realistic examples:</p><ul><li>delayed transaction status updates</li><li>unstable staging environments</li><li>dependency on third-party services</li><li>inconsistent API responses</li><li>synchronization issues between frontend and backend</li></ul><p>Sharing real experiences usually makes answers much stronger.</p><h3>Communication Skills Matter More Than Many People Realize</h3><p>One important thing about QA interviews is communication.</p><p>QA Engineers work closely with:</p><ul><li>developers</li><li>product owners</li><li>business analysts</li><li>support teams</li></ul><p>Because of this, interviewers also evaluate:</p><ul><li>how clearly candidates explain bugs</li><li>how they communicate risks</li><li>how they describe business impact</li><li>how they collaborate during Agile processes</li></ul><p>For example, instead of saying:</p><blockquote><em>“There is a bug in transfer feature.”</em></blockquote><p>A stronger explanation would be:</p><blockquote><em>“I found an issue where transaction status remained pending on the frontend even though backend processing completed successfully. This could potentially confuse users and trigger duplicate transfer attempts.”</em></blockquote><p>This type of explanation shows:</p><ul><li>analytical thinking</li><li>business awareness</li><li>system understanding</li></ul><h3>Understanding Architecture Helps a Lot</h3><p>QA Engineers do not need to become software architects, but understanding basic system architecture can make a huge difference during interviews.</p><p>Many banking and super apps use microservices architecture where:</p><ul><li>payment services</li><li>authentication services</li><li>notification services</li><li>investment modules</li><li>lifestyle services</li></ul><p>operate as separate backend systems connected through APIs.</p><p>Understanding these integrations helps QA Engineers identify:</p><ul><li>dependency risks</li><li>integration failures</li><li>synchronization problems</li><li>transaction inconsistencies</li></ul><p>Even high-level architecture understanding already gives a strong impression during interviews.</p><h3>Tips to Prepare for Banking QA Interviews</h3><h3>Improve Technical Understanding</h3><p>Learn:</p><ul><li>API testing</li><li>SQL basics</li><li>transaction flow validation</li><li>system integrations</li></ul><h3>Understand Business Flow</h3><p>Do not only memorize testing theory.</p><p>Understand:</p><ul><li>how banking transactions work</li><li>how payment systems operate</li><li>how users interact with financial products</li></ul><h3>Practice Communication</h3><p>Try practicing:</p><ul><li>bug explanations</li><li>standup updates</li><li>feature walkthroughs</li><li>interview simulations in English</li></ul><p>Strong communication creates a huge advantage for international opportunities.</p><h3>Learn to Think About Risk</h3><p>Interviewers appreciate QA Engineers who can identify:</p><ul><li>edge cases</li><li>failure scenarios</li><li>business impact</li><li>security risks</li></ul><p>not only happy path testing.</p><h3>Final Thoughts</h3><p>QA interviews in banking and fintech industries are no longer only about executing test cases.</p><p>Companies increasingly look for QA Engineers who understand:</p><ul><li>business processes</li><li>transaction systems</li><li>integrations</li><li>risk scenarios</li><li>user experience</li><li>product quality</li></ul><p>From my experience, combining technical QA skills with business understanding creates much stronger value as a QA professional.</p><p>The more we understand how systems, transactions, and users interact inside a digital product ecosystem, the more effective we become in ensuring software quality.</p><p>I’m currently exploring and sharing more topics around QA engineering, fintech systems, super apps, transaction flows, and software quality practices through my writing journey.</p><p>See you in the next QA and fintech discussion!👋</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c665d23495bc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>