Regression testing: Difference between revisions

Revision as of 05:49, 2 November 2023

Revision as of 05:50, 2 November 2023

Line 17:

Common strategies are to run such a system after every successful compile (for small projects), every night, or once a week. Those strategies can be automated by an external tool.

[https://webcodegenie.com/blog/regression-testing/ Regression testing] is an integral part of the [[extreme programming]] software development method. In this method, design documents are replaced by extensive, repeatable, and automated testing of the entire software package throughout each stage of the [[software development process]]. Regression testing is done after functional testing has concluded, to verify that the other functionalities are working.

In the corporate world, regression testing has traditionally been performed by a [[software quality assurance]] team after the development team has completed work. However, defects found at this stage are the most costly to fix. This problem is being addressed by the rise of [[unit testing]]. Although developers have always written test cases as part of the development cycle, these test cases have generally been either [[functional testing|functional tests]] or [[unit testing|unit tests]] that verify only intended outcomes. Developer testing compels a developer to focus on unit testing and to include both positive and negative test cases.<ref>{{cite web|url=http://www.sys-con.com/read/47359.htm|title=Developer Testing Is 'In': An interview with Alberto Savoia and Kent Beck|last=Dudney|first=Bill|date=2004-12-08|access-date=2007-11-29}}</ref>