Software regression: Difference between revisions

Revision as of 04:29, 19 December 2019

Revision as of 22:29, 21 December 2019

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.

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:{{Citation needed|date=September 2012}}

* 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.