Software regression: Difference between revisions
–—°′″≈≠≤≥±−×÷←→·§<ref></ref> |
m Reverted edits by 175.140.13.38 (talk) to last version by Walter Görlitz |
||
| Line 1: | Line 1: | ||
{{multiple issues| |
|||
{{Refimprove|date=December 2009}} |
{{Refimprove|date=December 2009}} |
||
{{Original research|date=July 2009}} |
{{Original research|date=July 2009}} |
||
Revision as of 16:43, 13 March 2015
 | This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)
|
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
References
- ^ Yehudai, Amiram; Tyszberowicz, Shmuel. "Locating Regression Bugs" (PDF). Research.IBM.com. IBM. Retrieved 24 June 2014.
- ^ Richardson, Jared; Gwaltney, William Jr (2006). Ship It! A Practical Guide to Successful Software Projects. Raleigh, NC: The Pragmatic Bookshelf. pp. 32, 193. ISBN 978-0-9745140-4-8.
 | This software article is a stub. You can help Wikipedia by expanding it. |