Parameterization in TestNG – Working with the testng.xml file

When it comes to testing through automation on a web application, Selenium is probably one of the primary choices for a tester. The rich library of methods that can detect and perform an action on any web element makes us wonder whether giving Selenium a try should be worth the effort. 



In addition, when the <a href="https://testsigma.com/blog/why-how-to-contribute-to-open-source-projects/" target="_blank" rel="noreferrer noopener">open-source</a> flag is seen waving high on a cloud repository, we are sure about our next steps and which way we are going through. This is not only my analysis of test automation and open-source inclination, but <a href="https://www.zarantech.com/blog/makes-selenium-hot-favorite-automation-tool-among-enterprises/" target="_blank" rel="noreferrer noopener nofollow">a lot of surveys</a> also point toward the same results:



<div class="wp-block-image"><figure class="aligncenter is-resized"><img loading="lazy" src="https://lh5.googleusercontent.com/6dQPOUX4lAs1NfLM_onCz_rEJFVGb8biUUEbVzdRDt2lIntuEmKIRsHvZBrQrx68KvN9fEqTY1xnBalh29g5OLur48aF9ysVVRfZPf1jK9xwHMxDmZjfPt24AGl6ygZDCrHOBMFHMCZ32IgJQZ87ZklZuTcX_tevxvh_K5E7W88LUFnW030I6RzRSA" alt="Automation Tools Usage" width="600" height="400"/></figure></div>



If we start discussing Selenium and its properties and everything it offers, we might end up covering up one book&#8217;s worth of material. Therefore, it is better to pick one of the most favorite and most used methods from the Selenium library and see how it helps us identify elements on a web page and take action on the results it returns. To demonstrate this and explore the process, we will use Selenium’s isDisplayed() method that tells us whether the element is displayed or not.&nbsp;



<div class="cta-banner-v2">
<div class="title-with-description ">
Automate your tests for web, mobile, desktop and APIs, without the need to code, with Testsigma 
</div>
<a href="https://testsigma.com/signup" target="_blank" class="cta-btn-v1" rel="noopener">Try for free</a>
</div>



<div id="toc_container" class="no_bullets">Table Of Contents<ul class="toc_list"><li><a href="#isDisplayed_Method_in_Selenium">1 isDisplayed() Method in Selenium</a></li><li><a href="#Do_We_Require_isDisplayed_Method_in_Selenium">2 Do We Require isDisplayed() Method in Selenium?</a></li><li><a href="#How_to_Use_isDisplayed_Method_in_Selenium">3 How to Use isDisplayed() Method in Selenium?</a></li><li><a href="#isEnabled_Method_in_Selenium">4 isEnabled() Method in Selenium</a></li><li><a href="#isSelected_Method_in_Selenium">5 isSelected() Method in Selenium</a></li><li><a href="#Conclusion">6 Conclusion</a></li><li><a href="#Suggested_Readings">7 Suggested Readings</a></li></ul></div>
<h2 id="h-isdisplayed-method-in-selenium">isDisplayed() Method in Selenium</h2>



Unlike biologists and anthropologists, computer software developers and scientists name concepts extremely close to what they would achieve. So, navigate().to would navigate us to the specified URL, findElement() will find an element, and switchTo().window() will switch to another window. 



Similarly, as you might have already guessed, isDisplayed() method in Selenium returns a boolean value telling us whether the element we are enquiring about is being displayed on the web page or not.&nbsp;



<h2 id="h-do-we-require-isdisplayed-method-in-selenium">Do We Require isDisplayed() Method in Selenium?</h2>



The first question that comes to mind is, do we need to dedicate one post to this method? Is this that important? I mean, not that I question the ability of Selenium Waits and the sense of relief it provides for the elements that load at different times, but can we rely on it entirely?<gwmw style="display:none;"></gwmw>



Let me rephrase the above sentence. If you have an element that does not load at the start, isn’t Selenium Waits enough to check if the element is available in the limited timeout we define in the method?&nbsp;



Selenium Waits let you wait for an element until it is visible (taking reference of a single use case out of many) on the web page. By its core nature, you have to wait for some time if you want to utilize this use case. I know you can implement waits with 0 value also, but calling internal functions and accessing multiple layers would increase the time of script execution.



