Regression Testing is carried out both manually and automation. The automatic tools are mainly used for the Regression Testing as this is mainly focused repeatedly testing the same application for the changes the application gone through for the new functionality, after fixing the previous bugs, any new changes in the design etc. The regression testing involves executing the test cases, which we ran for finding the defects. Whenever any change takes place in the Application we should make sure, the previous functionality is still available without any break.
For this reason one should do the regression testing on the application by running/executing the previously written test cases.
Regression testing will be conducted after any bug fixed or any functionality changed. During defect fixing procedure some part of coding may be changed or functionality may be manipulated.In this case the old testcases will be updated or completely re written according to new features of the application where bug fixed area.
The possible areas:
a. Old test cases will be executed as usual
b. Some new testcases will be added to existing test cases
c. Some testcases may be deleted.
egression Testing is carried out both manually and automation. The automatic tools are mainly used for the Regression Testing as this is mainly focused repeatedly testing the same application for the changes the application gone through for the new functionality, after fixing the previous bugs, any new changes in the design etc. The regression testing involves executing the test cases, which we ran for finding the defects. Whenever any change takes place in the Application we should make sure, the previous functionality is still available without any break. For this reason one should do the regression testing on the application by running/executing the previously written test cases.
Regression Testing, whenever u add some functionality and change something in the already tested application then we perform the regression testing to ensure the stability of the application procedure for regression testing.
After the bug was fixed, we have to test the application to ensure its stability i.e we have to test whether the bug is really rectified or it provides any side effects. After that only we start further testing on the application.
Name itself suggest that, is any changed component has make any affect on unchange componment called as regression testing and it is done when any functionality changes as well as any bug fixed to check due to this nothing is going wrong.
The discussion is about "How do you perform Regression Testing in your company". But all have replied with what is Regression testing. Good answers
Well, I would like to put my inputs on Regression testing. The regression testing is carried out as the last testing phase. Initially say, in a project the test cases covering all the functionality are 1000 numbers. Now at the time of regression the PM has a discussion with the QA, Testing lead as well as Development lead (the team will also be present) and have a review on the test cases to finalize how many test cases can be deleted from the total of 1000 test cases to perform regression on the build and designs a new test plan. This is done to avoid running/executing unwanted test cases or cases in which the functionality is very stable and for sure has no effect on the revision of the build from the development team. There are chances that 200 test cases can be deleted from the count of 1000 numbers shrinking the count to may be 800 test cases to perform regression on the build but all the 800 cases covers all the major functionality in the project. Also some companies term the build as Release candidate build in which regression is performed. The time taken for performing the Regression testing depends on the size of the project and the team size plus the total number of test cases. Basically, a tester can execute up to 100 test cases in a day. Again, if these 800 test cases are being tested and the report is sent. So the developers work on the bug fixing and give new build. Also depending on the size of the project the build is revised till stability is achieved. And based on the testing team report the build is released with the remaining defects been put in the release notes. Also as mentioned by our friends regression is been carried out either manually or with automation and sometimes in both where some TCs cannot be automated.
Regression testing : It is the process of reexecuting all the test cases incliuding relative passed test cases and failed test cases on the modified build to evaluate is there any side effects bcz of the resolved bug .
this will b fallowed , on the batch of test cases that represents that particular fucntionality on newly released build
ex : user login
while preparing test cases for the above functionaliaty we need to focuss on different possibilities like
1) user login with valied data
2) user login with invalliid data
3) user login with missing mandatory fields
after preparing test cases, its our resposibility to prepare " Tracability matrix "
Tracability matrix : it is nothing but mapping b/w prepared test cases and corresponding modules
after preparing test cases Tracability matrix, we will go testg execution , if we find any deviations from expected values we r going to report to the same to the devopement team
after checking for the genuinity , they will resolve the bug & send back to u for regression testing
this process continues till max test cases passes .