Revision as of 13:58, 23 May 2025 edit OAbot (talk \| contribs) Bots 646,105 edits m Open access bot: url-access updated in citation with #oabot. ← Previous edit		Revision as of 11:28, 16 August 2025 edit undo Jnestorius (talk \| contribs) Autopatrolled, Extended confirmed users, Pending changes reviewers 80,513 edits Test case (software) Next edit →
Line 5: * ''Unmasked'' – a change unmasks an already existing bug that had no effect before the change. 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 (software)\|test case]]s can reduce the likelihood of a regression. ==Prevention and detection==

Software regression: Difference between revisions