
<p>Software testing is the process of evaluating and confirming a software program to ensure it functions as intended. It is designed to ensure that a program works as intended and to discover flaws before it is used. There are two main methods for testing software,- Negative and Positive Testing.</p>



<p>In this article, we will clearly distinguish between these two tests with examples to help you write good test cases for your software programs.</p>



<div id="toc_container" class="no_bullets"><p class="toc_title">Table Of Contents</p><ul class="toc_list"><li><a href="#Difference_Between_Negative_and_Positive_Testing"><span class="toc_number toc_depth_1">1</span> Difference Between Negative and Positive Testing</a></li><li><a href="#Negative_vs_Positive_Testing_Examples_of_Test_Scenarios"><span class="toc_number toc_depth_1">2</span> Negative vs Positive Testing – Examples of Test Scenarios</a></li><li><a href="#Negative_vs_Positive_Testing"><span class="toc_number toc_depth_1">3</span> Negative vs Positive Testing</a></li><li><a href="#Positive_Testing_vs_Negative_Testing-_Similarities"><span class="toc_number toc_depth_1">4</span> Positive Testing vs Negative Testing- Similarities</a></li><li><a href="#Conclusion"><span class="toc_number toc_depth_1">5</span> Conclusion</a></li></ul></div>
<h2 class="wp-block-heading" id="difference-between-negative-and-positive-testing"><span id="Difference_Between_Negative_and_Positive_Testing">Difference Between Negative and Positive Testing</span></h2>



<p>Positive testing ensures that software performs as it is expected to. When writing test cases for positive testing, only legitimate (valid) inputs are provided as inputs.&nbsp;</p>



<p>In Negative testing, a software program is evaluated against false or incorrect data. This testing is also known as error path testing or failure.</p>



<figure class="wp-block-table aligncenter"><table><tbody><tr><td>Read More on <a href="https://testsigma.com/blog/negative-testing/" target="_blank" rel="noreferrer noopener">Negative Testing</a></td></tr></tbody></table></figure>



<h2 class="wp-block-heading" id="negative-vs-positive-testing-examples-of-test-scenarios"><span id="Negative_vs_Positive_Testing_Examples_of_Test_Scenarios">Negative vs Positive Testing – Examples of Test Scenarios</span></h2>



<p>Let’s test a software program with a Password text box field allowing users to enter passwords between 8 and 15 alphanumeric characters.</p>



<p>See the table below for various<a href="https://testsigma.com/guides/test-scenario/" target="_blank" rel="noreferrer noopener"> test scenario</a> examples.</p>



<figure class="wp-block-table"><table><tbody><tr><td><strong>Positive Test Scenarios</strong></td><td><strong>Negative Test Scenarios</strong></td></tr><tr><td>The Password text box should allow 8 characters of input.</td><td>The Password text box should throw an error or should not be accepted when less than 8 characters are entered.</td></tr><tr><td>The Password text box should allow 15 characters of input.</td><td>The password text box should throw an error or should not be accepted when more than 15 characters are entered.</td></tr><tr><td>Any values between 8 and 15 characters long should be accepted by the Password text box.</td><td>The password text box should not accept special characters as input</td></tr><tr><td>It should accept any combination of letters and numbers in the Password text box.</td><td>The password text box should not accept a combination of numbers only or a combination of letters only.</td></tr></tbody></table></figure>



<h2 class="wp-block-heading" id="negative-vs-positive-testing"><span id="Negative_vs_Positive_Testing">Negative vs Positive Testing</span></h2>



<p id="in-this-session-let-us-discuss-some-key-differences">In this session, let us discuss some key differences.<br>&nbsp;</p>



<h2 class="wp-block-heading"><img loading="lazy" decoding="async" alt="Positive and negative testing flow chart" src="https://lh7-us.googleusercontent.com/docsz/AD_4nXceHutfkGRVX5e-DyT8loU34BcymsmcTD_wTDhzOD22h-eL_SaEJ5ZhX3kf255cdfgXrO10Yk_We0j2BnJ1BHs3qLdkQ9YMQH8Bta50HjF1oHvGeSzYW3xTgt5M3YPRcWpJabYnEEPYmdXx9-s0W9TEEQw2?key=EFDOdEb5zUls68Ysu_lSdQ" width="500" height="333"></h2>



<figure class="wp-block-table"><table><tbody><tr><td><strong>Positive Testing</strong></td><td><strong>Negative Testing</strong></td></tr><tr><td>This testing examines a software program’s response with the help of a valid input data set.</td><td>This testing means checking the software program’s response using the invalid/incorrect input data set.</td></tr><tr><td>Positive testing is not a guarantee of high-quality software.</td><td>It ensures that the software product is of high quality.</td></tr><tr><td>Positive testing is executed quickly.</td><td>It takes more time to execute compared to positive testing.</td></tr><tr><td>Positive testing is used consistently to validate the set of test cases that are currently available.</td><td>It is used consistently to break the software program (product) with an unidentified set of test cases we will use.</td></tr><tr><td>Positive testing’s primary goal is to ensure that the <a href="https://www.geeksforgeeks.org/what-is-application-software/" target="_blank" rel="noreferrer noopener">software application </a>consistently complies with the developer’s software requirements specifications (SRS)</td><td>This testing’s primary goal is to evaluate a software program’s consistency in the face of erroneous validation data sets.</td></tr><tr><td>Positive testing does not cover all possible scenarios.</td><td>It encompasses all possible scenarios.&nbsp;</td></tr><tr><td>It is a process where the program is validated against a reliable input data set.</td><td>It is a process where the program is validated against the invalid input data set.</td></tr><tr><td>Positive testing has less impact comparatively.</td><td>It is more crucial and significant than Positive testing.</td></tr><tr><td>Positive testing can be implemented on all kinds of applications.</td><td>It can also be performed on all kinds of applications.</td></tr><tr><td>Someone with less knowledge can carry out the positive testing.</td><td>Professional software testers mainly use this testing.</td></tr><tr><td>It makes sure that the software program meets the required standard.</td><td>It makes sure the software works even if it meets unexpected situations.</td></tr><tr><td>Positive testing is implemented only for the predicted conditions.</td><td>It ensures that the software works for conditions that are tough predict but can happen in real life.</td></tr></tbody></table></figure>



<p>These two tests are two opposing test methods—as the name suggests—but they are also very effective at producing high-quality and bug-free software in the end.</p>



<h2 class="wp-block-heading" id="positive-testing-vs-negative-testing-similarities"><span id="Positive_Testing_vs_Negative_Testing-_Similarities">Positive Testing vs Negative Testing- Similarities</span></h2>



<p>Both are important parts of a whole software examination. Even though they have different priorities, both are similar in some major aspects and should be done together to make strong and easy-to-use software at the end.&nbsp;</p>



<p>Let&#8217;s take a look at these two testing techniques and see where they meet.</p>



<p><strong>Commonalities:</strong></p>



<p><strong>Purpose</strong>: Both negative as well as positive testing share the same goal — to catch defects, ensuring better quality of the software system.</p>



<p><strong>Life Cycle Integration</strong> is possible for them to be integrated throughout the software development life cycle (SDLC), from early requirement stages to post-release maintenance.</p>



<p><strong>Documentation</strong>: Both require clear documentation of test cases, expected results and identified bugs.</p>



<p><strong>Test Case Design</strong>: Both involve designing <a href="https://testsigma.com/guides/what-is-test-case/" target="_blank" rel="noreferrer noopener">test cases</a> with specific inputs and expected outcomes.</p>



<p><strong>Positive Testing </strong>(Happy Path Testing) emphasizes the verification that the software functions as intended under normal conditions with valid inputs.</p>



<p>There is a difference between doing negative and positive testing, which are based on the idea that they supply invalid or unexpected inputs deliberately. This helps identify any error, crash or security issues that would occur as a result.&nbsp;</p>



<p>You can read details on <a href="https://testsigma.com/blog/negative-testing/" target="_blank" rel="noreferrer noopener">negative testing</a> </p>



<p>The approach to testing is the following:</p>



<p><strong>Testing boundary values</strong> (for example, in a field expecting a small integer, you are expected to put down a very large number), <strong>invalid data formats and situations of error</strong>, which is not described explicitly in documentation requirements. For example, test that inputting special characters or overreaching character limit in a username field brings about an error and check if the application handles it properly.</p>



<p><strong>Balancing Negative with Positive Testing:</strong>&nbsp;</p>



<p>In the context of the project phase and risk assessment, both strategies hold value — though the weightage accorded to each can differ. For instance, during the early stages positive testing might take precedence as a means of confirming core functionality.&nbsp;</p>



<p>However, as development evolves, negative testing gains more importance: it helps unearth those elusive edge cases which may pose security threats later down the line.</p>



<p><strong>Additional Resources:</strong></p>



<p>This blog post from Testsigma provides a more detailed explanation of <a href="https://testsigma.com/blog/negative-testing/" target="_blank" rel="noreferrer noopener">negative testing</a> and its various techniques.</p>



<figure class="wp-block-table aligncenter"><table><tbody><tr><td>Read More &#8211; <a href="https://testsigma.com/blog/the-different-software-testing-types-explained/" target="_blank" rel="noreferrer noopener">The Different Software Testing Types Explained</a></td></tr></tbody></table></figure>



<h2 class="wp-block-heading" id="conclusion"><span id="Conclusion">Conclusion</span></h2>



<p>Negative and Positive testing go hand in hand and yet when used effectively, both methods can enhance software quality to a great extent.&nbsp;</p>



<p>It is important for testers to be aware of the advantages and limitations of both approaches so that they are able to develop a thorough testing strategy that ensures user satisfaction throughout the use of the product as well as a strong final output from development.</p>



<div class="cta-banner-v2">
<div class="title-with-description ">
<p class="title">Explore Testsigma, a low code test automation tool, to automate your end-to-end UI tests for web, mobile, desktop and APIs, from the same place, 10x faster.</p>
</div>
<a href="https://testsigma.com/signup" target="_blank" class="cta-btn-v1" rel="noopener">Start here</a>
</div>


