Revision as of 17:28, 11 January 2017 edit SMcCandlish (talk \| contribs) Autopatrolled, Extended confirmed users, Page movers, File movers, New page reviewers, Pending changes reviewers, Rollbackers, Template editors 203,717 edits m rm redundant link ← Previous edit		Revision as of 21:33, 8 June 2017 edit undo Nurg (talk \| contribs) Extended confirmed users, Page movers, Pending changes reviewers, Rollbackers 67,070 edits m →top: "which" is ok, "that" is better Next edit →
Line 4: }} A '''software regression''' is a [[software bug]] ~~which~~that makes a feature stop functioning as intended after a certain event (for example, a system upgrade, [[Patch (computing)\|system patching]] or a change to [[daylight saving time]]).<ref name=ibm-locating-bugs>{{cite web \|last1=Yehudai\|first1=Amiram \|last2=Tyszberowicz\|first2=Shmuel \|title=Locating Regression Bugs\|url=http://www.research.ibm.com/haifa/Workshops/verification2007/present/Dor_Nir_web.pdf\|website=Research.IBM.com\|publisher=IBM\|accessdate=24 June 2014}}</ref> 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 [[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=http://www.pragprog.com/titles/prj/ship-it \|year=2006 \|publisher=The Pragmatic Bookshelf \|___location=Raleigh, NC \|pages=32, 193 \|isbn = 978-0-9745140-4-8 }}</ref> [[Automated testing]] and well-written [[test case]]s can reduce the likelihood of a regression.

Software regression: Difference between revisions