Jump to content

Software regression: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
Kenyoni (talk | contribs)
→‎top: Adding/improving reference(s)
Kenyoni (talk | contribs)
→‎top: Added reference
Line 8: Line 8:
Regressions are often caused by [[Hotfix|encompassed bug fixes]] included in [[software patch]]es. 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.<ref>{{cite book |last=Richardson |first=Jared |author2=Gwaltney, William Jr |title=Ship It! A Practical Guide to Successful Software Projects |url=https://archive.org/details/shipitpracticalg0000rich/page/32 |year=2006 |publisher=The Pragmatic Bookshelf |location=Raleigh, NC |pages=[https://archive.org/details/shipitpracticalg0000rich/page/32 32, 193] |isbn=978-0-9745140-4-8 }}</ref> [[Automated testing]] and well-written [[test case]]s can reduce the likelihood of a regression.
Regressions are often caused by [[Hotfix|encompassed bug fixes]] included in [[software patch]]es. 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.<ref>{{cite book |last=Richardson |first=Jared |author2=Gwaltney, William Jr |title=Ship It! A Practical Guide to Successful Software Projects |url=https://archive.org/details/shipitpracticalg0000rich/page/32 |year=2006 |publisher=The Pragmatic Bookshelf |location=Raleigh, NC |pages=[https://archive.org/details/shipitpracticalg0000rich/page/32 32, 193] |isbn=978-0-9745140-4-8 }}</ref> [[Automated testing]] and well-written [[test case]]s can reduce the likelihood of a regression.


A software regression can be of one of three types:<ref>{{Cite web|url=https://apphawks.com/blog/regression-testing-types-technique-benefits/|title=Regression testing: Types, Techniques and Benefits - QA Service - Apphawks|date=2019-02-20|website=Software Testing Company & QA Services - Apphawks|language=en-GB|access-date=2019-12-21}}</ref>
A software regression can be of one of three types:<ref>{{Cite web|url=https://apphawks.com/blog/regression-testing-types-technique-benefits/|title=Regression testing: Types, Techniques and Benefits - QA Service - Apphawks|date=2019-02-20|website=Software Testing Company & QA Services - Apphawks|language=en-GB|access-date=2019-12-21}}</ref><ref>{{Cite web|url=https://airbrake.io/blog/what-is/regression-testing|title=Regression Testing: What It Is and How to Use It|last=Andrew Powell-Morse|date=2018-02-07|website=Airbrake Blog|language=en-US|access-date=2019-12-22}}</ref>


* Local – a change introduces a new bug in the changed module or component.
* Local – a change introduces a new bug in the changed module or component.

Revision as of 00:21, 22 December 2019

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:[3][4]

  • 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; Nir, Dor (2007). Locating Regression Bugs (PDF). Haifa Verification Conference. Retrieved 10 March 2018.
  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.
  3. ^ "Regression testing: Types, Techniques and Benefits - QA Service - Apphawks". Software Testing Company & QA Services - Apphawks. 2019-02-20. Retrieved 2019-12-21.
  4. ^ Andrew Powell-Morse (2018-02-07). "Regression Testing: What It Is and How to Use It". Airbrake Blog. Retrieved 2019-12-22.