What is positive and negative testing scenarios

Negative Testing vs Positive Testing – Top Key Differences

The Most Useful 16 Chrome Extensions for Web Developers


<p>The key differentiator that distinguishes good software from outstanding software is the user experience. Software testers should go beyond just checking the functionality of the product.<strong> </strong>Software<strong> </strong>Testing is one of those fields where the more you know the better it is. Testers need to be generalists to be effective at work, someone with broad knowledge across many topics and expertise in a few.&nbsp;</p>



<p id="h-user-experience-is-not-the-only-responsibility-of-the-ux-team-as-a-tester-you-use-the-software-more-frequently-than-anyone-else-on-the-team-you-can-add-significant-value-by-identifying-features-that-compromise-the-user-experience-ux-as-a-tester-quality-engineer-you-are-in-a-great-position-to-evaluate-the-ux-of-the-software-right-from-the-earliest-stages-of-software-development">User experience is not the only responsibility of the UX team. As a tester, you use the software more frequently than anyone else on the team. You can add significant value by identifying features that compromise the User Experience (UX). For instance, if you notice that users struggle to <a href="https://picsart.com/ai-image-extender/" target="_blank" rel="noreferrer noopener">expand images</a> for better visibility or to access key details, you should flag this as a potential UX issue.</p>



<p>I discuss some fascinating real-world examples of poor UX and how they affected me in this two-part article. These examples will teach you a few UX principles that you can apply in your everyday testing. So let&#8217;s get started.</p>



<div id="toc_container" class="no_bullets"><p class="toc_title">Table Of Contents</p><ul class="toc_list"><li><a href="#WHAT_DID_A_TEA_CUP_TEACH_ME_ABOUT_USER_EXPERIENCE"><span class="toc_number toc_depth_1">1</span> WHAT DID A TEA CUP TEACH ME ABOUT USER EXPERIENCE?</a></li><li><a href="#LESSON_1_8211_DO_NOT_COMPROMISE_ON_FUNCTIONALITY_FOR_AESTHETICSnbsp"><span class="toc_number toc_depth_1">2</span> LESSON 1 &#8211; DO NOT COMPROMISE ON FUNCTIONALITY FOR AESTHETICS.&nbsp;</a></li><li><a href="#HOW_POOR_DESIGN_RUINED_MY_MOVIE_EXPERIENCE"><span class="toc_number toc_depth_1">3</span> HOW POOR DESIGN RUINED MY MOVIE EXPERIENCE</a></li><li><a href="#LESSON_2_8211_SIZE_MATTERS_IN_THE_VISUAL_HIERARCHYnbsp"><span class="toc_number toc_depth_1">4</span> LESSON 2 &#8211; SIZE MATTERS IN THE VISUAL HIERARCHY&nbsp;</a></li><li><a href="#LESSON_3_8211_MATCH_BETWEEN_THE_SYSTEM_AND_THE_REAL_WORLDnbsp"><span class="toc_number toc_depth_1">5</span> LESSON 3 &#8211; MATCH BETWEEN THE SYSTEM AND THE REAL WORLD&nbsp;</a></li><li><a href="#CONCLUSION"><span class="toc_number toc_depth_1">6</span> CONCLUSION</a></li></ul></div>
<h2 class="wp-block-heading" id="what-did-a-tea-cup-teach-me-about-user-experience"><span id="WHAT_DID_A_TEA_CUP_TEACH_ME_ABOUT_USER_EXPERIENCE"><strong>WHAT DID A TEA CUP TEACH ME ABOUT USER EXPERIENCE?</strong></span></h2>



<p>There&#8217;s nothing like a hot cup of tea to lift your spirits and warm your heart when you&#8217;re having a rough day. In my hometown, I visited a popular cafe known for its wide selection of teas. The cafe served tea in a cup that looked absolutely stunning and classy. However, I was unable to enjoy my tea as it was difficult to grip the handle of the cup due to its poor design. </p>



<p><p style="padding-bottom: 30px">The handle had no slit to grab the mug to provide a secure grip. Because the cup was heavier than normal, it was even more inconvenient to hold it with hot tea. Because I was afraid of dropping the teacup, I had to remain cautious at all times. Furthermore, the cup&#8217;s design is not ideal for older people with hand tremors or individuals with reduced strength or flexibility in their hands.&nbsp;</p></p>



<div class="wp-block-image"><figure class="aligncenter is-resized"><img loading="lazy" decoding="async" src="https://s3.us-east-1.amazonaws.com/blog-assets-production.testsigma.com/blogs/wp-content/uploads/migrated_images/kOeHXAcBhKFN8gf5wZpqI8mMssJgKeuTp37lQfsyz3QNVrsIKXEMbS0Y7m2qTAlnQVh8pROLIlxQm8YQVRtD8lL121fISspBVzQow7NjS01Q1br9KHaltr-IqFuNYaOroQv9VMc1sqPkFbuJZVPwlmc_1748948775.png" alt="WHAT DID A TEA CUP TEACH ME ABOUT USER EXPERIENCE? 1" width="400" height="400"/></figure></div>



<p><p style="padding-top: 30px">A good design should support the user&#8217;s in completing their primary goals. In this case, although the cup looks appealing, it is compromising usability and accessibility. This is a classic example of what can happen when you prioritize aesthetics over functionality and simplicity.</p></p>



<p><p style="padding-bottom: 30px">This cup reminded me of&nbsp; ‘Coffeepot for Masochists’. Don Norman&#8217;s incredible book &#8220;The Design of Everyday Things&#8221; mentions it and uses it as the book&#8217;s cover image. ‘Coffeepot for Masochists’ is the most famous item in Jacques Carelman’s &#8216;Catalogue of unfindable things’, which contains delightful examples of everyday things that are deliberately unworkable.</p></p>



<div class="wp-block-image"><figure class="aligncenter is-resized"><img loading="lazy" decoding="async" src="https://s3.us-east-1.amazonaws.com/blog-assets-production.testsigma.com/blogs/wp-content/uploads/migrated_images/zpNsnKHVmEg4sJj1s2DBBs5CsSS3ulfx3f1L3w8y4-ZTtfvJCFjp89lKAOKwSCVLZr3dYOz8cutFKBR7UMWlPsVdLbXptRMU9_gM1JbDsoWs4aswo8_adTqHt6hb_OB39aYB0o3gtCPLuDSqEeIeajQ_1748948768.png" alt="WHAT DID A TEA CUP TEACH ME ABOUT USER EXPERIENCE? 2" width="300" height="400"/></figure></div>



<h2 class="wp-block-heading" id="h-lesson-1-do-not-compromise-on-functionality-for-aesthetics"><span id="LESSON_1_8211_DO_NOT_COMPROMISE_ON_FUNCTIONALITY_FOR_AESTHETICSnbsp"><strong>LESSON 1 &#8211; DO NOT COMPROMISE ON FUNCTIONALITY FOR AESTHETICS.&nbsp;</strong></span></h2>



<div class="wp-block-image"><figure class="aligncenter is-resized"><img loading="lazy" decoding="async" src="https://s3.us-east-1.amazonaws.com/blog-assets-production.testsigma.com/blogs/wp-content/uploads/migrated_images/Lz-3AUiPkruE-jrg6j7i6XZy_ENMXq3Lf4s4Z-rotxpD_kYEUi7IQ5J9AS8OVATwJJKts_o5VJ1YnegJnLEzvaPCCZqPz_MeNwPNgneaMDYQEFk9ti6I2CoA7iy9ntFPYMZ6Hlrg08x5mwx5jCcsDvE_1748948781.png" alt=" DO NOT COMPROMISE ON FUNCTIONALITY FOR AESTHETICS." width="400" height="400"/><figcaption>Graphic by Regex SEO</figcaption></figure></div>



<p><p style="padding-top: 30px">Many people believe that design makes software look visually pleasing. The visual appeal of your application can help you stand out from the rest of your competition. But you may be making the same mistake that the cup designer made. We all adore eye-catching interactive websites. However, the most important aspect of a usable design is <strong>Functionality</strong>. Always put the user at the center of everything that you do.</p></p>



<p><p style="padding-top: 10px">Think,</p></p>



<p>Is your product choosing Visuals Over Functionality?&nbsp;</p>



<p>Is focusing on flashy interfaces over interactions?&nbsp;</p>



<p><p style="padding-top: 10px">As a tester, ensure that the products you work on consider usability and accessibility in the design to provide the best user experiences. I don&#8217;t mean to imply that aesthetics are not important. Users expect both beauty and function from your application. Help your team to strike the right balance between aesthetics and functionality.&nbsp;</p></p>



<h2 class="wp-block-heading" id="how-poor-design-ruined-my-movie-experience"><span id="HOW_POOR_DESIGN_RUINED_MY_MOVIE_EXPERIENCE"><strong>HOW POOR DESIGN RUINED MY MOVIE EXPERIENCE</strong></span></h2>



<p>One of the best ways to spend quality time with your family is to watch a good movie while enjoying a large bowl of popcorn. ​ On a Saturday, I decided to take my wife to the movies. Unfortunately, we were late that day and had to rush into the theatre to make it on time. I had booked the tickets via a popular online platform. </p>



<p>I pulled out my phone and found the m-ticket(digital ticket) in the bookings section of the mobile app. We rushed to our screen and found our seats. We watched the movie for around 15 minutes. We couldn&#8217;t figure out anything that was going on in the movie. </p>



<p>I realized something was wrong. I soon figured out that I had entered the wrong room/screen, and unfortunately, the same movie was playing in the second half, following the intermission.&nbsp;</p>



<p><p style="padding-bottom: 30px">We had entered Screen 2 instead of Screen 4. We then had to rush back to screen 4. I not only missed the first crucial 30 minutes of the movie, but I also had to deal with an angry wife.</p></p>



