<?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 Yesim Yaren Cilingir  on Medium]]></title>
        <description><![CDATA[Stories by Yesim Yaren Cilingir  on Medium]]></description>
        <link>https://medium.com/@ozturkyesimyaren?source=rss-1c9f4b772e18------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*zWnmSc96nLO4Fv6-wOZ89A@2x.jpeg</url>
            <title>Stories by Yesim Yaren Cilingir  on Medium</title>
            <link>https://medium.com/@ozturkyesimyaren?source=rss-1c9f4b772e18------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 19:04:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ozturkyesimyaren/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[The Secret Behind That Perfect Cash Withdrawal]]></title>
            <link>https://medium.com/@ozturkyesimyaren/the-secret-behind-that-perfect-cash-withdrawal-f0ada24918a6?source=rss-1c9f4b772e18------2</link>
            <guid isPermaLink="false">https://medium.com/p/f0ada24918a6</guid>
            <category><![CDATA[banking]]></category>
            <category><![CDATA[atm]]></category>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[fintech]]></category>
            <dc:creator><![CDATA[Yesim Yaren Cilingir ]]></dc:creator>
            <pubDate>Thu, 24 Jul 2025 19:18:39 GMT</pubDate>
            <atom:updated>2025-07-24T19:18:39.716Z</atom:updated>
            <content:encoded><![CDATA[<h3><em>ATM Testing Through the Eyes of a Software Test Speacialist</em></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/256/1*Tq7S8pQqswgGnGnpmdNjeg@2x.jpeg" /></figure><p>Have you ever wondered how ATMs work or how they’re tested?<br>Today, in this story, I’d like to share some key points about what I do and how we test ATMs.</p><p>Behind every successful cash withdrawal, there is an invisible but critical preparation process. This is the work of a large, dedicated team. Among this big team, let’s talk about the Software Test Specialist who are an important part of that process.</p><p><strong>We quickly notice when something goes wrong, but what about when everything works perfectly? </strong>Every smooth transaction is the result of testing hundreds of scenarios, one by one.</p><p>Let’s take a look behind the scenes together!</p><p><strong>What’s Behind That Familiar Sound?</strong></p><p>You’re standing in front of the ATM, insert your card, enter your PIN, confirm the amount… hear a buzzing, the sound of money being counted, and then the banknotes appear.<br>This process only takes seconds but it may be the result of days of testing. Testing isn’t just about checking if something works. It’s about ensuring safety, accuracy and a good user experience.</p><h4><em>So how do we test?</em></h4><p><strong>General Hardware Tests</strong></p><p>We test physical parts of the ATM,</p><ul><li>Does the card reader take in the card smoothly?</li><li>Does the cash dispenser give the right amount?</li><li>Is the receipt readable?</li></ul><p><strong>Software Tests</strong></p><p>Here are some of the tests we perform,</p><ul><li>Cash withdrawal, deposit, balance inquiry</li><li>Bill payments, QR code transactions, debt payments, etc.</li></ul><p>These aren’t tested just once. We run automation scenarios repeatedly to make sure every function always works correctly and consistently.</p><p><strong>Unusual Situations</strong></p><p>What happens during a power outage?<br>What if the internet connection drops, will the money still come out?<br>What if the money is deducted from the account but not dispensed?</p><p>We test these risky scenarios many times to measure the system’s resilience.</p><p><strong>Real Card, Real Money; Field Testing</strong></p><p>What if a card is pulled out immediately after insertion?<br>Does the ATM block the card after three incorrect PIN attempts?</p><p>We run tests in real environments using real cards and real money to observe unexpected behaviors.</p><p><strong>API Tests</strong><br>We check the data exchange between the ATM and bank systems. If the communication fails, the transaction may stop. Every request-response cycle is carefully tested.</p><p><strong>DB Checks</strong><br>After every transaction, we run queries to ensure the correct records were saved in the system.</p><p><strong>Security</strong></p><ul><li>PIN must be hidden on screen and encrypted over the network</li><li>Sessions must expire after inactivity, and the card should eject</li><li>The system should lock itself and raise alarms in case of physical tampering</li></ul><p>We test all of this to ensure ATMs protect both the system and the user.</p><h4><strong>And Those Banknotes You Hold</strong></h4><p>ATM testing isn’t just about writing code or pressing buttons. It’s a multidisciplinary effort that brings together hardware, software, networks and even user psychology.</p><p>Our goal is always to deliver a system that is as close to perfect and error-free as possible – even though one hundred percent perfection isn’t always achievable.</p><p>It’s important to remember: even if all tests pass successfully, issues can still occur in the live environment. The testing environment doesn’t always fully reflect real-world conditions. User behavior, data variety, system integrations, and unexpected situations can all lead to problems in production.</p><p>That’s why our job as test specialist isn’t just about catching bugs – it’s also about anticipating risks and being prepared for the unexpected.</p><p><em>Delivering reliable, robust systems that never let the user down – that’s what we’re here for.</em></p><p>Thank you so much for taking the time to read my story.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f0ada24918a6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making Invisible Work Visible: The Power of Transparency in Agile Teams]]></title>
            <link>https://medium.com/@ozturkyesimyaren/making-invisible-work-visible-the-power-of-transparency-in-agile-teams-8b1c8dff96dd?source=rss-1c9f4b772e18------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b1c8dff96dd</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[qa-testing]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Yesim Yaren Cilingir ]]></dc:creator>
            <pubDate>Tue, 08 Jul 2025 15:22:55 GMT</pubDate>
            <atom:updated>2025-11-04T06:06:55.785Z</atom:updated>
            <content:encoded><![CDATA[<h3>Making Invisible Work Visible, The Power of Transparency in Agile Teams</h3><blockquote>“Working software over comprehensive documentation.”<br>“Individuals and interactions over processes and tools.”</blockquote><blockquote><em>– Agile Manifesto</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*19cu2ynf4A9IW8GP5g_Vng@2x.jpeg" /></figure><p>Hello everyone,</p><p>Lately I noticed, sprint velocity looked fine and Jira showed progress. But none of the key tests, critical analysis and silent validations are tracked.</p><p>After my observations I questioned: How much of our real work is visible?</p><p>In Agile teams, productivity is often measured by delivered outputs: written code, released features, completed user stories, increasing metrics in dashboards, sprint completion rates, closed Jira tasks, the number of successful CI/CD runs, pull requests deployed to production, or customer-facing new functionalities.</p><p>These are all important indicators. However, the behind-the-scenes efforts that make these visible outcomes possible are just as valuable.</p><p><strong>Testing processes, analysis work, quality control, and preventive measures</strong> are often carried out silently and, as a result, tend to stay in the background easily overlooked.</p><p>During a time when my team was discussing questions like, “How can we improve ourselves, our processes, our communication, and our collaboration models?”, I realized I was hearing similar thoughts from friends working in different teams and companies. Many were experiencing the same kind of invisible work described in this article.</p><p>So instead of keeping these reflections to myself, I decided to compile them and humbly share this technical post. I believe that sharing experiences like this can help us build more transparent and balanced team structures, and prevent a challenge that can otherwise grow over time:</p><p><strong>The perception that a high-effort contributor’s work goes unnoticed.</strong></p><p>When someone’s contributions don’t produce visible outcomes, they may be perceived as having a lighter workload or more free time.</p><h3>Why Does This Perception Arise?</h3><p>The lack of recognition for invisible work is often caused by specific factors:</p><p>• <strong>The nature of some roles is inherently quiet. </strong>Testing, analysis, observation, monitoring, etc., may not create visible deliverables but contribute directly to product quality.</p><p>• <strong>Quiet and well-organized team members. </strong>People who don’t ask for help, work methodically, and don’t externalize their workload are often perceived as “not busy.”</p><p>• <strong>Visibility gaps in Agile processes. </strong>Even when Scrum, Kanban, or hybrid approaches are used, especially supporting or cross-functional tasks are not always fully reflected in backlog items or Jira tasks.</p><p>Activities like refinement, analysis, manual testing, automation infrastructure updates, data preparation, and log analysis are all crucial — but if they’re not shown on the sprint board, they can’t be measured.</p><p>This prevents a clear view of workload distribution and can result in these contributions being overlooked.</p><h3>The Agile Perspective: Transparency, Observation, and Alignment</h3><p>One of the core principles of Agile is transparency.<br>Making all contributions visible is vital for fair work distribution, sustainability, and mutual understanding.</p><p><strong><em>Without transparency:</em></strong></p><p>• Workload may become unbalanced<br>• Motivation and trust may decline<br>• Critical processes may be neglected</p><p><strong><em>With transparency:</em></strong></p><ul><li>Team coordination improves<br>• Contributions are appreciated<br>• A healthy and balanced production environment emerges</li></ul><h3>Practical Actions to Make Invisible Work Visible</h3><p>Here are a few practices that can help highlight invisible contributions:</p><p><strong>• Explicitly mention invisible tasks in daily stand-ups. </strong>Regularly share activities such as testing, validation, and exploratory work.</p><p><strong>• Use metrics and dashboards. </strong>Track test coverage, bug prevention rates, and manual observation outcomes.</p><p><strong>• Include supporting tasks in the backlog. </strong>Documentation, analysis, and research should be planned and visible in sprint boards.</p><p><strong>• Foster a culture of appreciation. </strong>In retrospectives, recognize not only delivered features but also contributions that make the process secure and high-quality.</p><p><strong>• Educate stakeholders. </strong>Explain the value of invisible work and its role in sustainability to product management and leadership.</p><p>High-performing Agile teams are not just agile; they are transparent, balanced, and fully inclusive.</p><p>Making invisible work visible has a direct impact on trust, productivity, and job satisfaction.</p><p>Quiet contributions in areas like testing, analysis, and quality create strategic advantages.</p><blockquote>What matters is not the effort that can’t be shown, but the effort that is made visible.</blockquote><p>Thank you for taking the time to read.</p><p>How do you respond in similar situations? Feel free to share your thoughts, experiences, and suggestions. Let’s advance Agile culture together.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b1c8dff96dd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>