Jump to content

Software regression

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Walter Görlitz (talk | contribs) at 20:58, 19 August 2013 (remove both further reading links as they're not particularly informative). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)

This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.
Find sources: "Software regression" – news · newspapers · books · scholar · JSTOR (December 2009) (Learn how and when to remove this message)

This article possibly contains original research. Please improve it by verifying the claims made and adding inline citations. Statements consisting only of original research should be removed. (July 2009) (Learn how and when to remove this message)

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

Regression testing

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.

Retrieved from "https://en.wikipedia.org/w/index.php?title=Software_regression&oldid=569279817"

Hidden categories: