Maintenance Testing and Regression Testing | Requirement, Limitations and Techniques of Regression Testing

Maintenance Testing and Regression Testing

Maintenance Testing and Regression Testing has been described in this section of Software Testing Concepts. Generally, maintenance test performed and followed by regression test run

Regression Testing is done to confirm the existing functionality is working fine with efficiently or not for newly changes made. Here testing confirm the side effect of changes made in software. To confirm the properly that recent program or code changes are not adversely affecting the already working functionality.

In this testing, Tester makes sure that changes made in code should not have any side effects for existing functionality. So we can say that it is just ensuring to confirm the old code is still working properly or not after the newly changed code implemented.

Requirement of Regression Testing:

i.                    When client change the requirement or any other changes made by developers then Regression Testing required.

ii.                  When newly updates have been done in software or newly feature added then it require.

iii.                In bug fixing when any bug has been fix and project come for next round testing.

iv.                If there is any performance issue, then regression is required on its fix

Techniques of Regression Testing:

Maintenance of Software is the process of optimization, deletion, error corrections and enhancements of any program feature. Software can be interrupted due to these changes. Therefore at that time, Regression Testing required and we can use following techniques for regression:

i.                    Retest all scenarios/test cases: In this technique all test cases will be followed mean available all test cases will be executed and confirm the existing functionality properly.

ii.                  Selection of Test Cases: In this point we will select only required test cases and execute those only instead of executing all the test cases. By this way we will save time.

iii.                Prioritization of Scenarios/Test Cases: In this point we will prioritize the test cases according to requirement and urgency of software, and then executed only those scenarios and test cases.

Regression Testing Techniques

Limitations of Regression Testing:

i.                    Very Time Consuming Activity: Regression testing is very time consuming activity. It performed after all types of changes which take so much time.

ii.                  Costly: Due to required process it also needs to perform on every change, so regression testing is also a costly activity.

iii.                Time and Budget Constraint: Tester is not able to execute all the required test cases due to time and budget constraint.

Software Testing Principle	Software Development Life Cycle	Unit Testing
Integration Testing	System Acceptance Testing	Sanity and Smoke Testing
Regression Testing	Non Functional Testing	Test Case
Test Scenario	Software Testing Rules	SQL For Software Testing
Test Case Design and Example	Test Base	Traceability Matrix
Boundary Value analysis	Decision Table in Software Testing	State Transition Definition
Use Case Testing	Testing Review	Techniques of Test Estimation
Test Plan Structure	Definition of Bug	Bug Life Cycle
Automation Testing Tools	Test Web Based Application	Software Testing Types

maintenance testing, regression testing, limitations of regression testing, techniques of regression testing, requirement of regression testing and maintenance testing

MOBILE APPS    QTP TESTING QUESTIONS  MANUAL TESTING  ANDROID APPS