Regression Testing

[Former Member]

hai

can any body pls explan in Breif about the Regression testing

wat is that

why it is doinng

explain clearly

if possible pls send some test scenarios also to kirankumar12000gmail.com

good answer will be awarded

regards

kiran

[Former Member · Accepted solution]

Hello,

Regression testing is reffered to a test which verfies that some new configuration doesnot adversly impact existing functionality. This will be done on each phase of testing.

The purpose of regression testing is to verify that new additions or changes to the configuration, are accurate and have not caused any new defects to be introduced to the existing configuration that has already been tested.

Prase

[Former Member]

thnaks

[former_member192897]

Regression testing is referred to a test which verifies that some new configuration doesn't adversely impact existing functionality. This will be done on each phase of testing.

[former_member335885]

HI,

Regression testing means rerunning test cases from existing test suites to build confidence that software changes have no unintended side-effects. The u201Cidealu201D process would be to create an extensive test suite and run it after each and every change. Unfortunately, for many projects this is just impossible because test suites are too large, because changes come in too fast, because humans are in the testing loop, because scarce, highly in-demand simulation laboratories are needed, or because testing must be done on many different hardware and OS platforms.

Researchers have tried to make regression testing more effective and efficient by developing regression test selection (RTS) techniques, but many problem remain, such as:

Unpredictable performance. RTS techniques sometimes save time and money, but they sometimes select most or all of the original test cases. Thus, developers using RTS techniques can find themselves worse off for having done so.

Incompatible process assumptions. Testing time is often limited (e.g., must be done overnight). RTS techniques do not consider such constraints and, therefore, can and do select more test cases than can be run.

Inappropriate evaluation models. RTS techniques try to maximize average regression testing performance rather than optimize aggregate performance over many testing sessions. However, companies that test frequently might accept less effective, but cheaper individual testing sessions if the system would, nonetheless, be well-tested over some short period of time.

Some strategies and factors to consider during this process include the following:

Test fixed bugs promptly. The programmer might have handled the symptoms but not have gotten to the underlying cause.

Watch for side effects of fixes. The bug itself might be fixed but the fix might create other bugs.

Write a regression test for each bug fixed.

If two or more tests are similar, determine which is less effective and get rid of it.

Identify tests that the program consistently passes and archive them.

Focus on functional issues, not those related to design.

Make changes (small and large) to data and find any resulting corruption.

Trace the effects of the changes on program memory.

Also see http://en.wikipedia.org/wiki/Regression_testing

Thanks & Regards,

Kiran