<div class="wp-block-image"><figure class="aligncenter is-resized"><img loading="lazy" decoding="async" src="https://s3.us-east-1.amazonaws.com/blog-assets-production.testsigma.com/blogs/wp-content/uploads/migrated_images/xASGeddjZjShuxyTyE-ikzNe3WbnRmyioHrbaFHcFdIN6ga-QVQfdLxZOlz6yi4aKm9DSptCyyiXW9mN6tPWgz6RTMd1CDsLAemkNYzGTgAgd44-QMTszCOeqXrOrjQb8G0wFpcoxSJpUAy6KIYKAnM_1748948763.png" alt="HOW POOR DESIGN RUINED MY MOVIE EXPERIENCE" width="400" height="400"/></figure></div>



<p><p style="padding-top: 30px">In the rush and excitement of making it on time, I misunderstood the number 2 on the ticket for the screen number, which in fact, was the number of tickets purchased. I know I made a mistake. Everyone makes mistakes under pressure or excitement or when you rush.</p></p>



<h2 class="wp-block-heading" id="lesson-2-size-matters-in-the-visual-hierarchy"><span id="LESSON_2_8211_SIZE_MATTERS_IN_THE_VISUAL_HIERARCHYnbsp"><strong>LESSON 2 &#8211; SIZE MATTERS IN THE VISUAL HIERARCHY&nbsp;</strong></span></h2>



<p><p style="padding-bottom: 30px">The biggest text in the m-ticket is the number ‘2’, which is the number of tickets. I know I bought two tickets, and that is not a piece of helpful information for me. Unless the designers didn&#8217;t design this for the person who checks tickets at the entrance.</p></p>



<div class="wp-block-image"><figure class="aligncenter is-resized"><img loading="lazy" decoding="async" src="https://s3.us-east-1.amazonaws.com/blog-assets-production.testsigma.com/blogs/wp-content/uploads/migrated_images/dPARTdNmDsj9pAwgZNsBeYOgC2fLbFIX0xMeLpx5eni8xdECInfUuVdwbesA4-jwY0Xx4BGdmKkn6UYWwbEiiev191qlM-8ewaDT3_JmOXRv8l2Cz1WL1OGVSjbIdqWKC-rx9OAxXhY7phizqlzQYVI_1748948773.png" alt="SIZE MATTERS IN THE VISUAL HIERARCHY" width="400" height="400"/></figure></div>



<p><p style="padding-top: 30px">The positioning of elements according to their significance is known as the visual hierarchy in the design. Without a visual hierarchy, users can be overwhelmed and therefore fail to grasp anything.</p></p>



<p>Larger elements on the screen will always catch the eye of a viewer. So the most important piece of information should take precedence in the visual hierarchy. When it comes to movie tickets, the most crucial information is the date, time, screen, and seat number. So these details should be bigger and the first thing you should notice.&nbsp;</p>



<p>When your design has a poor visual hierarchy, users are confused, uncertain about where to look, or even misguided.&nbsp;</p>



<p><p style="padding-top: 10px;padding-bottom: 10px">While testing your software, ask yourself these questions:</p></p>



<ul class="list_style_disc wp-block-list"><li>What is the first thing you see on your application? Where does the eye naturally go?</li><li>What actions do we want our users to take? Are we able to draw their attention to that place?</li><li>Is the visual hierarchy guiding them through a journey we want them to?</li></ul>



<p><p style="padding-top: 10px">As a tester, always keep the audience&#8217;s needs in mind and help create designs that will have the desired impact.</p></p>



<p><p style="padding-bottom: 30px">Poor design can have serious consequences. Remember how Steve Harvey announced the wrong Miss Universe on stage?&nbsp; It is the design of the announcement card that IS to blame. Modern-day users often suffer from information overload.&nbsp; A thoughtful design should prevent users from making mistakes.</p></p>



<div class="wp-block-image"><figure class="aligncenter is-resized"><img loading="lazy" decoding="async" src="https://s3.us-east-1.amazonaws.com/blog-assets-production.testsigma.com/blogs/wp-content/uploads/migrated_images/cwqnLVmLlIizriOfvDPtKuMAS0g5s0rcxzK1Dni0K5iD-5HjV9USI78LLcRTGmcnzRnZYdlq-NHmfwJk_Xx9UM84ceAzxZWVCdnHcgLtBI7aZ4mYjeJQowQBbbbRdnNMpw83fb_M3FmfEKJkJJEjt58_1748948766.jpg" alt="poor design" width="400" height="400"/><figcaption>Learn more about <a href="https://medium.com/@Ktomasso/how-bad-design-ruined-miss-universe-afd9a3d40993" target="_blank" rel="noreferrer noopener">how a bad design ruined Miss Universe</a>.</figcaption></figure></div>



<h2 class="wp-block-heading" id="lesson-3-match-between-the-system-and-the-real-world"><span id="LESSON_3_8211_MATCH_BETWEEN_THE_SYSTEM_AND_THE_REAL_WORLDnbsp"><strong>LESSON 3 &#8211; MATCH BETWEEN THE SYSTEM AND THE REAL WORLD&nbsp;</strong></span></h2>



<p><a href="https://www.nngroup.com/" target="_blank" rel="noreferrer noopener">Jakob Nielsen&#8217;s</a> second Usability heuristics discusses the “Match between system and real-world.” The heuristic states, &#8220;The design should speak the users&#8217; language. Use words, phrases, and concepts familiar to the user”. </p>



<p><p style="padding-bottom: 30px">The designs should follow real-world conventions, making information appear in a more natural and logical order. It is in our nature to seek familiarity. We create mental models of systems work based on past experiences with real-world objects. As a result, we also bring those interpretations into the digital world.&nbsp;</p></p>



<div class="wp-block-image"><figure class="aligncenter is-resized"><img loading="lazy" decoding="async" src="https://s3.us-east-1.amazonaws.com/blog-assets-production.testsigma.com/blogs/wp-content/uploads/migrated_images/20hrbZQQTRSteW3Umqd71nHDcwicBxaeT-RtSEYCjiE2YizZkeC_n58fb9sUrMRST6LrYlmnPdZBLrmctgP-ybnrEdrj7KdUbIjm_g8DShEUdOL0yShPYm4idp78zOms8ptHT1Wtrv1JhyXZV8cetj4_1748948777.jpg" alt=" MATCH BETWEEN THE SYSTEM AND THE REAL WORLD 1" width="400" height="400"/></figure></div>



<div class="wp-block-image"><figure class="aligncenter is-resized"><img loading="lazy" decoding="async" src="https://s3.us-east-1.amazonaws.com/blog-assets-production.testsigma.com/blogs/wp-content/uploads/migrated_images/FJjTxYHG4LM7MEv35FeWzBLHh-hOHPmmHWmMxRthWrCFx80f6wrUqDERdwCq1mp_kZ0jOoKCxLkkecuAI3z-O_6NkMk_juyg4guhSkD-nm-BgbYBjlX4S9GlWkFIVFd6D6-mVWmKfxn0KkqTbFQaKrw_1748948770.png" alt=" MATCH BETWEEN THE SYSTEM AND THE REAL WORLD 2" width="400" height="400"/></figure></div>



<p style="padding-top: 30px">Almost every software you use today uses this principle. For example, we&#8217;re all familiar with the trash can, so when we see a similar trash bin icon in the user interface, we know we can drag a file to delete. Compass, Calendars, Calculators, clocks, Notes, and Book Readers are some other applications that look like objects in their physical world.</p>



<p><p style="padding-bottom: 30px">Before we conclude, here are a few amusing examples of poor design.</p></p>



<p class="has-text-align-center"><img decoding="async" style="width: 300px" src="https://s3.us-east-1.amazonaws.com/blog-assets-production.testsigma.com/blogs/wp-content/uploads/migrated_images/wNejDfCSfWc5z2HdOcbYAMzVKf4X5pE9jtSLcF3syxoxtbgjl1pvuWADoTKah2RBNLBbjtbmHRHc10vW_VREXpjqXvD6LsCjr8SqUrT15ezT5-2M4cJf_liZBjIbc9zn_yM-mYZGU3-Q_kStgfuL8Dk_1748948764.png" alt="Testsigma - HOW POOR DESIGN RUINED MY MOVIE EXPERIENCE"></p>



<p class="has-text-align-center"><img decoding="async" style="width: 300px" src="https://s3.us-east-1.amazonaws.com/blog-assets-production.testsigma.com/blogs/wp-content/uploads/migrated_images/6y9HQJNkDv5Wqm0YrtYA4A6lAsYVTRzTnH5ITSOr5cPR0l9I5v_7NOPYPFzwK3McLPaQybFK3qa3JtAUq-EZK7Y2aZe3x5C2ghInP-w1NJTURq05tjRWwf12eCKSIyr9UE_6SnbT-VxaZ-e3meikLNY_1748948779.png" alt="Testsigma - HOW POOR DESIGN RUINED MY MOVIE EXPERIENCE"></p>



<p><p style="padding-top: 30px;padding-bottom: 30px"><strong>I believe I need not explain why I poured curd into my tea.</strong></p></p>



<div class="wp-block-image"><figure class="aligncenter is-resized"><img loading="lazy" decoding="async" src="https://s3.us-east-1.amazonaws.com/blog-assets-production.testsigma.com/blogs/wp-content/uploads/migrated_images/fMavBSIPlUz5HyvM_6szZwlqoDgzE9QmLj1c8C6KpEDCuCMQbLhNx4Ieg5OMFqaVOqSQH_EdUjJCWPSRKIbVSIdkNd-9QcF8EXwU_OkyMuj90T15ZQgmZZMvp0AFPjw7Sb6R-USquRI-cpUHQ3-_PF4_1748948772.jpg" alt="amusing examples of poor design 3" width="300" height="300"/></figure></div>



<p><p style="padding-top: 30px;padding-bottom: 30px"><strong>It&#8217;s no surprise that the lights come on while someone is at the sink.</strong></p></p>



