Regression Testing

Regression testing (RT) which is coming under Manual Testing. RT perform during the system integration testing and also after the completion of SIT and UAT.  Regression testing performs after the defect is fixed or sometimes new functionality gets added to the application that time do the regression testing. It becomes necessary to check that there is no impact of these changes on the previously working functionality of the component.

We check the newly added functionality impact other module or not. We can goodly say that Regression testing to check whether the changed component has Affected the functionality of the existing module. Regression testing is done before the completion of UAT and after the completion of UAT.

Manual_Testing

User Acceptance Testing

Difference Between Retesting And Regression Testing

Retesting

At the time of performing Regression Testing, we focus on some ways like.

When new scenarios get added to a developed module that time we do the regression testing. Some failed test cases come from SIT and test cases check in this testing. High-priority, positive test cases check in this testing. sometimes time remaining after the completion of testing we check the low and medium-priority test cases. After getting CR means to change in a request that time we need to do regression. Because in the CR new requirement are come/new functionality gets added and sometimes some functionality removed. that’s why we do this testing.

Main Aim of the regression newly added module impact other modules or not we check and also check whether works well or not.

The actual process:

The new scenario adds, do the SIT after the SIT immediately we do the regression on that. For example, we add +91 before the mobile no. that is the scenario on that scenario performs SIT after that we do regression on that scenario.

Check fails test cases. New added module/functionality working well or not?

High-priority test cases. We check the high-priority test cases means related to the main functionality. If the remaining time then we check the low/medium test cases.

For example, In the pay-to-application new functionality gets added at sales time. after the end of the sale that functionality is removed. then we perform regression for checking the impact on the functions of another module. Give an example of a couple of code sales big billion sales of Flipkart etc.

Whenever we add any offer at a festival time, then remove it at that time we do the regression testing.

What is regression testing with example?

Regression testing which is comes under the manual testing. We do the regression testing basically two times during the system integration testing and also after the completion of SIT and UAT. We do the regression testing after defect are fixed or sometimes we new functionality get added into the application that time do the regression testing It becomes necessary to check that there is no impact of these changes on the previously working functionality of component .

Basically in regression testing we check the newly added functionality impact on other module or not. We can goodly say that Regression testing to check whether the changed component has Affected the functionality of existing module.. Regression testing is done before the completion of UAT and after the completion of UAT.

At the time of performing regression testing we focus on some ways like.

When new scenarios get added in developed module that time we do the regression testing. Some fail test cases comes from SIT that test cases check in this testing. High priority, positive test cases we check in this testing. Sometime time remaining after completion of testing we check the low and medium priority test cases. After getting CR means change in request that time we need to do regression. Because of in the CR new requirement are comes /new functionality get added and some time some functionality removed that’s why we do this testing.

Main Aim of the regression newly added module impact on other module or not we check and also we check that works well or not.

Example of Regression Testing

For example, In the pay tm application new functionality get added at sales time and after the end of sale that functionality is removed then we perform regression for checking impact on the functions of other module. Give example of couple code sales big billion sales of Flip kart etc.

Whenever we add any offer at festival time then remove it that time we do the regression testing

What is regression?

Regression testing is types of testing in software development life cycle. Regression testing is conducted on modified build to make sure there will not be impact on adding, deleting, modifying, features.

We do the regression testing after defect are fixed or sometimes we new functionality get added into the application that time do the regression testing It becomes necessary to check that there is no impact of these changes on the previously working functionality of component .

 

 

How does it work? Or Process of regression?

Actual process of regression testing.

New scenario add, do the SIT after the SIT immediate we do the regression on that. For example we add +91 before the mobile no. that is scenario on that scenario perform SIT after that we do regression on that scenario.

Check fails test cases. New added module/functionality working well or not.

High priority test cases. We check the high priority test cases means related to main functionality. If remaining the time then we check the low/medium test cases.

What are the types of regression? Or

What is the Technique of regression?

1.Normal Regression Testing :-

In the System and Integration testing (SIT) , when we got a defect that time do this  normal regression testing. We have not any changes in the build that time this technique performed.

2. Unit Regression Testing :-

Here we can check only changes and modification done by the developer.  Only check that impact on that functionality. When CR comes from client and modified existing functionality on that component we do this regression.

3.Regional regression testing :-

In regional regression testing done on modified build and also impacted (means that modified build is impact on other module that check in this testing) module . Change in Requirement and modified existing functionality then this regression done on that an also on the existing functionality.

4.Full Regression Testing :-

It is also known as end to end regression. We perform one round of full regression means, testing main feature and remaining part of application. When complete module moving from SIT to UAT that time final regression is done.

 

how to do regression testing? Or

 How is regression testing performed?

 

How do you do regression testing on data?

When new scenarios get added in developed module that time we do the regression testing. Some fail test cases comes from SIT that test cases check in this testing. High priority, positive test cases we check in this testing. Sometime time remaining after completion of testing we check the low and medium priority test cases. After getting CR means change in request that time we need to do

How regression testing is done manually?

Does regression testing need coding?

Regression testing is the part of manual testing. We do not need to the coding means doesn’t required any programming languages, like, c++, java, php, python etc. Regression testing done manually we only check that functionality work correctly or not.

 

 

Is regression testing done in UAT?

Regression testing it is not a part of UAT( user acceptance testing) . UAT- user acceptance testing it is a last part of the testing . Before performing UAT firstly done the regression. And after the completion of SIT Regression done.

 

 

When to apply the regression testing?

Why the regression testing important?