Revision as of 18:36, 6 November 2023 edit Occo5903 (talk \| contribs) 162 edits Deleted section on use of AI in regression testing — text itself read as machine-generated and is a simple list that adds little detail to the article, while also lacking any kind of sourcing other than a random AI company's product page. ← Previous edit		Revision as of 04:30, 23 February 2024 edit undo 203.13.128.125 (talk) Simplify grammar Next edit →
Line 11: Sometimes re-emergence occurs because a fix gets lost through poor [[revision control]] practices (or simple [[human error]] in revision control). Often, a fix for a problem will be "[[software brittleness\|fragile]]" in that it fixes the problem in the narrow case where it was first observed but not in more general cases which may arise over the lifetime of the software. Frequently, a fix for a problem in one area inadvertently causes a [[software bug]] in another area. ~~Finally, it~~It may happen that, when ~~some~~a feature is redesigned, some of the same mistakes that were made in the original implementation of the feature ~~are~~also ~~made~~occur in the redesign. ~~Therefore, in~~In most software development situations, it is considered [[Best Coding Practices\|good coding practice]], when a bug is located and fixed, to record a test that exposes the bug and re-run that test regularly after subsequent changes to the program.<ref name="kolawa">{{cite book \| last = Kolawa \| first = Adam \|author2=Huizinga, Dorota \| title = Automated Defect Prevention: Best Practices in Software Management \| url = http://www.wiley.com/WileyCDA/WileyTitle/productCd-0470042125.html \| year = 2007 \| publisher = Wiley-IEEE Computer Society Press \| page=73\| isbn = 978-0-470-04212-0 }}</ref> Although this may be done through [[manual testing]] procedures using programming techniques, it is often done using [[automated testing]] tools.<ref>[http://safari.oreilly.com/0201794292/ch08lev1sec4 Automate Regression Tests When Feasible], Automated Testing: Selected Best Practices, Elfriede Dustin, Safari Books Online</ref> Such a [[test suite]] contains software tools that allow the testing environment to execute all the regression [[test case]]s automatically; some projects even set up automated systems to re-run all regression tests at specified intervals and report any failures (which could imply a regression or an out-of-date test).<ref>{{cite web\| url=http://www.drdobbs.com/tools/change-code-without-fear/206105233\| title=Change Code Without Fear: Utilize a Regression Safety Net\|last=daVeiga\|first=Nada\|work=[[Dr. Dobb's Journal]]\| date=2008-02-06}}</ref>

Regression testing: Difference between revisions