| || |
- 1 Post By Tester850
When do you perform Regression Testing? Is it always necessary to perform Regression Testing? How will you decide if Regression Testing needs to be performed?
It depend on the nature of the fix. For example, a spelling mistake or text isn't aligned properly at the interface. This fix is usually simple and shouldn't affect other areas of the product (low risk). So, I verify the fix and don't perform regression testing.
Originally Posted by Pushkar Joshi
In the early development phase, I usually don't perform heavy regression testing. That's because requirements change and everything is so unstable (not worth my time to be too serious). But, I do continue and report bugs until it is stable. Once everything becomes stable or already released to the public, I spend most of time on regression testing whenever fixes are made. Usually, a tester will know if it's a big fix (high risk) or small fix (low risk) and you decide if regression needs to be performed.
I guess it also depends on what kind of software you are testing. Some software are very critical to businesses and you might need to do heavy regression testing for all fixes.
Moment a test engineer informs that a bug is fixed and hands over modified build, now modified build is tested for its impact over whole application. Such testing is named as regression testing. Regression testing is necessary for each modified build to ensure that there are no negative impacts on over all application because of modified build.
Regression is always performed. But how much depends on how strong your change control is, how much automation is in place, and how risky the changes are.
If your change control is, developers tell you what changed.. You might not have faith and opt to do a full regression.
If your change control is having a generated change list, which has managed feature tags that tell you all the affected features, than you may opt to only perform regression around those features.
If your automation is robust, you may perform less regression only around areas that have changed, and avoid doing functional regression.
If your automation is spotty or non existent, you may opt for doing more thorough regression around what changed.
Regression should always be performed after a new fix based on its priority. This will help us to find out the impact of this fix on other modules or functionality of the software. This should always be performed based on defect:
Low and Feel good fixes (If time and budget allow)
Automation is really useful for regression testing. It save testers time and effort of re-testing all the modules that may be impacted by new fix.
t the system using same procedure that was followed before we found a bug. If no bug found during regression while running the scripts, t will provide a the overall performance of the software.
Wow, I am speechless. There are some books that you should read on testing. It will help you more than peppering this forum with below the basics questions.
Originally Posted by Pushkar Joshi
Regression Testing is the testing process which is performed to make sure that fix of any bug doesn't affect any other feature of application. Hence regression testing is important and need to be performed while verifying any changes made in the product/application.
Regression testing is initiated when developer fix any bug or add new code for new functionality to the application. There can be many dependencies in newly added and existing functionality. This is quality measure to check that new code merged with old code and unmodified code is not getting affected. Most of the time testing team has task to check the last minute changes in the application. In such situation, testing only affected application area in necessary to complete the testing process in time with covering all major system aspects. Regression testings is very important when there is continuous change or new improvements added in the application. The new functionality should not negatively affect existing tested functionality.
Regression testing can be done by manually or automation. If you are using automation then it would save your time and provide the results ASAP. However if don't have functionality automated then still it is important to do and to ensure that nothing should be broken with new chnages in application.
Please refer the below links which would help you to understand the regression test and its importance:
How important is regression testing? ? Testing Tricks
How important are regression tests (specially in Agile) - Software Testing Club - An Online Software Testing Community
“Quality That Creates Value”
QASource delivers your own experienced QA team, a comprehensive QA infrastructure focused on efficiency and excellence, and a new, multi-million-dollar lab
Regression Testing is to be executed when test cases are retested to make sure whether the previous application is working fine and also to know and find bugs due to changes done to fix bugs of previous application function.