<div class="wp-block-image"><figure class="aligncenter is-resized"><img loading="lazy" decoding="async" src="https://s3.us-east-1.amazonaws.com/blog-assets-production.testsigma.com/blogs/wp-content/uploads/migrated_images/hHrxjNQnwqjCyHaOOLUxupz91zFL2yX1N_DEweyaQR4fpQkIOOWauCv-yTNI-RgmYqrlmnMum7LQEKn9-Otqfj-rPDog1deG6ZBJvXeMR5m0M9VOMhzaEWJmbgaZA8Mv_HHWEwh_5QIAudj7IZOMjqo_1748948762.jpg" alt="amusing examples of poor design 4" width="400" height="400"/><figcaption><strong>A secret door to escape from the sink?</strong></figcaption></figure></div>



<h2 class="wp-block-heading" id="conclusion"><span id="CONCLUSION"><strong>CONCLUSION</strong></span></h2>



<p>As testers, you can make a big difference in terms of user experience(UX) by including usability testing as part of your QA. Implementing this will make you and your team champions of a user-centric culture in your organization. Start small and take little steps that will lead you to success. Begin by reading about the fundamentals of UX, meet with your UX team and collaborate with them. </p>



<p>Participate in the design phase and try to contribute as much as possible. Think like a user and help your users achieve their goals when interacting with your product. A good UX gives your users a compelling reason to use your product.&nbsp; There is no better way than to learn from your real-life experiences. Learn from the design mistakes of others and ensure that your product avoids them.</p>



<p style="padding-bottom: 20px">I hope you enjoyed this article. Lot more coming in part 2; stay tuned! Share your personal experiences with poor design in the comments section below.</p>



<p><button class="btn bg-primary cta-btn" style="margin: auto"><a href="https://github.com/testsigmahq/testsigma" target="_blank" rel="noopener noreferrer" style="color:#fff">Try  the most intuitive open-source low code test automation tool</a></button></p>



<p style="padding-top: 20px"><a href="https://testsigma.com/" target="_blank" rel="noreferrer noopener">Testsigma</a> offers the finest in its class user experience, that will enable you to step up the pace of your test automation.</p>



<p style="padding-top: 10px">Read more about Mobile usability testing here: <a href="https://testsigma.com/blog/mobile-usablity-testing/" target="_blank" rel="noreferrer noopener">https://testsigma.com/blog/mobile-usablity-testing/</a></p>



<p class="has-small-font-size">PC: <a href="https://www.freepik.com/" target="_blank" rel="noreferrer noopener nofollow">freepik</a> </p>


UX & Testing: UX Lessons Learned From My Real-Life Experiences - Part 1

UX & Testing: 3 Real-Life UX Lessons -Part 1


<p>Software Testing is primarily an information-gathering process that assists stakeholders in making informed decisions. However, it can be problematic to gather information if the testing process is constantly interrupted by diversions and interruptions. <a href="https://testsigma.com/blog/best-software-testing-tools-qas-are-using-in-2022/" target="_blank" rel="noreferrer noopener">Software Testing tools</a> and test automation scripts can lead to false positives if proper measures and considerations are not taken when setting up the testing and automation process.</p>



<p>In this article, I will discuss some of the common causes behind false positives and provide you with some tips and tricks to help you avoid them during your <a href="https://testsigma.com/automated-testing" target="_blank" rel="noreferrer noopener">software test automation</a> process.</p>



<div id="toc_container" class="no_bullets"><p class="toc_title">Table Of Contents</p><ul class="toc_list"><li><a href="#False_Positives"><span class="toc_number toc_depth_1">1</span> False Positives</a></li><li><a href="#Common_Causes_of_False_Positives_in_Software_Testing"><span class="toc_number toc_depth_1">2</span> Common Causes of False Positives in Software Testing</a><ul><li><a href="#1_Flaky_Test_Automation_Scripts"><span class="toc_number toc_depth_2">2.1</span> 1. Flaky Test Automation Scripts: </a></li><li><a href="#2_Changing_Locators_Automation_Hooks"><span class="toc_number toc_depth_2">2.2</span> 2. Changing Locators (Automation Hooks): </a></li><li><a href="#3_Unstable_Test_Environment"><span class="toc_number toc_depth_2">2.3</span> 3. Unstable Test Environment: </a></li><li><a href="#4_Impractical_Test_Sequence"><span class="toc_number toc_depth_2">2.4</span> 4. Impractical Test Sequence: </a></li><li><a href="#5_Configuration_Issues"><span class="toc_number toc_depth_2">2.5</span> 5. Configuration Issues: </a></li><li><a href="#6_Script_Development_Execution_on_one_specific_machine"><span class="toc_number toc_depth_2">2.6</span> 6. Script Development &amp; Execution on one specific machine: </a></li></ul></li><li><a href="#Impact_of_False_Positives"><span class="toc_number toc_depth_1">3</span> Impact of False Positives</a></li><li><a href="#Avoiding_False_Positives_in_Software_Testing"><span class="toc_number toc_depth_1">4</span> Avoiding False Positives in Software Testing</a><ul><li><a href="#1_Auto-Healing_Locators"><span class="toc_number toc_depth_2">4.1</span> 1. Auto-Healing Locators: </a></li><li><a href="#2_Robust_Locators_Automation_Hooks"><span class="toc_number toc_depth_2">4.2</span> 2. Robust Locators (Automation Hooks): </a></li><li><a href="#3_Automatic_Retry_Reruns"><span class="toc_number toc_depth_2">4.3</span> 3. Automatic Retry / Rerun(s): </a></li><li><a href="#4_Scheduling_test_runs_periodically_to_ascertain_stability"><span class="toc_number toc_depth_2">4.4</span> 4. Scheduling test runs periodically to ascertain stability: </a></li><li><a href="#5_Develop_execute_on_separate_machines"><span class="toc_number toc_depth_2">4.5</span> 5. Develop &amp; execute on separate machines: </a></li><li><a href="#6_Plan_Testing_across_Layers"><span class="toc_number toc_depth_2">4.6</span> 6. Plan Testing across Layers: </a></li><li><a href="#7_Refreshing_Test_Environment"><span class="toc_number toc_depth_2">4.7</span> 7.  Refreshing Test Environment: </a></li><li><a href="#8_Verbose_Logging_Observability"><span class="toc_number toc_depth_2">4.8</span> 8. Verbose Logging &amp; Observability</a></li><li><a href="#9_Using_Contract_Verification_Scripts"><span class="toc_number toc_depth_2">4.9</span> 9. Using Contract Verification Scripts: </a></li></ul></li></ul></div>
<h2 class="has-text-align-left wp-block-heading" id="h-false-positives"><span id="False_Positives"><strong>False Positives</strong></span></h2>



<p>False Positives are commonly observed due to:</p>



<ul class="wp-block-list"><li>Errors in software test automation scripts</li><li>Instability in the <a href="https://testsigma.com/blog/test-environment/" target="_blank" rel="noreferrer noopener">test environment</a></li><li>Failures due to third-party libraries or cooperating processes, etc.</li></ul>



<p>If you are into software test automation, you may have already seen false positives like:</p>



<ul class="wp-block-list"><li>Automation Test Script Failure due to changing locators</li><li>Test Pipeline Failure due to Build Issue(s), etc.</li></ul>



<h2 class="has-text-align-left wp-block-heading" id="h-common-causes-of-false-positives-in-software-testing"><span id="Common_Causes_of_False_Positives_in_Software_Testing"><strong>Common Causes of False Positives in Software Testing</strong></span></h2>



<p>Now that we have an understanding of what a false positive is, let&#8217;s look at the common causes:</p>



<h3 class="wp-block-heading" id="1-flaky-test-automation-scripts"><span id="1_Flaky_Test_Automation_Scripts"><strong>1. Flaky Test Automation Scripts: </strong></span></h3>



<p>It is one of the most common reasons behind false positives during software test automation. Flakiness or instability can be due to many factors. Some of the popular ones are:</p>



<p>i. Poor design of test scripts</p>



<p>ii. Non-modular / non-maintainable code structure</p>



<p>iii. Non-clean code</p>



<p>iv. Poor testability of the application</p>



<p><strong>Read here &#8211; all about <a href="https://testsigma.com/guides/flaky-test/" target="_blank" rel="noreferrer noopener">Flaky Test</a></strong>.</p>



<h3 class="wp-block-heading" id="2-changing-locators-automation-hooks"><span id="2_Changing_Locators_Automation_Hooks"><strong>2. Changing Locators (Automation Hooks): </strong></span></h3>



<p>Regardless of the test automation platform, a common feature is the reliance of automation on some hooks or locators. If these hooks change too frequently or are not defined in a robust way, it may lead to frequent false positives followed by an investigation and fixing time. Commonly used automation hooks are:</p>



<p>i. XPaths</p>



<p>ii. JSON Paths</p>



<p>iii. XML Paths, etc.</p>



<h3 class="wp-block-heading" id="3-unstable-test-environment"><span id="3_Unstable_Test_Environment"><strong>3. Unstable <a href="https://testsigma.com/blog/test-environment/" target="_blank" rel="noreferrer noopener">Test Environment:</a> </strong></span></h3>



<p>There are a number of factors that can directly or indirectly affect the state of a system and the environment in which it is being tested. Some of such factors are:</p>



<p>i. The current and changing state of the system </p>



<p>ii. Dependent processes and their effects on the test environment</p>



<p>iii. Version changes</p>



<p>iv. Breaking contracts</p>



<h3 class="wp-block-heading" id="4-impractical-test-sequence"><span id="4_Impractical_Test_Sequence"><strong>4. Impractical Test Sequence: </strong></span></h3>



<p>In some cases, a test depends on specific business logic. Ex: Reading software from a device makes sense if you have already written software for the device. If someone wants to test the read functionality but does it after a delete software test, it will just lead to an impractical test sequence and a false positive.</p>



<p class="has-text-align-center">Write Software &#8211;&gt; Read Software</p>



<p class="has-text-align-center">Delete Software &#8211;&gt; Read Software</p>