As far as isDisplayed() is concerned, the method is instant and covers its own use case. Moreover, Selenium Waits do not return the boolean value as can be directly returned by the isDisplayed method in Selenium.



Know More: <a href="https://testsigma.com/blog/selenium-wait-for-page-to-load/" target="_blank" rel="noreferrer noopener">Page Loading in Selenium</a>



<h2 id="h-how-to-use-isdisplayed-method-in-selenium">How to Use isDisplayed() Method in Selenium?</h2>



The isDisplayed method is a simple to learn and execute method. This section will demonstrate how to use it inside your scripts and check for an element on the web page. As a prerequisite, you need to be familiar with the concepts of Selenium and basic working around it, such as initializing a web driver and using the web driver for accessing the web-related elements.



The syntax for isDisplayed method in Selenium is as follows:



&lt;webdriver instance&gt;.&lt;method to find element&gt;(&lt;property used&gt;(&lt;property symbol&gt;)).isDisplayed();



I know it looks a bit intimidating due to many variables, especially for people just starting their Selenium journey. But no need to worry about that. It becomes much simpler when we boil this down to individual elements and understand the syntax more clearly.



&lt;webdriver instance&gt;



The webdriver instance is the instance of the webdriver you are using in Selenium. The webdriver instance is declared as:



WebDriver driver = new FirefoxDriver();



If you are using a Firefox driver or:



WebDriver driver = new ChromeDriver();



If you are using a Google Chrome driver.



&lt;method to find element&gt;



Here, we will ask Selenium to find an element. For this, we will use a method built into the Selenium library for finding an element such as findElement.



&lt;property used&gt;



After writing the method to find an element, we need to tell Selenium the property by which we are looking for that particular element. So, if I am finding an element with “div-header,” is it an ID? A class? Or a name property? Therefore, this is important to distinguish the two elements. In Selenium, you can use the following properties to find the element:



<ul><li>Id</li><li>ClassName</li><li>CSS</li><li>Name</li><li>TagName</li><li>Xpath</li><li>LinkText</li><li>PartialLinkText</li></ul>



After placing each of the values in the above attributes, our line of code for isDisplayed() method in Selenium would look as follows:



