What is Regression Testing?
It is a type of testing where you can check the changes made in the codebase that do not affect the existing software functionality. For instance, such code changes might involve adding new features, bug fixes, updating current features, etc. In simple words, regression testing means re-executing previously passed test cases on the updated version of the apps to confirm that all features are still functioning properly. Moreover, regression testing is a series of tests that are conducted each time a new version is added to the codebase.Is It Possible To Perform Regression Testing Manually?

Examples of Regression Testing
Let’s take a web-based e-commerce platform as an example. Suppose the development team adds an enhancement to the search functionality, enabling users to filter the product by its color. Here’s how regression testing may be applied in such case:- Product Browsing: Apart from the changes made to the search functionality, users should still be able to browse through product categories, and check our product details and items in their cart without having any issues.
- Cart management: After adding a new search filter feature, regression testing ensures that people can still easily add, remove, or update items in the shopping carts.
- Checkout process: Confirmed that consumers can proceed via the checkout process smoothly, from entering shipping and billing information to completing the payment is pivotal. Regression testing ensures that this important functionality remains intact.
- User accounts: We need to test the user’s account management system to verify that they can still log in, update their profile, and check order history without having any issues with changes made.
- Mobile responsiveness: This testing may also involve checking the responsiveness of the platform across several devices and screen sizes to ensure the new search filter has not caused layout or usability problems on mobile devices.
What is Regression Testing?
It is a type of testing where you can check the changes made in the codebase that do not affect the existing software functionality. For instance, such code changes might involve adding new features, bug fixes, updating current features, etc. In simple words, regression testing means re-executing previously passed test cases on the updated version of the apps to confirm that all features are still functioning properly. Moreover, regression testing is a series of tests that are conducted each time a new version is added to the codebase.Is It Possible To Perform Regression Testing Manually?

Examples of Regression Testing
Let’s take a web-based e-commerce platform as an example. Suppose the development team adds an enhancement to the search functionality, enabling users to filter the product by its color. Here’s how regression testing may be applied in such case:- Product Browsing: Apart from the changes made to the search functionality, users should still be able to browse through product categories, and check our product details and items in their cart without having any issues.
- Cart management: After adding a new search filter feature, regression testing ensures that people can still easily add, remove, or update items in the shopping carts.
- Checkout process: Confirmed that consumers can proceed via the checkout process smoothly, from entering shipping and billing information to completing the payment is pivotal. Regression testing ensures that this important functionality remains intact.
- User accounts: We need to test the user’s account management system to verify that they can still log in, update their profile, and check order history without having any issues with changes made.
- Mobile responsiveness: This testing may also involve checking the responsiveness of the platform across several devices and screen sizes to ensure the new search filter has not caused layout or usability problems on mobile devices.
Disadvantages:
- Without automation, this type of testing takes more time.
- Testing is required for all small changes of code.
- A repetitive process of testing can affect agile sprint.
- Needs you to create complex test cases.