<h3 class="wp-block-heading" id="5-configuration-issues"><span id="5_Configuration_Issues"><strong>5. Configuration Issues: </strong></span></h3>



<p>Most complex software have a configurable build, and deployment system. When such configuration is not managed properly, it can lead to a range of configuration-related issues. Oftentimes, the configuration(s) is done manually, which can lead to unintended issues</p>



<p>Also, as an automation engineer, does your test suite consider specific versions of each dependency? Does it also consider the test environment states? Do your automation scripts use the setup and teardown (cleanup) modules to set up the test environment?</p>



<h3 class="wp-block-heading" id="6-script-development-execution-on-one-specific-machine"><span id="6_Script_Development_Execution_on_one_specific_machine"><strong>6. Script Development &amp; Execution on one specific machine: </strong></span></h3>



<p>Scripts that only run on local machine is mostly FLAKY. Script developers often ignore factors that may change on other machines when developing a script for a specific machine. Moreover, Programs don&#8217;t do what they haven&#8217;t been told to pay attention to, which leads to false positives.</p>



<h2 class="has-text-align-left wp-block-heading" id="h-impact-of-false-positives"><span id="Impact_of_False_Positives"><strong>Impact of False Positives</strong></span></h2>



<p>False positives often end up creating a ripple of side effects. It can impact testing in ways you might not expect. Here is how false positives can impact your testing:</p>



<p><strong>1. Loss of time:&nbsp;</strong></p>



<p>i. In going through logs</p>



<p>ii. In investigating the problem</p>



<p>iii. In reproducing the test steps</p>



<p>iv. In fixing the test scripts, environment, etc.</p>



<p><strong>2. Noise in Automated Testing Cycles</strong></p>



<p><strong>3. Loss of credibility &amp; integrity:</strong> False positives from your software test automation is inversely proportional to your test process credibility.</p>



<p><strong>4. Defocus on the actual information gathering process (testing)</strong></p>



<p class="has-text-align-center"><em>“The more you go in one direction, the far you go from the opposite direction.”</em></p>



<p class="has-text-align-center"><strong><em>Jerry Weinberg</em></strong></p>



<div class="cta-banner-v2">
<div class="title-with-description ">
<p class="title">Automate your tests for Web, Mobile, Desktop and APIs on Cloud with Testsigma. No setup required.</p>
</div>
<a href="https://testsigma.com/signup" target="_blank" class="cta-btn-v1" rel="noopener">Try for free</a>
</div>



<h2 class="has-text-align-left wp-block-heading" id="h-avoiding-false-positives-in-software-testing"><span id="Avoiding_False_Positives_in_Software_Testing"><strong>Avoiding False Positives in Software Testing</strong></span></h2>



<p class="has-text-align-left">The best strategy to deal with false positives is by avoiding them in the first place. To prevent false positives, here are some tips and tricks:</p>



<h3 class="wp-block-heading" id="1-auto-healing-locators"><span id="1_Auto-Healing_Locators"><strong>1. Auto-Healing Locators: </strong></span></h3>



<p>If you have ever attempted GUI App automation, you already know about the challenge of continuously changing locators. However, a good automation solution will allow multiple locators to identify GUI elements that can be used to make the system self-heal in the event of a locator failure. Ex: <a href="https://testsigma.com/" target="_blank" rel="noreferrer noopener"><strong>Testsigma</strong></a> provides the facility of auto-healing locators by default.&nbsp;</p>



<h3 class="wp-block-heading" id="2-robust-locators-automation-hooks"><span id="2_Robust_Locators_Automation_Hooks"><strong>2. Robust Locators (Automation Hooks): </strong></span></h3>



<p>Writing robust locators is a craft and requires a good understanding of the element lookup process. Learning how to write robust and stable locators is always a good investment.&nbsp;</p>



<h3 class="wp-block-heading" id="3-automatic-retry-rerun-s"><span id="3_Automatic_Retry_Reruns"><strong>3. Automatic Retry / Rerun(s):</strong> </span></h3>



<p>Automatic retry/rerun strategy can help you know the consistency of the issue. In some cases, the issue can be due to a momentary glitch in the test environment. Automated rerun strategies confirm this and save you time investigating a false positive.</p>



<h3 class="wp-block-heading" id="4-scheduling-test-runs-periodically-to-ascertain-stability"><span id="4_Scheduling_test_runs_periodically_to_ascertain_stability"><strong>4. Scheduling test runs periodically to ascertain stability: </strong></span></h3>



<p>A script not running is as good as a script, not present. Testing scripts should always be run periodically to ensure the stability of the environment, product, test scripts, infrastructure, etc.</p>



<h3 class="wp-block-heading" id="5-develop-execute-on-separate-machines"><span id="5_Develop_execute_on_separate_machines"><strong>5. Develop &amp; execute on separate machines: </strong></span></h3>



<p>Running regression tests on separate machines is a good strategy to avoid the pitfall of flaky scripts. Testing on separate machines helps reduce the likelihood of flakiness. You can also run headless tests or use docker containers or cloud systems. Read about <a href="https://testsigma.com/blog/selenium-headless/" target="_blank" rel="noreferrer noopener">Selenium Headless Tests</a></p>



<h3 class="wp-block-heading" id="6-plan-testing-across-layers"><span id="6_Plan_Testing_across_Layers"><strong>6. Plan Testing across Layers: </strong></span></h3>



<p>Planning entire testing on one layer can be a bad strategy in most cases. Testing should always be planned across several layers. Also, consider the flakiness index of different layers. Flakiness Index: UI &gt; API &gt; Unit</p>



<h3 class="wp-block-heading" id="7-refreshing-test-environment"><span id="7_Refreshing_Test_Environment"><strong>7.  Refreshing <a href="https://testsigma.com/blog/test-environment/" target="_blank" rel="noreferrer noopener">Test Environment</a>: </strong></span></h3>



<p>Test Environment and state can lead to false positives in your test results. Things that generally help to avoid such issues are:</p>



<p>1. Resetting State</p>



<p>2. Using Hooks</p>



<p>i. Setup </p>



<p>ii. Teardown </p>



<p>3. Spinning up docker containers, etc. </p>



<h3 class="wp-block-heading" id="8-verbose-logging-observability"><span id="8_Verbose_Logging_Observability"><strong>8. Verbose Logging &amp; Observability</strong></span></h3>



<h3 class="wp-block-heading" id="9-using-contract-verification-scripts"><span id="9_Using_Contract_Verification_Scripts"><strong>9. Using Contract Verification Scripts: </strong></span></h3>



<p>If you are <a href="https://testsigma.com/guides/api-testing/" target="_blank" rel="noreferrer noopener">testing API</a>(s) that depends on contracts, then it is always good to run scripts that:</p>



<p>i. Monitor Contracts</p>



<p>ii. Monitor Dependencies</p>



<p>For all our visual readers, I have summarized this entire article in the form of this <a href="https://xmind.app/m/sxBCik/" target="_blank" rel="noreferrer noopener">mind map</a>.</p>



<p>We hope you learned something about false positives and how to avoid them during the testing process through this article.</p>



<div class="cta-banner-v2">
<div class="title-with-description ">
<p class="title">Build and run tests 10x faster for web, mobile, desktop and APIs under Testsigma&#8217;s unified platform.</p>
</div>
<a href="https://testsigma.com/signup" target="_blank" class="cta-btn-v1" rel="noopener">Try for free</a>
</div>



<p>Wondering why to choose an open source test automation tool, read here: <a href="https://testsigma.com/blog/reasons-to-choose-an-open-source-test-automation-tool/" target="_blank" rel="noreferrer noopener">Reasons to Choose an Open-Source Test Automation Tool</a></p>


Software Test Automation False Positives & How to Avoid Them

What are False Positives & How to Avoid Them?


<p>The iterative approach to software development emerged around the 1990s. What started as a small co-located, self-sustaining team approach was widely adopted by many development teams. The agile mindset paved way for multiple development frameworks, including the infamous “Scrum methodology”. </p>



<p>With time, processes undergo metamorphoses, during which a few unpleasant practices sneak in causing distractions within the teams. This article focuses on a few unpleasant software testing distractors within an Agile Scrum team.&nbsp;&nbsp;</p>



<p>The below agile testing distractors may not have a significant impact in plain sight, if left unattended they may cause potential harm in the long run.&nbsp;</p>



<div id="toc_container" class="no_bullets"><p class="toc_title">Table Of Contents</p><ul class="toc_list"><li><a href="#Muted_Refinement_sessionsnbsp"><span class="toc_number toc_depth_1">1</span> Muted Refinement sessions&nbsp;</a></li><li><a href="#Absence_of_testing_notesnbsp"><span class="toc_number toc_depth_1">2</span> Absence of testing notes&nbsp;</a></li><li><a href="#Separate_QA_boardnbsp"><span class="toc_number toc_depth_1">3</span> Separate QA board&nbsp;</a></li><li><a href="#Ignored_test_effortsnbsp"><span class="toc_number toc_depth_1">4</span> Ignored test efforts&nbsp;</a></li><li><a href="#Commenting_defectsnbsp"><span class="toc_number toc_depth_1">5</span> Commenting defects&nbsp;</a></li><li><a href="#Piggybacking_testersnbsp"><span class="toc_number toc_depth_1">6</span> Piggybacking testers&nbsp;</a></li></ul></div>
<h2 class="wp-block-heading" id="h-muted-refinement-sessions"><span id="Muted_Refinement_sessionsnbsp"><strong>Muted Refinement sessions&nbsp;</strong></span></h2>



<div class="wp-block-image"><figure class="aligncenter is-resized"><img loading="lazy" decoding="async" src="https://s3.us-east-1.amazonaws.com/blog-assets-production.testsigma.com/blogs/wp-content/uploads/migrated_images/sXomQO3fUniztvQJkVhL5aaLVmojX6kgllxDRl6VcT_oVXcPEXhht-HsWY2Bdq-4Exi56oTV2JAMnvJ8q87DolB5JnwVaSlyB2EwCGksvBfeQRVsSerCo31HmogvGa4MksGSV0BRZ3cGBnGbe-c_1748948974.png" alt="Muted Refinement sessions" width="400" height="400"/><figcaption>The unpleasant phenomenon in Agile testing 1&nbsp;</figcaption></figure></div>