boolean isElementVisible = driver.findElement(By.id(&#8220;myHeaderDiv&#8221;)).isDisplayed();



Combining all the elements of code, we get the following snippet:



import org.junit.Test;



import org.openqa.selenium.By;



import org.openqa.selenium.WebDriver;



import org.openqa.selenium.chrome.ChromeDriver;



public class TestSigma {



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;protected WebDriver driver;



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;@Test



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;public void check_if_displayed()



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;driver = new ChromeDriver();



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;driver.navigate().to(&#8220;https://testsigma.com/blog/strings-in-javascript&#8221;);



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;boolean isElementVisible = driver.findElement(By.linkText(&#8220;Harish Rajora&#8221;)).isDisplayed();



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;System.out.println(&#8220;We found the element – &#8221; + isElementVisible);



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;driver.close();



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}



&nbsp;&nbsp;&nbsp;&nbsp;}



Here, I am using the linkText through findElement, which can find the text of a link. As expected, the result shown is true. Please note that we have used @Test annotations to work out this test. If you are unfamiliar with this, do read a detailed explanation on Parameterization in the TestNG post.



<h2 id="h-isenabled-method-in-selenium">isEnabled() Method in Selenium</h2>



Since we are talking about finding elements on a web page, we may as well touch upon two more methods that are implemented with the same intentions.&nbsp;



The isEnabled() method in Selenium is used to find out whether an element is enabled on the web page (in the current browsing context) or not. The syntax of this method is as follows:



&lt;webdriver instance&gt;.&lt;method to find element&gt;(&lt;property used&gt;(&lt;property symbol&gt;)).isEnabled();



All the parameter attribute values remain the same as in isDisplayed method.



In the previous section, we verified whether the link text is displayed or not. Since it is a link, we can use the same code with the isEnabled() method in Selenium as follows:



import org.junit.Test;



import org.openqa.selenium.By;



import org.openqa.selenium.WebDriver;



import org.openqa.selenium.chrome.ChromeDriver;



public class TestSigma {



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;protected WebDriver driver;



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;@Test



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;public void check_if_enabled()



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;driver = new ChromeDriver();



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;driver.navigate().to(&#8220;https://testsigma.com/blog/strings-in-javascript&#8221;);



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;boolean isElementEnabled = driver.findElement(By.linkText(&#8220;Harish Rajora&#8221;)).isEnabled();



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;System.out.println(&#8220;We found the element – &#8221; + isElementVisible);



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;driver.close();



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}



&nbsp;&nbsp;&nbsp;&nbsp;}



This will also return the value true. This method is generally used for elements that are disabled depending on situations such as disabling the submit button unless the form is completely filled.



<h2 id="h-isselected-method-in-selenium">isSelected() Method in Selenium</h2>



The final element that we will consider in this post is the isSelected() method in Selenium. As its name suggests, the isSelected() method is used to find out whether an element is selected on the web page or not. With reference to the above two stated methods, this method resembles a lot in the syntax and the working. The syntax of the isSelected() method in Selenium is as follows:



&lt;webdriver instance&gt;.&lt;method to find element&gt;(&lt;property used&gt;(&lt;property symbol&gt;)).isSelected();



The meaning of various attributes defined in the syntax remains the same. The usage of isSelected is also extremely similar to the above:



import org.junit.Test;



import org.openqa.selenium.By;



import org.openqa.selenium.WebDriver;



import org.openqa.selenium.chrome.ChromeDriver;



public class TestSigma {



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;protected WebDriver driver;



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;@Test



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;public void check_if_selected()



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;driver = new ChromeDriver();



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;driver.navigate().to(&#8220;https://testsigma.com/blog/strings-in-javascript&#8221;);



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;boolean isElementSelected = driver.findElement(By.cssSelector(&#8220;input[type=&#8217;checkbox&#8217;]:indian-national&#8221;)).isSelected();



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;System.out.println(&#8220;We found the element – &#8221; + isElementVisible);



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;driver.close();



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}



&nbsp;&nbsp;&nbsp;&nbsp;}



Since the element differs from the one used in isEnabled() method, we have used cssSelector instead. If there are any doubts about the program execution, do let us know in the comment section, and we will be happy to clarify them.



Also, please note that the primary use case of the isSelected method in Selenium is around the elements that can be selected or are “checkable.” For example, this method will be most suitable to find out if a radio button is checked or a checkbox is checked or not, etc.



<h2 id="h-conclusion">Conclusion</h2>



Selenium is inarguably one of the best platforms for scripted testing in the market. Even though credit goes out to its open-source nature and the large community that supports us in every hurdle, a lot of other things contribute to its success too. 



For instance, developers have always maintained a habit of listening to testers and implementing the most demanding features as soon as possible. They have also kept the concepts and the working of each method considerably simple compared to other frameworks. In this post, we tried to pick out three such things from the large pool and see how they can help us in testing web applications faster and more efficiently.



The isDisplayed() method in Selenium is used to test whether the referenced element is displayed on the web page or not. It returns a boolean value and can be used with any locator found in Selenium. Unlike Selenium Waits, the result is instant and requires fewer calls within. 



In addition, we discussed two more similar functions that are used exactly the same way as isDisplayed method with specific use cases. For instance, if you are using isEnabled() method in Selenium, its expertise falls within links, buttons, etc., that can be enabled. 



Similarly, isSelected() method works best where there are checkable elements on the web page. Apart from these three methods, you can use getTagName, getRect, etc. methods to get element-specific information. However, their motive deviates us from the essence of this post, and so we would like to wrap things up here.



Please let us know in the comment section if you have any suggestions, queries, or comments. Thank you for giving this post your valuable time.&nbsp;



<div class="cta-banner-v2">
<div class="title-with-description ">
Automate your tests for web, mobile, desktop and APIs, without the need to code, with Testsigma 
</div>
<a href="https://testsigma.com/signup" target="_blank" class="cta-btn-v1" rel="noopener">Try for free</a>
</div>



<h2 id="suggested-readings">Suggested Readings</h2>



<a href="https://testsigma.com/blog/sendkeys-selenium/" target="_blank" rel="noreferrer noopener">Selenium SendKeys: A Detailed Usage Guide</a>&nbsp;&nbsp;



<a href="https://testsigma.com/blog/selenium-get-current-url/" target="_blank" rel="noreferrer noopener">Selenium Get Current URL using Java: Tutorial</a>&nbsp;&nbsp;



<a href="https://testsigma.com/blog/selenium-headless/" target="_blank" rel="noreferrer noopener">Selenium Headless Tests on Browsers</a>



<a href="https://testsigma.com/blog/python-selenium-example/" target="_blank" rel="noreferrer noopener">Selenium with Python Tutorial</a>

How does Selenium isDisplayed() method work?

How Does Selenium isDisplayed() Method Work?

A Complete Guide to ETL Test Automation

How to Wait For Page to Load using Selenium

How to Get Selenium Wait for Page to Load [Updated]

It has often been observed that a manual tester does not really know the direction he should take to start his career in automation testing. With many tools available today, getting distracted and unable to decide how to start learning test automation is obvious. In this blog, we shall see how to streamline things so that you can learn automation testing at ease and without any Stress.



It is evident that because of a lack of clarity on such things, you cannot take that first step towards learning test automation. If you are new to automation testing, you can relate to what I am saying here. But, if you already have some experience in automation testing, this would help your fellow aspiring testers who aim to make their career in automation testing, or you can refer them to this article so that it will be beneficial for them.



<div id="toc_container" class="no_bullets">Table Of Contents<ul class="toc_list"><li><a href="#Mandatory_Steps_to_Become_an_Automation_Tester">1 Mandatory Steps to Become an Automation Tester </a></li><li><a href="#Software_Testing_Concepts">2 Software Testing Concepts</a></li><li><a href="#Programming_Languages">3 Programming Languages</a></li><li><a href="#Automation_Toolsnbsp">4 Automation Tools:&nbsp;</a></li><li><a href="#Web_Automation_Testing">5 Web Automation Testing:</a></li><li><a href="#Mobile_Automation_Testing">6 Mobile Automation Testing:</a></li><li><a href="#Performance_Testingnbsp">7 Performance Testing:&nbsp;</a></li><li><a href="#CICD_Pipeline">8 CI/CD Pipeline:</a></li><li><a href="#Approach_to_Learning_Automation_Testing">9 Approach to Learning Automation Testing:</a></li><li><a href="#Conclusion">10 Conclusion:</a></li></ul></div>
<h2 id="mandatory-steps-to-become-an-automation-tester">Mandatory Steps to Become an Automation Tester </h2>



To start learning automation testing, first, you must believe that you can do it. Nothing is impossible in this world if we are determined to do so. I know you won&#8217;t believe me. Keep reading, and you will see the answer. So, make up your mind before you continue reading the article.



Start your career in automation testing, and switch from a manual testing career to an automation testing profile by referring to this blog.&nbsp;



In this article, you&#8217;ll learn the tips, techniques, and approaches to learning test automation. Based on my real-time experience working in Software Test Automation Industry, I will be jotting down all the points for you to take care of, which will help you make a start and make you confident.&nbsp;



Get your tester horse to work! Take up the challenge.



<h2 id="software-testing-concepts">Software Testing Concepts</h2>



Software Testing concepts are a MUST to know for any tester, whether you are a manual tester or an automation tester. It includes the below:



<ol><li>Manual Testing concepts&nbsp;</li><li>Agile methodology, Scrum framework (widely used and known)</li><li>Defect tracking tool</li><li>Test Management tool</li></ol>



<h2 id="programming-languages">Programming Languages</h2>



Being a&nbsp; tester, you must know at least one programming language. One such language is Java which is widely used worldwide. Learning the basics completes the first step.



If you know the basics of any programming language or if you have created a project in your college, you can prepare more on that specific language and get expertise. If you know Java already, it is suggested to learn another programming language which will act as a bonus for you.&nbsp;



Having said that, if you are new to the programming world, then you can choose Python as your choice as it’s easy to learn comparatively.&nbsp;



<h2 id="h-automation-tools">Automation Tools:&nbsp;</h2>



Now, you must consider which tool you should learn to start your automation testing journey.



When you want to learn automation testing, you can go to any specific area like web automation, mobile application, API, Cloud, Performance, etc. There are automation tools available for each particular type of testing.&nbsp;



<h2 id="h-web-automation-testing">Web Automation Testing:</h2>



For web automation testing, I can suggest going with Selenium or Cypress. Depending on your chosen programming language, you can pick up the tool. You can go with Selenium with Java or Selenium with Python etc. Similarly, you can decide on other combinations as per your learning pace.&nbsp;



<h2 id="h-mobile-automation-testing">Mobile Automation Testing:</h2>



If you are inclined toward Mobile automation, you can start learning the Appium tool. But, again, if you are serious about making a career in mobile automation, you must understand mobile application testing (manually) before moving to mobile automation testing.&nbsp;



<h2 id="h-performance-testing">Performance Testing:&nbsp;</h2>



For Performance testing, we have JMeter, Neoload, etc. In contrast, NeoLoad is a powerful load and performance testing software solution designed for web and mobile applications. Jmeter is used for application&#8217;s load or performance testing. It is used to identify the bottleneck in the performance and improve the user experience.&nbsp;



<h2 id="h-ci-cd-pipeline">CI/CD Pipeline:</h2>



To be good at automation testing, you must know what CI/CD is. What does it entail? The purpose and the requirement should be clear to you first before understanding the basics of these tools. We have Jenkins available with us for CI. You also need to know about Maven, Gradle, GitHub, Git, Docker, etc.



<h2 id="h-approach-to-learning-automation-testing">Approach to Learning Automation Testing:</h2>



Let me share my approach, which I implemented when learning automation testing.&nbsp;Please note that the below points are not in order, and try to follow them daily.&nbsp;



1. Be strongly determined that you want to learn it.



2. Dedicate 1–2 hrs. each day to learn it.



3. Start from the very basics of any tool because when your basics are strong, you can quickly learn all advanced concepts.



4. While learning some concepts, make notes and explore more learning materials on the <a href="https://www.studocu.com/in" target="_blank" rel="noreferrer noopener">StuDocu</a> platform parallelly irrespective of whether it is basic knowledge, a programming language, or any automation tool, for example, Selenium.



5. If you are not working, then you can&#8217;t complain about timings. Spend 2–4 hrs. daily to learn.



6. After you learn, do hands-on on your personal computer without looking into a solution. It&#8217;s okay to go slow but don&#8217;t cheat. Remember, you are learning for yourself, not for others.



7. Next day, when you start a new topic, practice and revise what you learned on day 1. Check your hands-on exercises.



8. Keep following the same routine until you feel confident about yourself or for a minimum 3–4 months (religiously study).



9. Be serious about it. Have a goal in life and achieve it. It&#8217;s your life. Design the way you want it to be.



<h2 id="h-conclusion">Conclusion:</h2>



You can save these tips and share them with your friends looking to make a career in automation testing or who want to be automation testers. This will serve as a guide to you and them too. Also, please do not forget to come back to this blog after 4-5 months when you are prepared to embark on a test automation journey, and leave a comment for me to share your experience of becoming an automation tester.&nbsp;



I would be happy to hear all your success stories. Good Luck!&nbsp;

How to become an automation tester with no stress?

How to Become an Automation Tester with No Stress?

The Step After Automation: Top 6 Reasons to Invest in DevOps Orchestration

Automation and Orchestration: 6 Reasons Why to Invest in DevOps Orchestration

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.



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



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



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;



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



<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 id="negative-vs-positive-testing-examples-of-test-scenarios">Negative vs Positive Testing – Examples of Test Scenarios</h2>



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



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



<figure class="wp-block-table"><table><tbody><tr><td>Positive Test Scenarios</td><td>Negative Test Scenarios</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 id="negative-vs-positive-testing">Negative vs Positive Testing</h2>



In this session, let us discuss some key differences. &nbsp;



<h2><img loading="lazy" 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>Positive Testing</td><td>Negative Testing</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>



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.



<h2 id="positive-testing-vs-negative-testing-similarities">Positive Testing vs Negative Testing- Similarities</h2>



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;



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



Commonalities:



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



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



Documentation: Both require clear documentation of test cases, expected results and identified bugs.



Test Case Design: 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.



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



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;



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



The approach to testing is the following:



Testing boundary values (for example, in a field expecting a small integer, you are expected to put down a very large number), invalid data formats and situations of error, 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.



Balancing Negative with Positive Testing:&nbsp;



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;



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.



Additional Resources:



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.



<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 id="conclusion">Conclusion</h2>



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



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.



<div class="cta-banner-v2">
<div class="title-with-description ">
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.
</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

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. Software 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 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).&nbsp; 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 and well within the stages of software testing.



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.



<div id="toc_container" class="no_bullets">Table Of Contents<ul class="toc_list"><li><a href="#WHAT_DID_A_TEA_CUP_TEACH_ME_ABOUT_USER_EXPERIENCE">1 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">2 LESSON 1 &#8211; DO NOT COMPROMISE ON FUNCTIONALITY FOR AESTHETICS.&nbsp;</a></li><li><a href="#HOW_POOR_DESIGN_RUINED_MY_MOVIE_EXPERIENCE">3 HOW POOR DESIGN RUINED MY MOVIE EXPERIENCE</a></li><li><a href="#LESSON_2_8211_SIZE_MATTERS_IN_THE_VISUAL_HIERARCHYnbsp">4 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">5 LESSON 3 &#8211; MATCH BETWEEN THE SYSTEM AND THE REAL WORLD&nbsp;</a></li><li><a href="#CONCLUSION">6 CONCLUSION</a></li></ul></div>
<h2 id="what-did-a-tea-cup-teach-me-about-user-experience">WHAT DID A TEA CUP TEACH ME ABOUT USER EXPERIENCE?</h2>



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. 



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;



<div class="wp-block-image"><figure class="aligncenter is-resized"><img loading="lazy" src="https://lh3.googleusercontent.com/kOeHXAcBhKFN8gf5wZpqI8mMssJgKeuTp37lQfsyz3QNVrsIKXEMbS0Y7m2qTAlnQVh8pROLIlxQm8YQVRtD8lL121fISspBVzQow7NjS01Q1br9KHaltr-IqFuNYaOroQv9VMc1sqPkFbuJZVPwlmc" alt="WHAT DID A TEA CUP TEACH ME ABOUT USER EXPERIENCE? 1" width="400" height="400" /></figure></div>



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.



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.



<div class="wp-block-image"><figure class="aligncenter is-resized"><img loading="lazy" src="https://lh5.googleusercontent.com/zpNsnKHVmEg4sJj1s2DBBs5CsSS3ulfx3f1L3w8y4-ZTtfvJCFjp89lKAOKwSCVLZr3dYOz8cutFKBR7UMWlPsVdLbXptRMU9_gM1JbDsoWs4aswo8_adTqHt6hb_OB39aYB0o3gtCPLuDSqEeIeajQ" alt="WHAT DID A TEA CUP TEACH ME ABOUT USER EXPERIENCE? 2" width="300" height="400" /></figure></div>



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



<div class="wp-block-image"><figure class="aligncenter is-resized"><img loading="lazy" src="https://lh6.googleusercontent.com/Lz-3AUiPkruE-jrg6j7i6XZy_ENMXq3Lf4s4Z-rotxpD_kYEUi7IQ5J9AS8OVATwJJKts_o5VJ1YnegJnLEzvaPCCZqPz_MeNwPNgneaMDYQEFk9ti6I2CoA7iy9ntFPYMZ6Hlrg08x5mwx5jCcsDvE" alt=" DO NOT COMPROMISE ON FUNCTIONALITY FOR AESTHETICS." width="400" height="400" /><figcaption>Graphic by Regex SEO</figcaption></figure></div>



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 Functionality. Always put the user at the center of everything that you do.



Think,



Is your product choosing Visuals Over Functionality?&nbsp;



Is focusing on flashy interfaces over interactions?&nbsp;



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;



<h2 id="how-poor-design-ruined-my-movie-experience">HOW POOR DESIGN RUINED MY MOVIE EXPERIENCE</h2>



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. 



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. 



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;



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.



<div class="wp-block-image"><figure class="aligncenter is-resized"><img loading="lazy" src="https://lh3.googleusercontent.com/xASGeddjZjShuxyTyE-ikzNe3WbnRmyioHrbaFHcFdIN6ga-QVQfdLxZOlz6yi4aKm9DSptCyyiXW9mN6tPWgz6RTMd1CDsLAemkNYzGTgAgd44-QMTszCOeqXrOrjQb8G0wFpcoxSJpUAy6KIYKAnM" alt="HOW POOR DESIGN RUINED MY MOVIE EXPERIENCE" width="400" height="400" /></figure></div>



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.



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



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.



<div class="wp-block-image"><figure class="aligncenter is-resized"><img loading="lazy" src="https://lh6.googleusercontent.com/dPARTdNmDsj9pAwgZNsBeYOgC2fLbFIX0xMeLpx5eni8xdECInfUuVdwbesA4-jwY0Xx4BGdmKkn6UYWwbEiiev191qlM-8ewaDT3_JmOXRv8l2Cz1WL1OGVSjbIdqWKC-rx9OAxXhY7phizqlzQYVI" alt="SIZE MATTERS IN THE VISUAL HIERARCHY" width="400" height="400" /></figure></div>



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.



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;



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



While testing your software, ask yourself these questions:



<ul class="list_style_disc"><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>



As a tester, always keep the audience&#8217;s needs in mind and help create designs that will have the desired impact.



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.



<div class="wp-block-image"><figure class="aligncenter is-resized"><img loading="lazy" src="https://lh5.googleusercontent.com/cwqnLVmLlIizriOfvDPtKuMAS0g5s0rcxzK1Dni0K5iD-5HjV9USI78LLcRTGmcnzRnZYdlq-NHmfwJk_Xx9UM84ceAzxZWVCdnHcgLtBI7aZ4mYjeJQowQBbbbRdnNMpw83fb_M3FmfEKJkJJEjt58" 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 id="lesson-3-match-between-the-system-and-the-real-world">LESSON 3 &#8211; MATCH BETWEEN THE SYSTEM AND THE REAL WORLD&nbsp;</h2>



<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”. 



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;



<div class="wp-block-image"><figure class="aligncenter is-resized"><img loading="lazy" src="https://lh4.googleusercontent.com/20hrbZQQTRSteW3Umqd71nHDcwicBxaeT-RtSEYCjiE2YizZkeC_n58fb9sUrMRST6LrYlmnPdZBLrmctgP-ybnrEdrj7KdUbIjm_g8DShEUdOL0yShPYm4idp78zOms8ptHT1Wtrv1JhyXZV8cetj4" 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" src="https://lh3.googleusercontent.com/FJjTxYHG4LM7MEv35FeWzBLHh-hOHPmmHWmMxRthWrCFx80f6wrUqDERdwCq1mp_kZ0jOoKCxLkkecuAI3z-O_6NkMk_juyg4guhSkD-nm-BgbYBjlX4S9GlWkFIVFd6D6-mVWmKfxn0KkqTbFQaKrw" alt=" MATCH BETWEEN THE SYSTEM AND THE REAL WORLD 2" width="400" height="400" /></figure></div>



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.



Before we conclude, here are a few amusing examples of poor design.



<img style="width: 300px" src="https://lh4.googleusercontent.com/wNejDfCSfWc5z2HdOcbYAMzVKf4X5pE9jtSLcF3syxoxtbgjl1pvuWADoTKah2RBNLBbjtbmHRHc10vW_VREXpjqXvD6LsCjr8SqUrT15ezT5-2M4cJf_liZBjIbc9zn_yM-mYZGU3-Q_kStgfuL8Dk" alt="Testsigma - HOW POOR DESIGN RUINED MY MOVIE EXPERIENCE">



<img style="width: 300px" src="https://lh4.googleusercontent.com/6y9HQJNkDv5Wqm0YrtYA4A6lAsYVTRzTnH5ITSOr5cPR0l9I5v_7NOPYPFzwK3McLPaQybFK3qa3JtAUq-EZK7Y2aZe3x5C2ghInP-w1NJTURq05tjRWwf12eCKSIyr9UE_6SnbT-VxaZ-e3meikLNY" alt="Testsigma - HOW POOR DESIGN RUINED MY MOVIE EXPERIENCE">



I believe I need not explain why I poured curd into my tea.



<div class="wp-block-image"><figure class="aligncenter is-resized"><img loading="lazy" src="https://lh6.googleusercontent.com/fMavBSIPlUz5HyvM_6szZwlqoDgzE9QmLj1c8C6KpEDCuCMQbLhNx4Ieg5OMFqaVOqSQH_EdUjJCWPSRKIbVSIdkNd-9QcF8EXwU_OkyMuj90T15ZQgmZZMvp0AFPjw7Sb6R-USquRI-cpUHQ3-_PF4" alt="amusing examples of poor design 3" width="300" height="300" /></figure></div>



It&#8217;s no surprise that the lights come on while someone is at the sink.



<div class="wp-block-image"><figure class="aligncenter is-resized"><img loading="lazy" src="https://lh6.googleusercontent.com/hHrxjNQnwqjCyHaOOLUxupz91zFL2yX1N_DEweyaQR4fpQkIOOWauCv-yTNI-RgmYqrlmnMum7LQEKn9-Otqfj-rPDog1deG6ZBJvXeMR5m0M9VOMhzaEWJmbgaZA8Mv_HHWEwh_5QIAudj7IZOMjqo" alt="amusing examples of poor design 4" width="400" height="400" /><figcaption>A secret door to escape from the sink?</figcaption></figure></div>



<h2 id="conclusion">CONCLUSION</h2>



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. 



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.



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.



<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>



<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.



Read more about Mobile usability testing here: <a href="https://testsigma.com/blog/mobile-usability-testing-what-is-it-and-how-is-it-done/" target="_blank" rel="noreferrer noopener">https://testsigma.com/blog/mobile-usability-testing-what-is-it-and-how-is-it-done/</a>



PC: <a href="https://www.freepik.com/" target="_blank" rel="noreferrer noopener nofollow">freepik</a>

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

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

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.



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.



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



False Positives are commonly observed due to:



<ul><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>



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



<ul><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" id="h-common-causes-of-false-positives-in-software-testing">Common Causes of False Positives in Software Testing</h2>



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



<h3 id="1-flaky-test-automation-scripts">1. Flaky Test Automation Scripts: </h3>



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:



i. Poor design of test scripts



ii. Non-modular / non-maintainable code structure



iii. Non-clean code



iv. Poor testability of the application



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



<h3 id="2-changing-locators-automation-hooks">2. Changing Locators (Automation Hooks): </h3>



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:



i. XPaths



ii. JSON Paths



iii. XML Paths, etc.



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



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:



i. The current and changing state of the system 



ii. Dependent processes and their effects on the test environment



iii. Version changes



iv. Breaking contracts



<h3 id="4-impractical-test-sequence">4. Impractical Test Sequence: </h3>



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.



Write Software &#8211;&gt; Read Software



Delete Software &#8211;&gt; Read Software



<h3 id="5-configuration-issues">5. Configuration Issues: </h3>



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



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?



<h3 id="6-script-development-execution-on-one-specific-machine">6. Script Development &amp; Execution on one specific machine: </h3>



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.



<h2 class="has-text-align-left" id="h-impact-of-false-positives">Impact of False Positives</h2>



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:



1. Loss of time:&nbsp;



i. In going through logs



ii. In investigating the problem



iii. In reproducing the test steps



iv. In fixing the test scripts, environment, etc.



2. Noise in Automated Testing Cycles



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



4. Defocus on the actual information gathering process (testing)



“The more you go in one direction, the far you go from the opposite direction.”



Jerry Weinberg



<div class="cta-banner-v2">
<div class="title-with-description ">
Automate your tests for Web, Mobile, Desktop and APIs on Cloud with Testsigma. No setup required.
</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" id="h-avoiding-false-positives-in-software-testing">Avoiding False Positives in Software Testing</h2>



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:



<h3 id="1-auto-healing-locators">1. Auto-Healing Locators: </h3>



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">Testsigma</a> provides the facility of auto-healing locators by default.&nbsp;



<h3 id="2-robust-locators-automation-hooks">2. Robust Locators (Automation Hooks): </h3>



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;



<h3 id="3-automatic-retry-rerun-s">3. Automatic Retry / Rerun(s): </h3>



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.



<h3 id="4-scheduling-test-runs-periodically-to-ascertain-stability">4. Scheduling test runs periodically to ascertain stability: </h3>



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.



<h3 id="5-develop-execute-on-separate-machines">5. Develop &amp; execute on separate machines: </h3>



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>



<h3 id="6-plan-testing-across-layers">6. Plan Testing across Layers: </h3>



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



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



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



1. Resetting State



2. Using Hooks



i. Setup 



ii. Teardown 



3. Spinning up docker containers, etc. 



<h3 id="8-verbose-logging-observability">8. Verbose Logging &amp; Observability</h3>



<h3 id="9-using-contract-verification-scripts">9. Using Contract Verification Scripts: </h3>



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:



i. Monitor Contracts



ii. Monitor Dependencies



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>.



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



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



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>

Software Test Automation False Positives & How to Avoid Them