Software regression: Difference between revisions
No edit summary |
Undid revision 550455611 by 202.3.120.4 (talk) What? |
||
| Line 10: | Line 10: | ||
* Remote – a change in one part of the software breaks functionality in another module or component. |
* Remote – a change in one part of the software breaks functionality in another module or component. |
||
* Unmasked – a change unmasks an already existing bug that had no effect before the change. |
* Unmasked – a change unmasks an already existing bug that had no effect before the change. |
||
* Yoshimitsu - A bug caused by a Japanese programmer. |
|||
==See also== |
==See also== |
||
Revision as of 18:17, 15 April 2013
 | This article needs additional citations for verification. (December 2009) |
 | This article possibly contains original research. (July 2009) |
A software regression is a software bug which makes a feature stop functioning as intended after a certain event (for example, a system upgrade, system patching or a change to daylight saving time).[1] A software performance regression is a situation where the software still functions correctly, but performs slowly or uses more memory when compared to previous versions.
Regressions are often caused by encompassed bug fixes included in software patches. One approach to avoiding this kind of problem is regression testing. A properly designed test plan prevents this possibility before releasing any software.[2] Automated testing and well-written test cases can reduce the likelihood of a regression.
A software regression can be of one of three types:[citation needed]
- Local – a change introduces a new bug in the changed module or component.
- Remote – a change in one part of the software breaks functionality in another module or component.
- Unmasked – a change unmasks an already existing bug that had no effect before the change.
See also
Further reading
http://www.cs.kent.edu/~jmaletic/cs63901/downloads/UnitTesting.pdf [dead link]
References
- ^ http://www.research.ibm.com/haifa/Workshops/verification2007/present/Dor_Nir_web.pdf
- ^ Richardson, Jared (2006). Ship It! A Practical Guide to Successful Software Projects. Raleigh, NC: The Pragmatic Bookshelf. pp. 32, 193. ISBN 978-0-9745140-4-8.
{{cite book}}: Unknown parameter|coauthors=ignored (|author=suggested) (help)
 | This software article is a stub. You can help Wikipedia by expanding it. |