<p style="padding-top: 20px">By default, the complexity of a user story is linked to developmental effort conveniently ignoring the testing effort involved. Sometimes implementation would hardly take any time but, the impact of this change stimulates a larger blast radius which significantly boosts the time required for testing. </p>



<p>A user story is complete and common understanding is established only if the story is addressed in 360degrees. Test implications should be considered during refinement sessions. Test <a href="https://testsigma.com/blog/quality-engineering-discussions-with-james-espie/" target="_blank" rel="noopener">engineers should facilitate this discussion</a> with the product owner and the wider development team during the refinement session.&nbsp;</p>



<h2 class="wp-block-heading" id="absence-of-testing-notes"><span id="Absence_of_testing_notesnbsp"><strong>Absence of testing notes&nbsp;</strong></span></h2>



<p>Refinement sessions provide a good opportunity for the PO(Product Owner) and the development team to scrub through the user story and add more details. Breaking down a user story into implementable tasks, clarifying any open questions, and validating certain aspects of implementations are the main aim of refinement meetings. However, most of the teams miss out on capturing the test notes.&nbsp;</p>



<p>Let us first discuss what a testing note is?&nbsp;</p>



<p><p style="padding-bottom: 30px">The supplemental details required to execute the tests for that particular user story is called a testing note. It can be any details like &#8211; test data, plugin requirements, dependency on external services, test limitations, test relevancy, etc.</p></p>



<div class="wp-block-image"><figure class="aligncenter is-resized"><img loading="lazy" decoding="async" src="https://s3.us-east-1.amazonaws.com/blog-assets-production.testsigma.com/blogs/wp-content/uploads/migrated_images/5vtx-1rhghBdiJ_9puW34i9d3j70PtyOIeClmqtcu9n765OorbqDPmzfsHe2GodvqESTJ_rpKrSIDCJ3sbs82ZHiiPEH7FbY3Kyhki6Ov4-nrkjM_-U1Hm0cG-BEf3N-B4w-c2oCWciOqz12dF8_1748948976.png" alt="Absence of testing notes" width="400" height="400"/><figcaption>The unpleasant phenomenon in Agile testing 2&nbsp;</figcaption></figure></div>



<p style="padding-top: 20px">In real-world projects, not all stories can be tested in all environments.&nbsp;</p>



<p>For example: develop or test environments have limited configuration capacity and files of certain sizes cannot be processed. Capturing testing notes helps teams to bring clarity and a shared understanding of how a particular scenario can be approached. It also gives POs a good opportunity to understand the hidden risks.&nbsp;</p>



<h2 class="wp-block-heading" id="separate-qa-board"><span id="Separate_QA_boardnbsp"><strong>Separate QA board&nbsp;</strong></span></h2>



<p>Mainstream scrum boards restrict by displaying only the user stories movement across swim lanes. However, an agile <a href="https://testsigma.com/blog/how-to-be-an-active-tester/" target="_blank" rel="noopener">tester performs much more test activities</a> than just the new feature testing or regression testing. For example:&nbsp;</p>



<p>1. Supporting small hot-fixes&nbsp;</p>



<p>2. Short enhancements&nbsp;</p>



<p>3. Legacy applications support&nbsp;</p>



<p>4. Usability testing&nbsp;</p>



<p>5. Automating the user stories&nbsp;</p>



<p>6. Maintenance of automated scripts&nbsp;</p>



<p><p style="padding-bottom: 30px">7. TestOps etc</p></p>



<div class="wp-block-image"><figure class="aligncenter is-resized"><img loading="lazy" decoding="async" src="https://s3.us-east-1.amazonaws.com/blog-assets-production.testsigma.com/blogs/wp-content/uploads/migrated_images/8T1QM1uf0AmUJEIGlHrHTYiwxdbU27VMf4Pu3xUW61U9_6HaxbFlSSvNhWL6Ydg7ralpHDt8lDrqAFepsPXmkH-D9PD5a7VOLHa9AsCIsWDNvFFgdBRApjlBg26eri1isQBBBTNo9uEMqGxBtGc_1748948977.png" alt="Separate QA board" width="400" height="400"/><figcaption>The unpleasant phenomenon in Agile testing 3&nbsp;</figcaption></figure></div>



<br><div class="bg-primary cta">
<p class="fz-21 “pt-1” "><b>Easily automate your user stories with completely customizable no-code test automation tool Testsigma.</b></p>
<div class="d-flex mb-1" style="justify-content:space-evenly">
     <button class="btn cta-btn bg-white"><a href="https://github.com/testsigmahq/testsigma" target="_blank" rel="noopener noreferrer">Try Testsigma </a></button></div>
</div><br>



<p>By and large development teams remain unaware of any of these activities. Agile development team tasks should be as transparent as possible. The available capacity of every team member should be taken into account before pulling in sprint tasks. </p>



<p>Especially the automation tasks are separated out to different scrum boards, this is detrimental in a long run. To stop this from becoming a major distractor, all the peripheral test activities should be made visible in the sprint scrum board to account for overall delivery within the agile scrum team.&nbsp;</p>



<p>The idea is not to completely discourage having a separate QA scrum board, this can be handy in some <a href="https://testsigma.com/blog/agile-automation-testing-safe/" target="_blank" rel="noopener">scaled agile</a> teams when multiple scrum teams have to coordinate several tasks. However, the clarity of what should stay away from mainstream scrum boards should be given a thought.&nbsp;</p>



<h2 class="wp-block-heading" id="ignored-test-efforts"><span id="Ignored_test_effortsnbsp"><strong>Ignored test efforts&nbsp;</strong></span></h2>



<p>After scrubbing and combing the backlog in the refinement session, PO prepares a prioritized backlog list which will be presented in a scrum planning meeting. The development team maps each task against the size which implies the effort required to implement the story. Planning is a crucial scrum activity, and most teams miss out on taking testing efforts into account.&nbsp;</p>



<p><p style="padding-bottom: 30px">This is an anti-pattern in agile methodology. A story is considered to be complete only if it goes through development and testing activities. Agile teams should encourage every team member to actively participate in the planning poker session. Test Engineers should confidently step forward to provide their view on the user stories during the planning meetings.</p></p>



<div class="wp-block-image"><figure class="aligncenter is-resized"><img loading="lazy" decoding="async" src="https://s3.us-east-1.amazonaws.com/blog-assets-production.testsigma.com/blogs/wp-content/uploads/migrated_images/NBe9UdY9kggu_biAxAuULTkvu9_TC8_E21miSZPLUwthN6hV9RZn5tMnuTVBmVVRDZfbBqTATQvgRR_XmO_AGerigjrD7j52oEh5Clh1vTYtSwKMukFWwDokguIa8WuAib_5rYaNim2BocT7zcA_1748948978.png" alt="Ignored test efforts" width="400" height="400"/><figcaption>The unpleasant phenomenon in Agile testing 4&nbsp;</figcaption></figure></div>



<h2 id="commenting-defects"><span id="Commenting_defectsnbsp"><strong>Commenting defects&nbsp;</strong></span></h2>



<p><p style="padding-bottom: 30px">Agile recommends reducing waste and weeding out all the overhead activities. Development teams who do not use external bug reporting tools, encourage team members to report the bugs within the user story tickets. In such cases, the test team will miss out on the most valuable QA activity “root cause analysis”. Why is it even important? Defects are a mirror to the health of the application, a good quality report states the weak links and helps the development team in strengthening those areas which need deeper attention.</p></p>



<div class="wp-block-image"><figure class="aligncenter is-resized"><img loading="lazy" decoding="async" src="https://s3.us-east-1.amazonaws.com/blog-assets-production.testsigma.com/blogs/wp-content/uploads/migrated_images/OvOyCBgRq_6ruLf6WjmnaLZM7_MdLqQSMXBByYQ0UBe4y-TEdIA2N8BRY2CgNcrB4w2iyML35Qdx3SvNiEaXZYn1wjmT0tBya2xi0kkYxpHNcXTzxLGzv-ivJovBMUthNoVUactR6xoKRBX-hUc_1748948975.png" alt="Commenting defects" width="400" height="400"/><figcaption>The unpleasant phenomenon in Agile testing 5&nbsp;</figcaption></figure></div>



<p style="padding-top: 20px">Teams commenting defects within the user story will be unable to aggregate the bugs and feed the root cause analysis activity. The whole idea of iterative development is driven by continuous improvement, when defects are not accessible teams miss out on valuable intrinsic details. To avoid this becoming a distractor in agile testing, it is important to educate development teams about the importance of defect analysis and follow bug reporting either using dedicated tools or some other way where they can aggregate data over a period of time&nbsp;</p>



<h2 class="wp-block-heading" id="piggybacking-testers"><span id="Piggybacking_testersnbsp"><strong>Piggybacking testers&nbsp;</strong></span></h2>



<p>Early feedback helps development teams to adopt changes more easily. User stories checked earlier in the development cycle help to establish an early feedback loop. In the real world situation, when the user story is developed and tested PO’s are expected to do a walk-through and bring forth any changes if required.&nbsp;</p>



<p>POs/PM create dependency on testers to give them the demo of a new feature. If the tester and PO fail to catch up on time, the tickets just pile up in the QA lane thus increasing the cycle time. Apprehend this bottleneck even before it piles up to cause deeper issues. Encourage POs to put their hands on the application and try out the features themselves. Doing so not just reduce the latency but also helps business to understand how the feature fits with wider application.&nbsp;</p>



<p style="padding-top: 10px">Related reads:</p>



