Should we add Negative Test Cases to Regression Testing?

 


Adding negative test cases to regression testing depends upon the project scope and requirements.

However, following are a few key factors that help in identifying the test cases for your regression test suite:

1. Altered pieces of code are frequently covered: Frequent changes are undertaken in many parts of the software. These parts are more prone to defects and hence should be included in the regression suite. Those test cases should be included for functionalities that have been changed recently. 

 

2. Business-critical functionalities are covered: The core aspects of the software can be identified based on the business requirements document. All the test cases should be included in the regression test that covers these core functions. A traceability matrix can also be used so that all the high-priority cases can be rounded up. 

 

3. Bugs are yielded frequently: Those test cases should be identified that fail more frequently over the production cycle. These test cases cover those areas of the software that usually malfunction after a change or are fragile. The prioritization of these cases needed to be done and should be added to the regression test suite.

 

4. Leveraging complex test cases: Complex pathways that involve GUI sequences take care of many of the system functionalities. As the system becomes complicated, problems may arise in sequencing. Hence, regression tests should also cover complex test cases.

A risk-based testing approach can be used, wherein the ranking of test cases is done based on certain factors and then selected based on priority. These prioritized tests guarantee cost savings, effort and time.

 

Test cases can be simplified into three classes as follows:

l  Low priority: This comes last in the priority list and should be included based on necessity

l  Medium priority: This includes complex test cases and negative test case scenarios. The business value can also be significantly impacted by these test cases

l  High priority: Error-prone modules, business-critical functionalities and those modules that have been recently changed are taken into consideration.

Comments

Post a Comment

Popular posts from this blog

Regression testing vs. UAT: Know the difference?

Image
  Regression testing and User Acceptance Testing (UAT) play a key role in developing a quality product. Regression testing ensures that the functionality of the software product or application is working as per the expected requirements, despite changes being made in the code.  User Acceptance Testing is involved in ascertaining whether the product meets business and user-specific requirements. In this article, you will get to know what are the differences between regression testing and user acceptance testing. What is Regression testing Definition? It is a testing method that verifies the new changes made to the code do not alter or modify the existing functionalities. This testing method makes sure that the existing functionalities do not get altered or modified, despite changes being introduced in the code.  Whenever a code change happens during the software application development process, regression testing is performed. This testing method checks the overall functionality an
Read more

Regression Test Automation: A Quickstart Guide

Image
  The strategic need to automate regression testing: In many business scenarios, cost and time constraints are faced by organizations due to high-end software development and testing activities. This is because the mobile/web applications need to be thoroughly tested before they are released. When software goes through many changes for a release, there is a possibility for regressions (bugs found in the previous working functionality) to occur. When the functionalities of a software product have regressions then it may scale up the development costs and affect the software release deadlines. For this purpose, regression testing is conducted. But, when regression testing is conducted manually by the team, it consumes a lot of time. Hence, there is a need to automate regression testing.  When regression test cases are automated, the tester's time is saved from checking for regressions that have occurred due to the updates and changes that have been made in the application. Those test
Read more

How To Write A Regression Test Plan: Best Practices & Checklist For Effective Regression Testing

Writing a regression test plan is crucial for ensuring the stability and reliability of software applications, especially when changes are introduced.  Here are some best practices and a checklist to guide you in creating an effective regression test plan: Best Practices: 1.     Understand the Application: Gain a deep understanding of the application, including its features, functionalities, and critical areas. This knowledge is essential for identifying key regression test scenarios. 2.     Prioritize Test Cases: Prioritize test cases based on criticality, business impact, and the likelihood of being affected by changes. This helps focus regression testing efforts on the most important areas. 3.     Automate Repetitive Tests: Identify repetitive and time-consuming test cases that can be automated. Automation helps in faster execution, allowing more time for exploratory testing and focusing on complex scenarios. 4.     Create a Regression Test Suite: Build a comprehen
Read more