Software regression: Difference between revisions

Content deleted Content added
as the first sentence notes, regressions are not necessarily caused by new versions of the software the regression is in - fixed
m changing citation to paper instead of PowerPoint presentation about the paper
Line 4:
}}
 
A '''software regression''' is a [[software bug]] 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 webconference |last1=Yehudai|first1=Amiram |last2=Tyszberowicz|first2=Shmuel |last3=Nir|first3=Dor|title=Locating Regression Bugs|url=httphttps://www.researchresearchgate.ibm.comnet/haifaprofile/WorkshopsAvi_Ziv/verification2007publication/present225437428_Using_Virtual_Coverage_to_Hit_Hard-To-Reach_Events/Dor_Nir_weblinks/544a2c590cf2ea6541343ef8/Using-Virtual-Coverage-to-Hit-Hard-To-Reach-Events.pdf#page=235|websiteconference=ResearchHaifa Verification Conference|conference-url=https://www.IBMresearch.ibm.com/haifa/conferences/hvc2017/previous.shtml|publisheryear=IBM2007|accessdate=2410 JuneMarch 20142018}}</ref> 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 [[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.