<p><a href="https://testsigma.com/regression-testing" target="_blank" rel="noreferrer noopener">https://testsigma.com/regression-testing </a><a href="https://testsigma.com/continuous-testing" target="_blank" rel="noreferrer noopener">https://testsigma.com/continuous-testing <br></a><a href="https://testsigma.com/blog/top-test-automation-challenges-to-look-out-for/" target="_blank" rel="noreferrer noopener">https://testsigma.com/blog/top-test-automation-challenges-to-look-out-for/ </a><a href="https://testsigma.com/blog/understanding-agile-testing-framework/" target="_blank" rel="noreferrer noopener">https://testsigma.com/blog/understanding-agile-testing-framework/ </a><a href="https://testsigma.com/blog/challenges-insprint-automation-regression-testing/" target="_blank" rel="noreferrer noopener">https://testsigma.com/blog/challenges-insprint-automation-regression-testing/</a></p>


The Unpleasant Phenomenon In Agile Testing


<p>The core objective of both code coverage and test coverage remains the measurement metrics leveraged to simplify the assessment of the quality of application code. These are significant for developers to rectify any errors if discovered and enhance the overall quality of an application.</p>



<div id="toc_container" class="no_bullets"><p class="toc_title">Table Of Contents</p><ul class="toc_list"><li><a href="#Code_Coverage_vs_Test_Coverage_8211_Overview"><span class="toc_number toc_depth_1">1</span> Code Coverage vs Test Coverage &#8211; Overview</a><ul><li><a href="#What_is_Code_Coverage"><span class="toc_number toc_depth_2">1.1</span> What is Code Coverage?</a></li><li><a href="#What_is_Test_Coverage"><span class="toc_number toc_depth_2">1.2</span> What is Test Coverage?</a></li></ul></li><li><a href="#Code_Coverage_vs_Test_Coverage_8211_A_Comparison"><span class="toc_number toc_depth_1">2</span> Code Coverage vs Test Coverage &#8211; A Comparison</a></li><li><a href="#Code_Coverage_vs_Test_Coverage_Which_One_Should_You_Choose"><span class="toc_number toc_depth_1">3</span> Code Coverage vs Test Coverage: Which One Should You Choose?</a></li><li><a href="#Summary"><span class="toc_number toc_depth_1">4</span> Summary</a></li><li><a href="#Frequently_Asked_Questions"><span class="toc_number toc_depth_1">5</span> Frequently Asked Questions</a><ul><li><a href="#What_is_the_difference_between_code_coverage_and_feature_coverage"><span class="toc_number toc_depth_2">5.1</span> What is the difference between code coverage and feature coverage?</a></li></ul></li></ul></div>
<h2 class="wp-block-heading" id="code-coverage-vs-test-coverage-overview"><span id="Code_Coverage_vs_Test_Coverage_8211_Overview"><strong>Code Coverage vs Test Coverage &#8211; Overview</strong></span></h2>



<h3 class="wp-block-heading" id="what-is-code-coverage"><span id="What_is_Code_Coverage">What is Code Coverage?</span></h3>



<p>Code Coverage is the percentage of the source code executed by a test suite. It points out what has been tested and what has not been tested, thereby revealing untested paths. Tools such as JaCoCo or Istanbul usually visualize such data by pointing out areas where more tests are needed. High code coverage may imply high quality but does not guarantee it; it is a good metric for the effectiveness of testing.</p>



<h3 class="wp-block-heading" id="what-is-test-coverage"><span id="What_is_Test_Coverage">What is Test Coverage?</span></h3>



<p><a href="https://testsigma.com/blog/test-coverage/" target="_blank" rel="noreferrer noopener">Test Coverage</a> is the extent to which the testing process covers the software requirements or specifications. It ensures testing all aspects, both functional and non-functional, based on defined criteria. Sometimes, test coverage may be measured using requirement traceability matrices or similar tools.</p>



<p>This will help ensure that all features have been validated and verified against requirements, thus enhancing confidence in the product, though it does not coincide with the thoroughness of testing.</p>



<p>Check here &#8211; <a href="https://testsigma.com/blog/how-create-best-test-case-design-get-maximum-test-coverage/" target="_blank" rel="noreferrer noopener">How do You Ensure Test Coverage</a></p>



<h2 class="wp-block-heading" id="code-coverage-vs-test-coverage-a-comparison"><span id="Code_Coverage_vs_Test_Coverage_8211_A_Comparison"><strong>Code Coverage vs Test Coverage &#8211; A Comparison</strong></span></h2>



<p>Let us look into this table to know more:</p>



<figure class="wp-block-table"><table><tbody><tr><td><strong>Aspect</strong></td><td><strong>Code Coverage</strong></td><td><strong>Test Coverage</strong></td></tr><tr><td><strong>Definition</strong></td><td>Measures the percentage of code executed during testing.</td><td>The extent to which testing covers requirements/specifications.</td></tr><tr><td><strong>Advantages</strong></td><td>Identifies untested code, helps improve code quality, provides insights into testing effectiveness, helps in refactoring, and can lead to fewer bugs in production.</td><td>Ensures all features are validated, highlights gaps in testing, enhances confidence in product quality, facilitates requirement tracking, and encourages comprehensive test design.</td></tr><tr><td><strong>How to Measure?</strong></td><td>Tools like JaCoCo, Istanbul, or Clover are used to track executed lines/branches.</td><td>Through requirement traceability matrices or testing frameworks that align tests with requirements.</td></tr><tr><td><strong>Mechanisms</strong></td><td>Instrumentation of code, Static analysis.</td><td>Mapping requirements to test cases and test case reviews.</td></tr><tr><td><strong>Tools</strong></td><td>JaCoCo, Istanbul, Clover.</td><td>TestRail, HP ALM, Jira (with plugins).</td></tr></tbody></table></figure>



<p>Check here &#8211; <a href="https://testsigma.com/blog/test-coverage-techniques/" target="_blank" rel="noreferrer noopener">Test Coverage Techniques</a></p>



<h2 class="wp-block-heading" id="h-code-coverage-vs-test-coverage-which-one-should-you-choose"><span id="Code_Coverage_vs_Test_Coverage_Which_One_Should_You_Choose"><strong>Code Coverage vs Test Coverage: Which One Should You Choose?</strong></span></h2>



<p>It’s now time to address the elephant in the room – code coverage vs test coverage: which one to choose and why. As both of these are completely different measurement approaches, it won’t be justified to choose between the two. Code coverage is a quantitative measure and is more related to the white-box testing technique. While on the other hand, test coverage is a qualitative measure and a black-box testing approach. </p>



<p>So there’s no exact answer to this question &#8220;code coverage vs test coverage: which one to choose &#8220;, as it would entirely depend on your business requirements and the intricacy of the software application. In a majority of the cases, however, both test coverage and code coverage are used.</p>



<h2 class="wp-block-heading" id="h-summary"><span id="Summary"><strong>Summary</strong></span></h2>



<p>People have always mistaken both test coverage and code coverage to be the same term. But they don’t have anything in common!</p>



<p>For all the testers, having an in-depth analysis of code coverage and test coverage is vital. Not only do these techniques offer efficient testing, but also help developers save hundreds of hours and executives save resources.</p>



<p>Additionally, 100% code coverage should not be sought at any stage of SDLC because it will end up wasting more time and resources as developers would miss out on vital testing modules when short at the time.<br><br>None of the <strong>code coverage </strong>or <strong>test coverage </strong>is a perfect choice, but you should try both of them for a considerable amount of time. The combo would most likely yield the ideal results.</p>



<h2 class="wp-block-heading" id="frequently-asked-questions"><span id="Frequently_Asked_Questions"><strong>Frequently Asked Questions</strong></span></h2>



<h3 class="wp-block-heading" id="what-is-the-difference-between-code-coverage-and-feature-coverage"><span id="What_is_the_difference_between_code_coverage_and_feature_coverage">What is the difference between code coverage and feature coverage?</span></h3>



<p>Code coverage measures the percentage of code executed during tests, while feature coverage assesses whether all specified features or functionalities are tested.&nbsp;</p>



<customlinks>
  <ts-link-item>
    <ts-linktext-value>Test Coverage Metrics</ts-linktext-value>
    <ts-linkurl-value>https://testsigma.com/blog/test-coverage-metrics/</ts-linkurl-value>
  </ts-link-item>
  <ts-link-item>
    <ts-linktext-value>Test Automation Coverage</ts-linktext-value>
    <ts-linkurl-value>https://testsigma.com/blog/test-automation-coverage/</ts-linkurl-value>
  </ts-link-item>
  <ts-link-item>
    <ts-linktext-value>Flutter Test Coverage</ts-linktext-value>
    <ts-linkurl-value>https://testsigma.com/blog/flutter-test-coverage/</ts-linkurl-value>
  </ts-link-item>
  <ts-link-item>
    <ts-linktext-value>Test Coverage Techniques</ts-linktext-value>
    <ts-linkurl-value>https://testsigma.com/blog/test-coverage-techniques/</ts-linkurl-value>
  </ts-link-item>
</customlinks>


feature image of Code Coverage vs Test Coverage

Code Coverage vs Test Coverage: Differences You Need to Know


<p>Working in software development as a tester, it can be difficult to find time to improve the testing process when you are the bottleneck to release with lots of tickets, stories or features to test. I am currently a QA Lead at <a href="https://cerahq.com/" target="_blank" rel="noreferrer noopener nofollow">Cera Care</a>, one of the fastest growing healthcare startups in Europe. Working in this fast moving environment is very challenging for my team, where features are prioritised over anything else and teams have up to 6 developers to 1 QA engineer. </p>



<p>As you can imagine this does not allow much time for activities outside of feature testing. Quality is compromised as the feature will be described as a minimal viable product (MVP). Improvements are added to the backlog to be implemented after the initial pilots or user feedback. </p>



<p>Before being able to tackle the quality technical debt another priority comes along meaning there is no time to revisit the feature. What has this got to do with being an active tester you might ask? Well, that’s where the testing role within my team has changed to more of an advisor and involves collaborating closely with developers, product, user experience (UX) and data.</p>



