Skip to main content Accessibility help
×
Hostname: page-component-76fb5796d-skm99 Total loading time: 0 Render date: 2024-04-27T21:46:44.621Z Has data issue: false hasContentIssue false

7 - Selection, Minimization and Prioritization of Test Cases for Regression Testing

Published online by Cambridge University Press:  05 November 2012

Yogesh Singh
Affiliation:
Guru Gobind Singh Indraprastha University, Delhi
Get access

Summary

Software maintenance is becoming important and expensive day by day. Development of software may take a few years (2 to 4 years), but the same may have to be maintained for several years (10 to 15 years). Software maintenance accounts for as much as two-thirds of the cost of software production [BEIZ90].

Software inevitably changes, whatever well-written and designed initially it may be. There are many reasons for such changes:

  1. (i) Some errors may have been discovered during the actual use of the software.

  2. (ii) The user may have requested for additional functionality.

  3. (iii) Software may have to be modified due to change in some external policies and principles. When European countries had decided to go for a single European currency, this change affected all banking system software.

  4. (iv) Some restructuring work may have to be done to improve the efficiency and performance of the software.

  5. (v) Software may have to be modified due to change in existing technologies.

  6. (vi) Some obsolete capabilities may have to be deleted.

This list is endless but the message is loud and clear i.e. ‘change is inevitable’. Hence, software always changes in order to address the above mentioned issues. This changed software is required to be re-tested in order to ensure that changes work correctly and these changes have not adversely affected other parts of the software. This is necessary because small changes in one part of the software program may have subtle undesired effects in other seemingly unrelated parts of the software.

Type
Chapter
Information
Software Testing , pp. 335 - 367
Publisher: Cambridge University Press
Print publication year: 2011

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

Save book to Kindle

To save this book to your Kindle, first ensure coreplatform@cambridge.org is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

Available formats
×