<?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 Jasmine Shany on Medium]]></title>
        <description><![CDATA[Stories by Jasmine Shany on Medium]]></description>
        <link>https://medium.com/@jas123?source=rss-45578cb7be47------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*q-RtXjaABPMVHxiAeBEtOg.png</url>
            <title>Stories by Jasmine Shany on Medium</title>
            <link>https://medium.com/@jas123?source=rss-45578cb7be47------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:27:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jas123/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[Taking control of your professional growth: a personal experience]]></title>
            <link>https://medium.com/@jas123/taking-control-of-your-professional-growth-a-personal-experience-b53cbdfd8890?source=rss-45578cb7be47------2</link>
            <guid isPermaLink="false">https://medium.com/p/b53cbdfd8890</guid>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[career-development]]></category>
            <dc:creator><![CDATA[Jasmine Shany]]></dc:creator>
            <pubDate>Tue, 29 Mar 2022 06:19:18 GMT</pubDate>
            <atom:updated>2022-03-29T06:19:18.311Z</atom:updated>
            <content:encoded><![CDATA[<p>If you are the kind of person that claims taking control of your professional growth, changing careers, and moving up the ladder are easy feats, I would love to draw on your experience.</p><p>For me, my growth journey was and still is a hell of a ride. Not so long ago, I promised myself that I’d go above and beyond to take control of my journey, gain focus and combine my passion and skills to see where this path would take me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*amYgxY9Z0MtAYYJP9QUwLg.png" /></figure><p>As my journey continues, I recently changed my title at work to “Director of Product, R&amp;D Operations.” What exactly does this mean for me? We will get to that, so keep reading.</p><p>My professional career began in the field of Quality. For the past 14 years, I have led teams in the quality assurance departments of various corporations. I have always been passionate about processes, their value, personal growth (for myself and my team), leadership development, and team building.</p><p>At the height of the pandemic two years ago, I joined Diagnostic Robotics, a digital health sector market leader. Even though part of my plans included gaining control of my professional growth, I didn’t know how to go about it. I was certain that it needed to become a priority, though.</p><p>Fortunately, I had <a href="https://medium.com/@goldshmidt">Amit </a><a href="https://medium.com/@goldshmidt?source=user_profile----------------------------------------">Goldshmidt</a> as a manager, a genuine leadership inspirational figure who wasted no time, asked all the right questions, and provided me with much-needed guidance.</p><p>That’s where it all started for me, and I hope my detailed process will help others gain more clarity:</p><p><strong>1.Jot down your dreams — </strong>Start by literally putting pen to paper and listing your professional goals. I focused and tried to be as honest with myself as possible while answering questions such as “What does my dream job look like?”, “What am I truly passionate about?”, What opportunity would I pursue next if there were no limitations?”</p><p>I figured that at the top of my list would be gaining experience in multiple cross-functions, leading significant efforts from ideation to delivery, and working with clients to define customer satisfaction better. This exercise enabled me to organize my dreams by role (Team leader, VP, COO)</p><p><strong>2. Map your skills </strong>— Continue by listing your abilities to determine where you need improvement. Focus on each skill area and need for improvement related to a particular growth path. For example, skills like delegation, motivating others, and team management are paramount for a management path and need to be at the highest levels.</p><p>As for me, once I listed my skills, I ranked my current abilities on a scale of 1–5 and noted what level I thought the skill needed to be at for my chosen path. Your manager should also rank it, but this requires a collaboration based on trust and open communication.</p><p><strong>This is how it looks like</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SK37gJtmdGbG5sVxMN4O0Q.png" /></figure><p><strong>3. Start paving the way — </strong>Once you had completed the daunting task of performing an unbiased self-assessment. You should work closely with your manager to identify opportunities to fill the gaps. Also actively search for opportunities within the company that would correspond to your plans of polishing specific skills listed in your self-assessment and create your own reality.</p><p>That being said, the ride is equally bumpy and exciting. It is important to keep in mind that your skillset is your career capital, so an essential step in gaining control of your career is to seek fulfilling positions that would allow you to put your best assets forward.</p><p><strong>Some simple ground rules that helped me</strong></p><p>● Don’t focus on the title, but rather look at the essence of the role — what will your day-to-day responsibilities be? What experience will you gain? Who is your manager?</p><p>● Allow yourself to fail — the journey of taking control of your career is not easy; you will feel like you’re failing multiple times as you work to improve and focus on your chosen direction. Don’t forget that we learn and improve from every failure. Don’t get discouraged!</p><p>● Engage your manager. Cue them into your plans and request guidance. A true leader will encourage and support you.</p><p>● To the managers out there: dare to listen to your team, try to ask the questions that will give the other side food for thought, and believe in them.</p><p>Paving your professional way is not easy, but it is very satisfying. My current role is challenging and just a stop along my way. It is an operational function in charge of optimizing the intersection of product, engineering, and customer success while supporting the R&amp;D team and their go-to-market counterparts to improve alignment, communication, and processes. This starts to sound more and more like my next post, so make sure to stick around.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b53cbdfd8890" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quality == ?]]></title>
            <link>https://medium.com/ni-tech-talk/quality-f936465b81b7?source=rss-45578cb7be47------2</link>
            <guid isPermaLink="false">https://medium.com/p/f936465b81b7</guid>
            <category><![CDATA[continuous-delivery]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[quality]]></category>
            <dc:creator><![CDATA[Jasmine Shany]]></dc:creator>
            <pubDate>Wed, 01 Jan 2020 18:26:25 GMT</pubDate>
            <atom:updated>2020-01-09T08:12:58.329Z</atom:updated>
            <content:encoded><![CDATA[<h3>Quality == ?</h3><p>Part 2/2 <strong>Ensuring quality in every step in a feature life cycle</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vYOA9_WWWAlEZnLgCFRR2w.jpeg" /></figure><p>In my <a href="https://medium.com/sears-israel/quality-c24ff756a0de">previous post</a>, I took you into the journey of “the true definition of <strong>quality</strong>”- quite a history this word has!</p><p>In this follow-up post, I will take you to a tour of a <strong>feature lifecycle flow</strong> and it’s quality stations. If you wonder why strawberries? I would say strawberries for me are a ‘fine’, high-end fruit and I also happen to love strawberries!</p><p><a href="https://www.websitemagazine.com/blog/business-writing-the-wiifm-principle"><strong>WIIFM</strong></a><strong> you ask?</strong></p><p>In a world of CI/CD product delivery process, in which there is no QA role, we face a new reality. <strong>The responsibility of the product quality shifts from the QA team to the development team:</strong> the developer writes and tests his feature, he owns the feature end-to-end including the quality phase. In order to ensure the best user experience and providing value for our users, we must create layers of defense that will include: strong automation test frameworks, coherent test architecture, monitoring, logs, alerts, anomaly detection, production tests, exploratory tests and any other layer that should raise our confidence.</p><p><strong>It’s a lot…where do I start?</strong></p><p>Quality begins with people. One must have the correct personnel to carry out the job. There are 2 key roles involved:</p><ol><li>FO-”Feature Owner” In the company I work at (<a href="https://www.naturalint.com/jobs/">Natural Intelligence</a>), a developer is called a feature owner. He owns the feature end-to-end, from its technical break down and creation of an HLD (high-level design), until deployment to production and even post-production!</li><li>QDO- ”Quality Domain Owner” (I will probably need to write a separate post on this amazing role). is a dedicated and very professional quality leader who is leading the quality aspects per product domain. His role includes production awareness, test guidelines, tool creation, deep bugs investigation and logs analysis. his goal is to create a “one voice” quality standard, and alignment between all developers and teams in the company.</li></ol><p><strong>Ensuring quality in every step in a feature life cycle</strong></p><p>There are 8 main quality aspects in a feature’s lifecycle. Let’s take a deeper dive into each of these phases.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1whImJRqAlWZomPX7aHfcQ.png" /><figcaption>Feature lifecycle</figcaption></figure><ul><li><strong>Spec</strong>-<strong> </strong>Part of the spec template includes the following elements: Main user flow of the feature, what are the monitors/alerts that are important, (i.e feature using 3rd party API: error handling alerts definitions, fallback experience). It should also include data requirements (if needed a unique data reporting in order to measure the success / KPI of the feature) and performance requirements. Owner: Product manager</li><li><strong>HLD</strong>- (high-level design), is a technical document written by the developer which describes the feature and changes going to be done. it will also include the following: Which new automation tests will be written (unit tests for logic, system test/any integration tests and yes also e2e flow if needed), performance/load tests needed. Owner: FO</li><li><strong>Feature Kickoff</strong>- An important phase, to align all relevant parties. It’s usually a short meeting that the Product, QDO and FO attends. for those who hate meetings (like me), a Slack channel is quite enough. Sync on what the FO is about to do, risks, questions on the spec/HLD. Owner: FO/Product manager</li><li><strong>Development</strong>- FO develops the feature, tests it, creates alerts/logs. In complicated features, QDO writes a quality plan and review it with the team. Owner: FO &amp; QDO</li><li><strong>CR</strong>-<strong> </strong>Stands for<strong> C</strong>ode <strong>R</strong>eview. I recommend creating a code review standard in your company. We are in the process of creating one.</li><li><strong>Master is Always Green</strong>-<strong> </strong>A mindset and an actual thing! Once a developer pushes to master, he should accept full ownership that if his last build broke the master, he should fix it. “You break it, you fix it&quot; rule. This means we should always aim to have a releasable master. Owner: FO</li><li><strong>DR</strong>-<strong> </strong>Stands for<strong> D</strong>esign <strong>R</strong>eview. In UI features I recommend a pixel-perfect review with the designer and go through the feature flow and main resolutions/devices. Owner: FO</li></ul><p><strong>You are ready! Your feature has shipped to PRODUCTION!</strong></p><ul><li>Last but not least, <strong>Post-Production.</strong> For this phase, open your app/site in production (really?? Yes, really☺) and run the main flows of the feature-<strong>review it as a user</strong>. Check for js/server errors, create a logs board if needed, and analytics board to make sure the data reporting (clicks/AB tests split) you reported really works :) Owner: FO</li></ul><p>Don’t panic over the long list. Start with a quality mindset, keep your users in mind, and the rest will follow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2rf9ehymLrZ763EzgD3r7w.png" /><figcaption>Quality aspects cheatsheet</figcaption></figure><p>To sum up- in a world of CI/CD, two roles are changing: A developer becomes a “feature owner” who owns the entire process from design to production, testing and beyond. The QA becomes a “quality domain owner” who leads the quality for the entire domain. There are 8 key elements, which performing them will ensure a viable process, enjoyable product and value to your users. These elements are detailed in the cheat sheet above for you to use.</p><p>If you reached this point, <strong>now</strong> you can indulge yourself with a big bowl of strawberries! :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FH8aPpu8PnboGpNjU4rN0g.jpeg" /><figcaption>Yummy!</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f936465b81b7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ni-tech-talk/quality-f936465b81b7">Quality == ?</a> was originally published in <a href="https://medium.com/ni-tech-talk">NI Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Analytics & QA — Do they go hand in hand?]]></title>
            <link>https://medium.com/sears-israel/analytics-qa-do-they-go-hand-in-hand-6df8284b1f1e?source=rss-45578cb7be47------2</link>
            <guid isPermaLink="false">https://medium.com/p/6df8284b1f1e</guid>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[quality]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Jasmine Shany]]></dc:creator>
            <pubDate>Sun, 03 Jun 2018 09:05:23 GMT</pubDate>
            <atom:updated>2018-06-03T09:05:23.636Z</atom:updated>
            <content:encoded><![CDATA[<p>My short answer will be — Yes! Don’t be lazy…read why :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H-11Dy3jbv6WZkzUbGB0sw.jpeg" /></figure><p>In the past years many companies have moved to work with <a href="https://medium.com/sears-israel/deploy-deliver-7ec1ff078245"><em>continuous development and deployment</em>.</a> In this new environment, dev teams are constantly sprinting to provide a high quality product with added value to increasingly unforgiving users. For QA teams this is quite challenging. Testing in this FAST world and making sure they find the <strong>most valuable </strong>defect as <strong>fast </strong>as they can is no trivial task.</p><p>Testing without a calculated plan can result in testers’ time spent on areas of the product that yield little value and are less used. But it’s possible to significantly reduce the amount of testing you do while maintaining reasonable levels of confidence through regression.</p><h4>How you ask….?</h4><p>When you think of QA, there are couple of topics that come to mind: bugs, automation, testing, production, scale, performance, “fit for the purpose”, regression etc… What about <a href="https://en.wikipedia.org/wiki/Analytics"><em>analytics</em></a>? Is it also one of QA’s topics you would think about?</p><p>QA can use business data to learn about their users’ behavior, patterns, most/least used features, etc., thus able to make data based decisions instead of educated guesses. Analytics can highlight the risky areas, help with focusing your tests efforts, and help with bugs prioritization.</p><p>You can use any analytics <a href="https://contently.com/strategist/2016/08/02/the-top-10-free-content-analytics-tools/"><em>tool </em></a>to extract the information and data on your product. Let’s drill it down a bit…</p><h4>User Data</h4><p>Extracting, analyzing and monitoring user data such as main flows/ site areas, most used/engaged features, which OS/device/browser is common among your users and which page has low/high bounce rate — could even indicate a bug.</p><p>All of the data above and much more can help to prioritize the tests that should be covered as part of regression testing / exploratory testing. Highlighting high risks area and flows indicate broken flows and also indicate potential bugs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e1K1BZwVzqOFV_ByVvROuA.png" /><figcaption>Sample User Behavior Flow Chart</figcaption></figure><h4>User Impact</h4><p>User data can provide a good starting point to prioritize bugs. Meaning, as part of the bug analysis investigation, extract data of how many users experience this bug, encounter this broken flow and percentage of functionality usage of the page( X% of the users who enter the page experience the bug). This data can certainly help the product manager to better handle bug prioritization.</p><h4>Monitoring &amp; Proactive Approach</h4><p>Various tools provide different monitoring alerts, providing crucial insight allowing you to set alerts on main business flows as an additional product safety net aside automation tests. This allows you to control the main business flows such as: number of user registration/login/add to cart clicks or any other business metrics. Once you get an alert on a drop in one of the metrics this will probably indicate a bug in that area (don’t forget to set a threshold to make sure you wont get false positive alerts).</p><blockquote>These tactics change the QA and makes it more proactive. Identifying bugs as soon as they hit production!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/809/1*u4n6F8CbMkJz_pwjeWmPSw.png" /><figcaption>Sample Business Monitor Dashboard</figcaption></figure><h4>Analytics Data can provide fast and accurate answers!</h4><p><em>Next time you open a bug, try asking the hard questions: what is the user impact and exposure rate? How severe is this bug? What can be done to monitor this business flow so we won’t encounter this bug again?</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6df8284b1f1e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sears-israel/analytics-qa-do-they-go-hand-in-hand-6df8284b1f1e">Analytics &amp; QA — Do they go hand in hand?</a> was originally published in <a href="https://medium.com/sears-israel">Sears Israel</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quality == ?]]></title>
            <link>https://medium.com/sears-israel/quality-c24ff756a0de?source=rss-45578cb7be47------2</link>
            <guid isPermaLink="false">https://medium.com/p/c24ff756a0de</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[quality-software]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[quality]]></category>
            <dc:creator><![CDATA[Jasmine Shany]]></dc:creator>
            <pubDate>Thu, 18 Jan 2018 09:28:33 GMT</pubDate>
            <atom:updated>2018-01-18T09:28:33.842Z</atom:updated>
            <content:encoded><![CDATA[<h4>Part 1 / 2</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G5fTdVhIpQkvlSUraC4gBw.jpeg" /></figure><p>A wise man asked me in a middle of a meeting, “what is quality? Or… I will rephrase: what is quality for you?”</p><p>Caught me unprepared :) I went for the more comfortable answers: zero customer complains, zero bugs, meeting the product requirement etc…</p><p>BUT something was missing!</p><p>It reminded me a famous quote from the book “Zen and the Art of Motorcycle Maintenance” by Robert Pirsig:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/582/1*zq7X4SZAFOw-Iz7keTEnKg.png" /></figure><p>After many hours online, reading most of the <a href="http://www.pqm-online.com/assets/files/lib/books/juran.pdf">“Juran’s Quality Handbook”</a> (it’s a really long book :)) &amp; 12 years in the industry working on various products. I can tell that there are many, many definitions of quality! Some are more related to subjective feelings while others to objective facts. Additionally, professionals define it a bit different depends on the company, product and even manager they work with.</p><p>In the following post I will share what I have learned looking up quality and give my personal thoughts.</p><p><strong>It all starts with some history</strong></p><p>One of the leading advocates for quality was <a href="https://en.wikipedia.org/wiki/Philip_B._Crosby"><strong>Philip Crosby</strong></a>. In the 70’s he defined quality as “conformance to requirements.” A product that deviates from specifications is likely to be poorly made and unreliable, providing less satisfaction (poor quality) than one that is property constructed (high quality).</p><blockquote>“quality is free” doing something right and bugs free the first time is cheaper than fixing it later.</blockquote><p>Another approach comes from <a href="http://www.skymark.com/resources/leaders/juran.asp"><strong>Joseph Juran</strong></a>, a quality guru of the 20th century. He defining quality as “fitness for use”:</p><ul><li>features of products which meet customer needs and thereby provide customer satisfaction.</li><li>freedom from deficiencies.</li></ul><p>“An essential requirement of these products is that they meet the needs of those members of society who <strong>will actually use them</strong>. This concept of fitness for use is universal. It applies to all goods and services, without exception.”</p><p>Additional to the above, there are the 5 different perspective defined by <a href="https://de.wikipedia.org/wiki/David_A._Garvin"><strong>David A.Garvin</strong></a>, a Professor of Business Administration at Harvard business school.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*3b5x3C5feG5SrGhjkZUNDg.png" /></figure><p><a href="https://www.istqb.org/">ISTQB </a>finds quality as “The degree to which a component, system or process meets specified requirements and/or user/customer needs and expectations.”</p><p>All theses and some other definitions raised me some questions:</p><ul><li>A software with no defects (I don’t believe this software exists) means the product is quality?</li><li>If a product fits me it means that it fits you as well?</li><li>Will this product fit me in 5/10 years?</li><li>Do we really know our user’s requirements? All users has the same requirements?</li></ul><p><strong>It’s all about the value</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PIhEYuUUZJmqihaS-K-PQQ.jpeg" /></figure><p>I find<strong> Jerry Weinberg’s </strong>definition<strong> </strong>to quality as the most suitable definition:</p><p><em>“Quality is value to some person”[who matters]</em></p><p>Quality goes hand in hand with value, I also believe Value and Quality are in the eye of the beholder. There are many times where I have purchased products that my husband called them a piece of s**t. But for me they were great &amp; very useful. The more he tried to point out the issues/defects/ unnecessarily of them, I found “hacks” &amp; “workarounds”. What we value defines quality or rather defines our tolerance limits for quality.</p><p>While quality is value to some person, that doesn’t mean that we’re trying meeting everyone’s needs &amp; requirements. <a href="http://www.satisfice.com/blog/"><strong>James Bach</strong></a> has added “who matters” to Jerry’s definition. these people are not only the customer or end users. it can also be marketing, other R&amp;D teams or stakeholders.</p><blockquote>Quality is always relative to some person. Whenever someone says something about quality, we should ask who is the person behind the quality statement, and what does the individual value.</blockquote><p>Next post will talk about <em>defining quality in every step of a product lifecycle…</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c24ff756a0de" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sears-israel/quality-c24ff756a0de">Quality == ?</a> was originally published in <a href="https://medium.com/sears-israel">Sears Israel</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Finding the right balance in exploratory testing]]></title>
            <link>https://medium.com/sears-israel/finding-the-right-balance-in-exploratory-testing-80848858ee0?source=rss-45578cb7be47------2</link>
            <guid isPermaLink="false">https://medium.com/p/80848858ee0</guid>
            <category><![CDATA[exploratory-testing]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[agile-testing]]></category>
            <dc:creator><![CDATA[Jasmine Shany]]></dc:creator>
            <pubDate>Sun, 01 Jan 2017 07:26:01 GMT</pubDate>
            <atom:updated>2017-01-01T07:26:01.313Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*lEUeS3TVlneKItNQF3m1Xg.jpeg" /></figure><p>As a tester in an agile environment, exploratory testing is a quite familiar testing approach. When exploring, you execute as soon as you think of a test. This is one of the key attributes that distinguishes exploratory testing from scripted testing. As you explore, you discover how the software operates, you learn about its quirks and peculiarities. You watch carefully, looking for subtle clues about where there might be a nest of bugs lurking.</p><p>Focusing on the most important information to discover, is one of the core skills of a master explorer. It can be quite tricky and difficult. You will need to find the right balance in your exploratory testing between testing “too deep” or “too shallow”.</p><p>Think of it as adding the right amount of sugar to your coffee :) putting too much will make it too sweet, while too little will make it bitter (Yuk!).</p><p><strong>Let’s examine it a bit further…</strong></p><p>What does it actually mean testing “too deep”? You will find yourself raising bugs which are not “user focused”, many of them will be rejected by the product owner. Also, when you share your testing scenarios, your team will raise questions such as: “Why are you so focusing on that area? We have a great amount of automation tests coverage at that specific part, why don’t you put your effort in…”</p><p>Going “too shallow” is almost as letting your end user test for you, users don’t compromise on quality. They don’t care how many tests you ran on your application, they care about the product quality and that it answers their needs. You will also have many “escaped defects” originated from stakeholders, end users or from the company employees themselves. Your team might be wondering about the domain quality and might find themselves constantly adding scope to your tests scenarios.</p><p><strong>Two Key Aspects</strong></p><p>As I see it, there are 2 key indicators that can help you understand your position on the scale between deep testing and shallow testing:</p><p><em>Team feedback</em></p><p>By team I mean, product owners, developers and other QA partners that provide a constant feedback to your work. They are the ones that work closely to you and to the product, try to be open minded as you can to their advices. Their inputs are priceless and invaluable!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/362/1*AHKfoM0WpnO7IOrWEYzylQ.jpeg" /></figure><p><em>Production Status</em></p><p>Feel &amp; know production quality status at any given time! Receiving many bugs from support team or from the end user, bugs you are not aware of, this means you had been testing too shallow. On the other hand, focusing on rare cases and getting your bugs pushed pack, might tell that you’ve tested too deep.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/362/1*89U_wpmOz6tYLNraDPT5LA.jpeg" /></figure><p><strong>Balanced vs Edge Cases</strong></p><p>Keeping it in the balanced point is possible but could also be risky. We tend to get used to it and might miss trying new testing approaches such as: Using testing personas, analyzing the data analytics and following the new user flows (since we are living in an agile environment — this can constantly change). Also, we might take testing on different platforms (IPad, mobile web, etc.) too obvious.</p><p>In some situations, we do swing between both sides: big new features, code refactoring or a huge effect on another site areas, can cause you to test too deeply. While, starting a new project and you are not so familiar with the business requirements, the exploratory testing world is new to you or you are just having a relaxed sprint with no big changes can cause you to test too shallow.</p><p><strong>Guidelines</strong></p><p>Consider using these guidelines next time to figure out when you’ve done enough exploration in a given area:</p><ul><li>Your exploration has answered all the open questions and there are no unknowns for you.</li><li>You are not learning anything new. You have characterized the capabilities, limitations, and risks of the existing implementation. As a result, you feel like you are dealing with a known quantity with no more surprises to be uncovered, at least for now.</li><li>More information will not change anything. You could gather more information, but there is no point.</li><li>Focus your exploratory testing by using personas, testing tours, heuristics, user journeys or session-based test management. What you learn will help your team improve quality, not only in the impending release, but as the product evolves in the future.</li></ul><p>Thanks,</p><p>Jasmine Shany.</p><p><strong>3 highly recommended books:</strong></p><ul><li><a href="https://www.amazon.com/More-Agile-Testing-Addison-Wesley-Signature/dp/0321967054">More Agile Testing: Learning Journeys for the Whole Team</a> by <a href="https://www.safaribooksonline.com/search/?query=author%3A%22Lisa%20Crispin%22&amp;sort=relevance&amp;highlight=true">Lisa Crispin</a>, <a href="https://www.safaribooksonline.com/search/?query=author%3A%22Janet%20Gregory%22&amp;sort=relevance&amp;highlight=true">Janet Gregory</a></li><li><a href="https://www.amazon.com/Explore-Increase-Confidence-Exploratory-Testing/dp/1937785025/ref=sr_1_fkmr0_1?s=books&amp;ie=UTF8&amp;qid=1483255307&amp;sr=1-1-fkmr0&amp;keywords=Explore+it%21+By+Elizabeth+Hendrickson">Explore it!</a> By Elizabeth Hendrickson</li><li><a href="https://www.amazon.com/Lessons-Learned-Software-Testing-Context-Driven/dp/0471081124">Lessons Learned in Software Testing: A Context-Driven Approach</a> by <a href="https://www.safaribooksonline.com/search/?query=author%3A%22Bret%20Pettichord%22&amp;sort=relevance&amp;highlight=true">Bret Pettichord</a>, <a href="https://www.safaribooksonline.com/search/?query=author%3A%22James%20Bach%22&amp;sort=relevance&amp;highlight=true">James Bach</a>, <a href="https://www.safaribooksonline.com/search/?query=author%3A%22Cem%20Kaner%22&amp;sort=relevance&amp;highlight=true">Cem Kaner</a>.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80848858ee0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sears-israel/finding-the-right-balance-in-exploratory-testing-80848858ee0">Finding the right balance in exploratory testing</a> was originally published in <a href="https://medium.com/sears-israel">Sears Israel</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>