Content deleted Content added
Clarifying that CI does not require TDD |
Altered pages. Add: date, s2cid, authors 1-1. Removed parameters. Formatted dashes. Some additions/deletions were parameter name changes. | Use this bot. | #UCB_Other |
||
Line 109:
* When unit tests fail or a [[Software bug|bug]] emerges, if developers need to revert the codebase to a bug-free state without [[debugging]], only a small number of changes are lost (because integration happens frequently)
* Constant availability of a "current" build for testing, demo, or release purposes
* Frequent code check-in pushes developers to create modular, less complex code<ref>{{Cite journal |
With continuous automated testing, benefits can include:
Line 144:
* {{Cite web |title=A Recipe for Build Maintainability and Reusability |url=http://jayflowers.com/joomla/index.php?option=com_content&task=view&id=26 |last=Flowers |first=Jay |access-date=28 May 2006 |archive-date=25 June 2020 |archive-url=https://web.archive.org/web/20200625060704/https://jayflowers.com/joomla/index.php?option=com_content&task=view&id=26 |url-status=dead }}
* {{Cite web |title=Developer works |url=http://www.ibm.com/developerworks/java/library/j-ap11297/ |last=Duvall |first=Paul |website=[[IBM]] |date=4 December 2007}}
* {{Cite web |title=Version lifecycle |date=June 2024 |url=http://www.mediawiki.org/wiki/Version_lifecycle |publisher=MediaWiki}}
[[Category:Continuous integration| ]]
|