Editing Software testing (section)

==== Agile development ====

[[Agile software development]] commonly involves testing while the code is being written and organizing teams with both programmers and testers and with team members performing both programming and testing.

One agile practice, [[Test-driven development|test-driven software development]] (TDD), is a way of [[unit testing]] such that unit-level testing is performed while writing the product code.<ref name="AgileAllianceTDD">{{Cite web |date=December 5, 2015 |title=What is Test Driven Development (TDD)? |url=https://www.agilealliance.org/glossary/tdd/ |access-date=March 17, 2018 |website=Agile Alliance}}</ref> Test code is updated as new features are added and failure conditions are discovered (bugs fixed). Commonly, the unit test code is maintained with the project code, integrated in the build process, and run on each build and as part of regression testing. Goals of this [[continuous integration]] is to support development and reduce defects.<ref>{{Cite web |title=Test-Driven Development and Continuous Integration for Mobile Applications |url=https://msdn.microsoft.com/en-us/library/bb985498.aspx#_Continuous_Integration |access-date=March 17, 2018 |website=Microsoft Developer Network|date=January 14, 2009 }}</ref><ref name="AgileAllianceTDD" />

Even in organizations that separate teams by programming and testing functions, many often have the programmers perform [[unit testing]].<ref>{{Cite book |last1=Brown |first1=Chris |url=http://www.informit.com/articles/article.aspx?p=26320&seqNum=6 |title=Introduction to Rapid Software Testing |last2=Cobb |first2=Gary |last3=Culbertson |first3=Robert |date=April 12, 2002}}</ref>