Jump to content

Software regression

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Greenrd (talk | contribs) at 12:21, 10 March 2018 (as the first sentence notes, regressions are not necessarily caused by new versions of the software the regression is in - fixed). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

A software regression is a software bug that 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 than before.

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 aims at preventing 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

  1. ^ Yehudai, Amiram; Tyszberowicz, Shmuel. "Locating Regression Bugs" (PDF). Research.IBM.com. IBM. Retrieved 24 June 2014.
  2. ^ 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.
Stub icon

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=829726464"