Editing Unit testing (section)

=== Reduced cost ===
The cost of finding a bug before coding begins or when the code is first written is considerably lower than the cost of detecting, identifying, and correcting the bug later. Bugs in released code may also cause costly problems for the end-users of the software.<ref>{{cite journal |last1=Boehm |first1=Barry W. |author-link1=Barry Boehm |last2=Papaccio |first2=Philip N. |date=October 1988 |title=Understanding and Controlling Software Costs |url=http://faculty.ksu.edu.sa/ghazy/Cost_MSc/R6.pdf |journal=IEEE Transactions on Software Engineering |volume=14 |issue=10 |pages=1462–1477 |doi=10.1109/32.6191 |access-date=13 May 2016 |archive-date=9 October 2016 |archive-url=https://web.archive.org/web/20161009084506/http://faculty.ksu.edu.sa/ghazy/Cost_MSc/R6.pdf |url-status=dead }}</ref><ref>{{cite web|url=https://msdn.microsoft.com/en-us/library/ee330950%28v=vs.110%29.aspx|title=Test Early and Often|publisher=Microsoft}}</ref><ref>{{cite web|url=http://www.ni.com/white-paper/8082/en/| title=Prove It Works: Using the Unit Test Framework for Software Testing and Validation| publisher=[[National Instruments]]| date=2017-08-21}}</ref> Code can be impossible or difficult to unit test if poorly written, thus unit testing can force developers to structure functions and objects in better ways.