<figure class="wp-block-image is-resized"><img loading="lazy" decoding="async" src="https://s3.us-east-1.amazonaws.com/blog-assets-production.testsigma.com/blogs/wp-content/uploads/migrated_images/dI1RSiHdiHE94aLrHdLqNb1rn8ZBI_OFRwjrBFsRif39IG66YpL-gK413gqrMK512G4tQQHeHyZjVlieNb1eSgRIpg3jEKi0ect1jWj_lgGyBsX9Nb7zvOzdjuXFDZJyHJn3WtfoBRlBVShefA_1748949335.jpg" alt="Testsigma - How To Be An Active Tester" width="600" height="400"/></figure>



<p>Tester stereotype by<a href="https://unsplash.com/@markusspiske?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText" target="_blank" rel="noreferrer noopener nofollow"> Markus Spiske</a></p>



<div id="toc_container" class="no_bullets"><p class="toc_title">Table Of Contents</p><ul class="toc_list"><li><a href="#How_to_break_down_the_traditional_testers_stereotype"><span class="toc_number toc_depth_1">1</span> How to break down the traditional testers stereotype</a></li><li><a href="#Being_proactive_instead_of_reactive_in_testing"><span class="toc_number toc_depth_1">2</span> Being proactive instead of reactive in testing</a></li><li><a href="#Getting_involved_in_development_discussions"><span class="toc_number toc_depth_1">3</span> Getting involved in development discussions</a></li><li><a href="#Working_with_data_to_understand_user_funnels"><span class="toc_number toc_depth_1">4</span> Working with data to understand user funnels</a></li><li><a href="#Tester_participation_is_often_a_2_way_process"><span class="toc_number toc_depth_1">5</span> Tester participation is often a 2 way process</a></li><li><a href="#Testers_everywhere"><span class="toc_number toc_depth_1">6</span> Testers everywhere</a></li></ul></div>
<h2 class="wp-block-heading" id="how-to-break-down-the-traditional-testers-stereotype"><span id="How_to_break_down_the_traditional_testers_stereotype">How to break down the traditional testers stereotype</span></h2>



<p>Only a short while ago, I had a conversation with a startup founder who I explained the difference between checking and testing in relation to the value a tester can provide to the development process. With a strong product knowledge and an inquisitive mindset to explore the inner workings of a system. </p>



<p>The tester can get involved in conversations at the beginning of the development process. In my current organisation that starts with user research to discover what the current challenges are that the user is facing. At this stage the tester can sit in on the user research sessions or read the results that are published on dovetail. </p>



<p>This insight is invaluable for the testers to understand how the user would interact with the feature once it has been developed. They can form realistic scenarios when they come to explore the system and run their <a href="https://www.developsense.com/blog/2009/04/of-testing-tours-and-dashboards/" target="_blank" rel="noreferrer noopener nofollow">testing tours</a>.</p>



<h2 class="wp-block-heading" id="being-proactive-instead-of-reactive-in-testing"><span id="Being_proactive_instead_of_reactive_in_testing">Being proactive instead of reactive in testing</span></h2>



<p>Building on the participation of the tester in the user experience research phase. Sometimes you need help from other people and teams to enable your productivity. Such as investigating ways to make parts of the system easier to test with developers. Or finding data to improve your test data set with the data analysts. </p>



<p>This can be a frustrating process of waiting for others&#8217; time and delaying hands-on testing activities. This is where testers, by becoming an advisor, advocate or coach (however you want to describe it) can be very valuable. </p>



<p>Collaborating with the product team to make user stories clearer and easier to implement. Refining those acceptance criteria and improving the definition of done for development to include testing, monitoring and release documentation. This frees up testers time to concentrate on activities which refine the testing focus, increase the quality of the <a href="https://testsigma.com/blog/test-data/" target="_blank" rel="noreferrer noopener">test data</a> or open up almost impossible areas to test. </p>



<p>Read here more on <a href="https://testsigma.com/blog/active-testing/" target="_blank" rel="noreferrer noopener">Active Testing</a></p>



<div class="wp-block-image"><figure class="aligncenter is-resized"><img loading="lazy" decoding="async" src="https://s3.us-east-1.amazonaws.com/blog-assets-production.testsigma.com/blogs/wp-content/uploads/migrated_images/QzLyZj5iRtUz5t2f0FzVXUlts-zI8BjQPBYnWbF0JZYep0BSgmE67_0RWV_b9d3_RhfzLFH8sVQLAfWNXu8JpYoVlY4O0DUqC0ociPv6Ls4aJctPmswaoDPJv72trMbL_TlgmHcpGPJu_622xg_1748949332.jpg" alt="Testsigma - Being proactive instead of reactive in testing" width="600" height="400"/><figcaption>Developer and tester collaboration by<a href="https://unsplash.com/@charlesdeluvio?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText" target="_blank" rel="noreferrer noopener nofollow"> charlesdeluvio</a></figcaption></figure></div>



<h2 class="wp-block-heading" id="getting-involved-in-development-discussions"><span id="Getting_involved_in_development_discussions">Getting involved in development discussions</span></h2>



<p>Whether you consider yourself a technical or non-technical person (what the word technical means in terms of testing is another blog article). You can always get involved in developer discussions such as “technical refinements” (also called whiteboarding sessions). </p>



<p>Raising questions around <a href="https://testsigma.com/blog/testability/" target="_blank" rel="noreferrer noopener">testability </a>and consistency across API specifications for example is really important to improve the quality of the application. Also at the code review stage of development, a tester can ask the developer to walk them through the feature and the tests they’ve implemented. Identify edge cases and discover any cases which aren’t covered by the automated checks. Understanding the test coverage and where to focus your testing can help identify issues quicker.</p>



<h2 class="wp-block-heading" id="working-with-data-to-understand-user-funnels"><span id="Working_with_data_to_understand_user_funnels">Working with data to understand user funnels</span></h2>



<p>One of the most powerful collaborations a tester can make in my opinion is working with the data team. Whether that be looking at user funnels or considering data requirements in the development process. Analysing data in customer data tools like segment can help you identify the most important parts of the system for your users. Also the aim of analysing production data is to validate test scenarios and possibly identify new scenarios. </p>



<p>Walking through the user funnels with data analysts can help understand what the data is saying. Statistics was never my strong point, despite studying it at A Level (UK college exams) and taking statistics modules at university in my psychology degree (You can read more about my journey on my blog). The data team also provides the bridge between the business and application data. For example in my organisation, reports provided by the data team are crucial for finance to pay employees on time.</p>



<p style="padding-bottom: 30px"> In this example, the data engineers extract and transform the data from the application databases. Meaning the data platform has no direct dependencies on the application itself, only the data in the database. This can lead to data issues downstream without any breaking changes within the application. See the diagram below to explain the complexities of what I described.</p>



<div class="wp-block-image"><figure class="aligncenter size-full is-resized"><img loading="lazy" decoding="async" src="https://testsigma.com/blog/wp-content/uploads/Data-dependencies-from-web-application.png" alt="Testsigma - Working with data to understand user funnels" class="wp-image-19599" width="600" height="400"/><figcaption>Data dependencies from web application</figcaption></figure></div>



<h2 class="wp-block-heading" id="tester-participation-is-often-a-2-way-process"><span id="Tester_participation_is_often_a_2_way_process">Tester participation is often a 2 way process</span></h2>



<p>Tester participation is a two way communication. With all the teams involved that I described above it can feel like as a tester you are the one always asking for people to help you out. However, it&#8217;s very much a two way street, later down the line everyone will appreciate your pestering and constant asking of questions. Working closely with these teams you can develop an understanding for each representative&#8217;s specific interests in the application, enabling you to understand and speak their language. </p>



<p>Putting in the effort to build these relationships and understand the team&#8217;s challenges will influence the quality of the product. Though it may seem very one sided. There are many situations where the tester will be called upon as well such as reproducing live issues from product owners, developers asking testers to create some test data, UX clarifying whether the designs are still up-to-date or data analysts requesting a dump of pre-production environment to run through their data pipeline.</p>



<h2 class="wp-block-heading" id="testers-everywhere"><span id="Testers_everywhere">Testers everywhere</span></h2>



<p>To wrap things up, testers pop up everywhere within the software development lifecycle (SDLC). Being curious is a key asset of the tester within the engineering function. Asking questions is another core skill to encourage conversations and discover unknown information. By participating in all the activities described here, a tester can discover interesting insights previously never discovered. </p>



<p>By collaborating with people across the engineering function, a tester can improve their communication with technical and non-technical people. Proactively exploring information from multiple sources helps to paint a clearer picture of the whole software development process and beyond.</p>



<p><button class="btn bg-primary cta-btn" style="margin: auto"><a style="color:#fff" href="https://github.com/testsigmahq/testsigma" target="_blank" rel="noopener noreferrer">Collaborate better on your test automation tasks with Testsigma, try it here.</a></button></p><br>



<p><strong>Related reads:</strong></p>



<p><a href="https://testsigma.com/blog/how-to-be-an-efficient-and-productive-software-tester/" target="_blank" rel="noreferrer noopener">How to be an efficient and productive software tester?</a></p>



<p><a href="https://testsigma.com/blog/how-to-be-an-open-minded-tester/" target="_blank" rel="noreferrer noopener">How To Be An Open-Minded Tester?</a></p>



<p><a href="https://testsigma.com/tools/software-testing-tools/" target="_blank" rel="noreferrer noopener">Different Types Of Tools To Help Make Tester&#8217;s Day-To-Day Life Easier</a></p>



<p><a href="https://testsigma.com/blog/15-must-have-skills-for-a-top-automation-tester/" target="_blank" rel="noreferrer noopener">15 Must Have Skills For a Top Automation Tester</a></p>



<p><a href="https://testsigma.com/blog/how-to-become-an-automation-tester/" target="_blank" rel="noreferrer noopener">How to Become an Automation Tester</a></p>



<p></p>
