Software regression: Difference between revisions

Revision as of 01:47, 22 December 2019

Revision as of 21:21, 31 December 2019

Line 1:

{{Unreliable sources|date=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, [[Patch (computing)|system patching]] or a change to [[daylight saving time]]).<ref name=ibm-locating-bugs>{{cite conference |last1=Yehudai|first1=Amiram |last2=Tyszberowicz|first2=Shmuel |last3=Nir|first3=Dor|title=Locating Regression Bugs|url=https://www.researchgate.net/profile/Avi_Ziv/publication/225437428_Using_Virtual_Coverage_to_Hit_Hard-To-Reach_Events/links/544a2c590cf2ea6541343ef8/Using-Virtual-Coverage-to-Hit-Hard-To-Reach-Events.pdf#page=235|conference=Haifa Verification Conference|conference-url=https://www.research.ibm.com/haifa/conferences/hvc2017/previous.shtml|year=2007|accessdate=10 March 2018}}</ref> A '''software performance regression''' is a situation where the software still functions correctly, but performs more slowly or uses more memory or resources than before.<ref>{{Cite journal|last=Shang|first=Weiyi|last2=Hassan|first2=Ahmed E.|last3=Nasser|first3=Mohamed|last4=Flora|first4=Parminder|date=11 December 2014|title=Automated Detection of Performance Regressions Using Regression Models on Clustered Performance Counters|url=https://sail.cs.queensu.ca/Downloads/ICPE2015_AutomatedDetectionofPerformanceRegressionsUsingRegressionModelsOnClusteredPerformanceCounters.pdf#page=1|journal=|volume=|pages=|via=}}</ref>