Vid

Krimson Guest	Vid Jul 26, 2009 16:38:38 GMT -5 Quote Select Post Deselect Post Link to Post Back to Top Post by Krimson on Jul 26, 2009 16:38:38 GMT -5

Eton Bones Administrator "Please apologize for your stupidity, there are many, thank you" Posts: 140	Vid Jul 14, 2013 19:59:08 GMT -5 Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by Eton Bones on Jul 14, 2013 19:59:08 GMT -5 reply2
	test

Eton Bones
Administrator

"Please apologize for your stupidity, there are many, thank you"

Posts: 140

Vid Mar 21, 2015 0:23:15 GMT -5

Quote

Post by Eton Bones on Mar 21, 2015 0:23:15 GMT -5

[dohtml ]<table width="100%" style="vertical-align:top;" role="grid"> <tbody>  <tr>   <td width="50%" valign="top" class="board item first boardtd" id="board-2"> <div class="board-name"><a class="board-link board-2" href="/board/2/introductions">Introductions</a></div> <div class="board-last-post"> <a class="thread-recent-link thread-100 post-132 board-2" href="/threads/recent/100">not sure how Vikings Great others, HI though.</a> BY <a title="admin" class="user-link user-1 group-1" style="color: #257771;" href="/user/1">Dusty the Small</a> <abbr title="Tue Mar 17 2015 16:06:22 GMT-0500 (Central Standard Time)" class="time" data-timestamp="1426626382000">Mar 17, 2015 at 4:06pm</abbr></div> <table width="100%" cellpadding="5px" style="vertical-align:top;"> <tbody><tr style="vertical-align:top;"> <td width="70%"><div class="board-description"> <table><tbody><tr><td width="70px"> <div title="THREADS" class="board-thread-count">5 <div style="font-size:10px;padding-top:2px;">THREADS</div></div> <div title="POSTS" class="board-post-count">11 <div style="font-size:10px;padding-top:2px;">POSTS</div></div> </td><td> Are you new here? Welcome! Feel free to introduce yourself. </td></tr></tbody></table>  </div></td> </tr> <tr> <td style="margin-bottom:10px;">  </td></tr> </tbody></table>  <div class="clear"></div>  </td>      <td width="50%" valign="top" class="board item boardtd" id="board-4"> <div class="board-name"><a class="board-link board-4" href="/board/4/information">Information</a></div> <div class="board-last-post"> <a class="thread-recent-link thread-4 post-151 board-4" href="/threads/recent/4">Rules</a> BY <a title="admin" class="user-link user-1 group-1" style="color: #257771;" href="/user/1">Dusty the Small</a> <abbr title="Wed Mar 18 2015 21:55:34 GMT-0500 (Central Standard Time)" class="time" data-timestamp="1426733734000">Mar 18, 2015 at 9:55pm</abbr></div> <table width="100%" cellpadding="5px" style="vertical-align:top;"> <tbody><tr style="vertical-align:top;"> <td width="70%"><div class="board-description"> <table><tbody><tr><td width="70px"> <div title="THREADS" class="board-thread-count">5 <div style="font-size:10px;padding-top:2px;">THREADS</div></div> <div title="POSTS" class="board-post-count">6 <div style="font-size:10px;padding-top:2px;">POSTS</div></div> </td><td> Here you will find the rules and other information about the site. </td></tr></tbody></table>  </div></td> </tr> <tr> <td style="margin-bottom:10px;">  </td></tr> </tbody></table>  <div class="clear"></div>  </td>   </tr><tr>   <td width="50%" valign="top" class="board item boardtd" id="board-6"> <div class="board-name"><a class="board-link board-6" href="/board/6/suggestions">Questions and Suggestions</a></div> <div class="board-last-post">NO POSTS HAVE BEEN MADE IN THIS BOARD.</div> <table width="100%" cellpadding="5px" style="vertical-align:top;"> <tbody><tr style="vertical-align:top;"> <td width="70%"><div class="board-description"> <table><tbody><tr><td width="70px"> <div title="THREADS" class="board-thread-count">0 <div style="font-size:10px;padding-top:2px;">THREADS</div></div> <div title="POSTS" class="board-post-count">0 <div style="font-size:10px;padding-top:2px;">POSTS</div></div> </td><td> Guests and members can post comments or questions here in case they have any. </td></tr></tbody></table>  </div></td> </tr> <tr> <td style="margin-bottom:10px;">  </td></tr> </tbody></table>  <div class="clear"></div>  </td>     <td valign="top" class="board item last boardtd" id="board-7" colspan="3"> <div class="board-name"><a class="board-link board-7" href="/board/7/announcements">Announcements</a></div> <div class="board-last-post"> <a class="thread-recent-link thread-105 post-194 board-7" href="/threads/recent/105">Activity Check</a> BY <a title="admin" class="user-link user-1 group-1" style="color: #257771;" href="/user/1">Dusty the Small</a> <abbr title="Mon Mar 23 2015 23:29:04 GMT-0500 (Central Standard Time)" class="time recent_time" data-timestamp="1427171344000">3 hours ago</abbr></div> <table width="100%" cellpadding="5px" style="vertical-align:top;"> <tbody><tr style="vertical-align:top;"> <td width="70%"><div class="board-description"> <table><tbody><tr><td width="70px"> <div title="THREADS" class="board-thread-count">3 <div style="font-size:10px;padding-top:2px;">THREADS</div></div> <div title="POSTS" class="board-post-count">14 <div style="font-size:10px;padding-top:2px;">POSTS</div></div> </td><td> Staff will post site-wide announcements here. </td></tr></tbody></table>  </div></td> </tr> <tr> <td style="margin-bottom:10px;">  </td></tr> </tbody></table>  <div class="clear"></div>  </td>    </tr></tbody></table>[/dohtml]

Last Edit: Mar 25, 2015 0:38:17 GMT -5 by Eton Bones

test

Eton Bones
Administrator

"Please apologize for your stupidity, there are many, thank you"

Posts: 140

Vid Mar 24, 2015 3:39:59 GMT -5

Quote

Post by Eton Bones on Mar 24, 2015 3:39:59 GMT -5

[dohtml height="500" width="100%"]<div id="content" class="mw-body" role="main"> <a id="top"></a> <div id="siteNotice"><div id="centralNotice"></div></div> <div class="mw-indicators"></div> <h1 id="firstHeading" class="firstHeading" lang="en">Unit testing</h1> <div id="bodyContent" class="mw-body-content"> <div id="siteSub">From Wikipedia, the free encyclopedia</div> <div id="contentSub"></div> <div id="jump-to-nav" class="mw-jump"> Jump to: <a href="#mw-head">navigation</a>, <a href="#p-search">search</a> </div> <div id="mw-content-text" lang="en" dir="ltr" class="mw-content-ltr"><table class="metadata plainlinks ambox ambox-content ambox-multiple_issues compact-ambox" role="presentation"><tbody><tr><td class="mbox-image"><div style="width:52px"><img alt="" src="//upload.wikimedia.org/wikipedia/commons/thumb/b/b4/Ambox_important.svg/40px-Ambox_important.svg.png" width="40" height="40" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/b/b4/Ambox_important.svg/60px-Ambox_important.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/b/b4/Ambox_important.svg/80px-Ambox_important.svg.png 2x" data-file-width="40" data-file-height="40"></div></td><td class="mbox-text"><table class="collapsible" style="width:95%; background:transparent;" id="collapsibleTable0"><tbody><tr><th style="text-align:left; padding:0.2em 2px 0.2em 0;">[<a id="collapseButton0" href="#">hide</a>]This article has multiple issues. Please help <a class="external text" href="//en.wikipedia.org/w/index.php?title=Unit_testing&action=edit">improve it</a> or discuss these issues on the <a href="/wiki/Talk:Unit_testing" title="Talk:Unit testing">talk page</a>.</th></tr><tr><td><table class="metadata plainlinks ambox ambox-content ambox-Refimprove" role="presentation"><tbody><tr><td class="mbox-image"><div style="width:52px"><a href="/wiki/File:Question_book-new.svg" class="image"><img alt="" src="//upload.wikimedia.org/wikipedia/en/thumb/9/99/Question_book-new.svg/50px-Question_book-new.svg.png" width="50" height="39" srcset="//upload.wikimedia.org/wikipedia/en/thumb/9/99/Question_book-new.svg/75px-Question_book-new.svg.png 1.5x, //upload.wikimedia.org/wikipedia/en/thumb/9/99/Question_book-new.svg/100px-Question_book-new.svg.png 2x" data-file-width="262" data-file-height="204"></a></div></td><td class="mbox-text">This article needs additional citations for <a href="/wiki/Wikipedia:Verifiability" title="Wikipedia:Verifiability">verification</a>. Please help <a class="external text" href="//en.wikipedia.org/w/index.php?title=Unit_testing&action=edit">improve this article</a> by <a href="/wiki/Help:Introduction_to_referencing/1" title="Help:Introduction to referencing/1">adding citations to reliable sources</a>. Unsourced material may be challenged and removed. (November 2007)</td></tr></tbody></table><table class="metadata plainlinks ambox ambox-style ambox-Cleanup" role="presentation"><tbody><tr><td class="mbox-image"><div style="width:52px"><img alt="" src="//upload.wikimedia.org/wikipedia/en/thumb/f/f2/Edit-clear.svg/40px-Edit-clear.svg.png" width="40" height="40" srcset="//upload.wikimedia.org/wikipedia/en/thumb/f/f2/Edit-clear.svg/60px-Edit-clear.svg.png 1.5x, //upload.wikimedia.org/wikipedia/en/thumb/f/f2/Edit-clear.svg/80px-Edit-clear.svg.png 2x" data-file-width="48" data-file-height="48"></div></td><td class="mbox-text">This article may require <a href="/wiki/Wikipedia:Cleanup" title="Wikipedia:Cleanup">cleanup</a> to meet Wikipedia's <a href="/wiki/Wikipedia:Manual_of_Style" title="Wikipedia:Manual of Style">quality standards</a>. No <a href="/wiki/Template:Cleanup/doc" title="Template:Cleanup/doc">cleanup reason</a> has been specified. Please help <a class="external text" href="//en.wikipedia.org/w/index.php?title=Unit_testing&action=edit">improve this article</a> if you can. (July 2009)</td></tr></tbody></table></td></tr></tbody></table></td></tr></tbody></table>In <a href="/wiki/Computer_programming" title="Computer programming">computer programming</a>, unit testing is a <a href="/wiki/Software_testing" title="Software testing">software testing</a> method by which individual units of <a href="/wiki/Source_code" title="Source code">source code</a>, sets of one or more computer program modules together with associated control data, usage procedures, and operating procedures, are tested to determine whether they are fit for use.<a href="#cite_note-kolawa-1">[1]</a> Intuitively, one can view a unit as the smallest testable part of an application. In <a href="/wiki/Procedural_programming" title="Procedural programming">procedural programming</a>, a unit could be an entire module, but it is more commonly an individual function or procedure. In <a href="/wiki/Object-oriented_programming" title="Object-oriented programming">object-oriented programming</a>, a unit is often an entire interface, such as a class, but could be an individual method.<a href="#cite_note-2">[2]</a> Unit tests are short code fragments<a href="#cite_note-3">[3]</a> created by programmers or occasionally by <a href="/wiki/White-box_testing" title="White-box testing">white box testers</a> during the development process. It is also known as component testing.<a href="#cite_note-4">[4]</a>Ideally, each <a href="/wiki/Test_case" title="Test case">test case</a> is independent from the others. Substitutes such as <a href="/wiki/Method_stub" title="Method stub">method stubs</a>, <a href="/wiki/Mock_object" title="Mock object">mock objects</a>,<a href="#cite_note-mocksarentstubs-5">[5]</a> <a href="/wiki/Mock_object#Mocks.2C_fakes_and_stubs" title="Mock object">fakes</a>, and <a href="/wiki/Test_harness" title="Test harness">test harnesses</a> can be used to assist testing a module in isolation. Unit tests are typically written and run by <a href="/wiki/Software_developer" title="Software developer">software developers</a> to ensure that code meets its design and behaves as intended.<div id="toc" class="toc"><div id="toctitle"><h2>Contents</h2> [<a href="#" id="togglelink">hide</a>] </div><ul><li class="toclevel-1 tocsection-1"><a href="#Benefits">1 Benefits</a><ul><li class="toclevel-2 tocsection-2"><a href="#Finds_problems_early">1.1 Finds problems early</a></li><li class="toclevel-2 tocsection-3"><a href="#Facilitates_change">1.2 Facilitates change</a></li><li class="toclevel-2 tocsection-4"><a href="#Simplifies_integration">1.3 Simplifies integration</a></li><li class="toclevel-2 tocsection-5"><a href="#Documentation">1.4 Documentation</a></li><li class="toclevel-2 tocsection-6"><a href="#Design">1.5 Design</a></li></ul></li><li class="toclevel-1 tocsection-7"><a href="#Separation_of_interface_from_implementation">2 Separation of interface from implementation</a></li><li class="toclevel-1 tocsection-8"><a href="#Parameterized_unit_testing">3 Parameterized unit testing</a></li><li class="toclevel-1 tocsection-9"><a href="#Unit_testing_limitations">4 Unit testing limitations</a></li><li class="toclevel-1 tocsection-10"><a href="#Applications">5 Applications</a><ul><li class="toclevel-2 tocsection-11"><a href="#Extreme_programming">5.1 Extreme programming</a></li><li class="toclevel-2 tocsection-12"><a href="#Techniques">5.2 Techniques</a></li><li class="toclevel-2 tocsection-13"><a href="#Unit_testing_frameworks">5.3 Unit testing frameworks</a></li><li class="toclevel-2 tocsection-14"><a href="#Language-level_unit_testing_support">5.4 Language-level unit testing support</a></li></ul></li><li class="toclevel-1 tocsection-15"><a href="#See_also">6 See also</a></li><li class="toclevel-1 tocsection-16"><a href="#Notes">7 Notes</a></li><li class="toclevel-1 tocsection-17"><a href="#External_links">8 External links</a></li></ul></div><h2>Benefits[<a href="/w/index.php?title=Unit_testing&action=edit&section=1" title="Edit section: Benefits">edit</a>]</h2>The goal of unit testing is to isolate each part of the program and show that the individual parts are correct.<a href="#cite_note-kolawa-1">[1]</a> A unit test provides a strict, written <a href="/wiki/Design_by_Contract" title="Design by Contract" class="mw-redirect">contract</a> that the piece of code must satisfy. As a result, it affords several benefits.<h3>Finds problems early[<a href="/w/index.php?title=Unit_testing&action=edit&section=2" title="Edit section: Finds problems early">edit</a>]</h3>Unit testing finds problems early in the <a href="/wiki/Development_cycle" title="Development cycle" class="mw-redirect">development cycle</a>.In <a href="/wiki/Test-driven_development" title="Test-driven development">test-driven development</a> (TDD), which is frequently used in both <a href="/wiki/Extreme_Programming" title="Extreme Programming" class="mw-redirect">Extreme Programming</a> and <a href="/wiki/Scrum_(development)" title="Scrum (development)" class="mw-redirect">Scrum</a>, unit tests are created before the code itself is written. When the tests pass, that code is considered complete. The same unit tests are run against that function frequently as the larger code base is developed either as the code is changed or via an automated process with the build. If the unit tests fail, it is considered to be a bug either in the changed code or the tests themselves. The unit tests then allow the location of the fault or failure to be easily traced. Since the unit tests alert the development team of the problem before handing the code off to testers or clients, it is still early in the development process.<h3>Facilitates change[<a href="/w/index.php?title=Unit_testing&action=edit&section=3" title="Edit section: Facilitates change">edit</a>]</h3>Unit testing allows the programmer to <a href="/wiki/Refactoring" title="Refactoring" class="mw-redirect">refactor</a> code at a later date, and make sure the module still works correctly (e.g., in <a href="/wiki/Regression_testing" title="Regression testing">regression testing</a>). The procedure is to write test cases for all <a href="/wiki/Subroutine" title="Subroutine">functions</a> and <a href="/wiki/Method_(computer_science)" title="Method (computer science)" class="mw-redirect">methods</a> so that whenever a change causes a fault, it can be quickly identified.Readily available unit tests make it easy for the programmer to check whether a piece of code is still working properly.In continuous unit testing environments, through the inherent practice of sustained maintenance, unit tests will continue to accurately reflect the intended use of the executable and code in the face of any change. Depending upon established development practices and unit test coverage, up-to-the-second accuracy can be maintained.<h3>Simplifies integration[<a href="/w/index.php?title=Unit_testing&action=edit&section=4" title="Edit section: Simplifies integration">edit</a>]</h3>Unit testing may reduce uncertainty in the units themselves and can be used in a <a href="/wiki/Top-down_and_bottom-up_design" title="Top-down and bottom-up design">bottom-up</a> testing style approach. By testing the parts of a program first and then testing the sum of its parts, <a href="/wiki/Integration_testing" title="Integration testing">integration testing</a> becomes much easier.[<a href="/wiki/Wikipedia:Citation_needed" title="Wikipedia:Citation needed">citation needed</a>]An elaborate hierarchy of unit tests does not equal integration testing. Integration with peripheral units should be included in integration tests, but not in unit tests.[<a href="/wiki/Wikipedia:Citation_needed" title="Wikipedia:Citation needed">citation needed</a>] Integration testing typically still relies heavily on humans <a href="/wiki/Manual_testing" title="Manual testing">testing manually</a>; high-level or global-scope testing can be difficult to automate, such that manual testing often appears faster and cheaper.[<a href="/wiki/Wikipedia:Citation_needed" title="Wikipedia:Citation needed">citation needed</a>]<h3>Documentation[<a href="/w/index.php?title=Unit_testing&action=edit&section=5" title="Edit section: Documentation">edit</a>]</h3>Unit testing provides a sort of living documentation of the system. Developers looking to learn what functionality is provided by a unit, and how to use it, can look at the unit tests to gain a basic understanding of the unit's interface (<a href="/wiki/Application_programming_interface" title="Application programming interface">API</a>).Unit <a href="/wiki/Test_case" title="Test case">test cases</a> embody characteristics that are critical to the success of the unit. These characteristics can indicate appropriate/inappropriate use of a unit as well as negative behaviors that are to be trapped by the unit. A unit test case, in and of itself, documents these critical characteristics, although many software development environments do not rely solely upon code to document the product in development.<h3>Design[<a href="/w/index.php?title=Unit_testing&action=edit&section=6" title="Edit section: Design">edit</a>]</h3>When software is developed using a test-driven approach, the combination of writing the unit test to specify the interface plus the refactoring activities performed after the test is passing, may take the place of formal design. Each unit test can be seen as a design element specifying classes, methods, and observable behaviour. The following <a href="/wiki/Java_(programming_language)" title="Java (programming language)">Java</a> example will help illustrate this point.Here is a set of test cases that specify a number of elements of the implementation. First, that there must be an interface called Adder, and an implementing class with a zero-argument constructor called AdderImpl. It goes on to <a href="/wiki/Assertion_(computing)" title="Assertion (computing)" class="mw-redirect">assert</a> that the Adder interface should have a method called add, with two integer parameters, which returns another integer. It also specifies the behaviour of this method for a small range of values over a number of test methods.<div dir="ltr" class="mw-geshi mw-code mw-content-ltr"><div class="java source-java"><pre class="de1">public class TestAdder {  // can it add the positive numbers 1 and 1? public void testSumPositiveNumbersOneAndOne() { Adder adder = new AdderImpl(); assert(adder.add(1, 1) == 2); }  // can it add the positive numbers 1 and 2? public void testSumPositiveNumbersOneAndTwo() { Adder adder = new AdderImpl(); assert(adder.add(1, 2) == 3); }  // can it add the positive numbers 2 and 2? public void testSumPositiveNumbersTwoAndTwo() { Adder adder = new AdderImpl(); assert(adder.add(2, 2) == 4); }  // is zero neutral? public void testSumZeroNeutral() { Adder adder = new AdderImpl(); assert(adder.add(0, 0) == 0); }  // can it add the negative numbers -1 and -2? public void testSumNegativeNumbers() { Adder adder = new AdderImpl(); assert(adder.add(-1, -2) == -3); }  // can it add a positive and a negative? public void testSumPositiveAndNegative() { Adder adder = new AdderImpl(); assert(adder.add(-1, 1) == 0); }  // how about larger numbers? public void testSumLargeNumbers() { Adder adder = new AdderImpl(); assert(adder.add(1234, 988) == 2222); }}</pre></div></div>In this case the unit tests, having been written first, act as a design document specifying the form and behaviour of a desired solution, but not the implementation details, which are left for the programmer. Following the "do the simplest thing that could possibly work" practice, the easiest solution that will make the test pass is shown below.<div dir="ltr" class="mw-geshi mw-code mw-content-ltr"><div class="java source-java"><pre class="de1">interface Adder { int add(int a, int b);}class AdderImpl implements Adder { int add(int a, int b) { return a + b; }}</pre></div></div>Unlike other diagram-based design methods, using unit-tests as a design specification has one significant advantage. The design document (the unit-tests themselves) can be used to verify that the implementation adheres to the design. With the unit-test design method, the tests will never pass if the developer does not implement the solution according to the design.It is true that unit testing lacks some of the accessibility of a diagram, but <a href="/wiki/Unified_Modeling_Language" title="Unified Modeling Language">UML</a> diagrams are now easily generated for most modern languages by free tools (usually available as extensions to <a href="/wiki/Integrated_development_environment" title="Integrated development environment">IDEs</a>). Free tools, like those based on the <a href="/wiki/XUnit" title="XUnit">xUnit</a> framework, outsource to another system the graphical rendering of a view for human consumption.<h2>Separation of interface from implementation[<a href="/w/index.php?title=Unit_testing&action=edit&section=7" title="Edit section: Separation of interface from implementation">edit</a>]</h2>Because some classes may have <a href="/wiki/Reference_(computer_science)" title="Reference (computer science)">references</a> to other classes, testing a class can frequently spill over into testing another class. A common example of this is classes that depend on a <a href="/wiki/Database" title="Database">database</a>: in order to test the class, the tester often writes code that interacts with the database. This is a mistake, because a unit test should usually not go outside of its own class boundary, and especially should not cross such process/network boundaries because this can introduce unacceptable performance problems to the unit test-suite. Crossing such unit boundaries turns unit tests into integration tests, and when test cases fail, makes it less clear which component is causing the failure. See also <a href="/wiki/Test-driven_development#Fakes.2C_mocks_and_integration_tests" title="Test-driven development">Fakes, mocks and integration tests</a>Instead, the software developer should create an abstract interface around the database queries, and then implement that interface with their own <a href="/wiki/Mock_object" title="Mock object">mock object</a>. By abstracting this necessary attachment from the code (temporarily reducing the net effective coupling), the independent unit can be more thoroughly tested than may have been previously achieved. This results in a higher quality unit that is also more maintainable.<h2>Parameterized unit testing[<a href="/w/index.php?title=Unit_testing&action=edit&section=8" title="Edit section: Parameterized unit testing">edit</a>]</h2>Parameterized unit tests (PUTs) are tests that take parameters. Unlike traditional unit tests, which are usually closed methods, PUTs take any set of parameters. PUTs have been supported by <a href="/wiki/TestNG" title="TestNG">TestNG</a>, <a href="/wiki/JUnit" title="JUnit">JUnit</a> and various .NET test frameworks. Suitable parameters for the unit tests may be supplied manually or in some cases are automatically generated by the test framework. Testing tools like <a href="/wiki/QuickCheck" title="QuickCheck">QuickCheck</a> exist to generate test inputs for PUTs.<h2>Unit testing limitations[<a href="/w/index.php?title=Unit_testing&action=edit&section=9" title="Edit section: Unit testing limitations">edit</a>]</h2>Testing will not catch every error in the program, since it cannot evaluate every execution path in any but the most trivial programs. The same is true for unit testing. Additionally, unit testing by definition only tests the functionality of the units themselves. Therefore, it will not catch integration errors or broader system-level errors (such as functions performed across multiple units, or non-functional test areas such as <a href="/wiki/Software_performance_testing" title="Software performance testing">performance</a>). Unit testing should be done in conjunction with other <a href="/wiki/Software_testing" title="Software testing">software testing</a> activities, as they can only show the presence or absence of particular errors; they cannot prove a complete absence of errors. In order to guarantee correct behavior for every execution path and every possible input, and ensure the absence of errors, other techniques are required, namely the application of <a href="/wiki/Formal_verification" title="Formal verification">formal methods</a> to proving that a software component has no unexpected behavior.Software testing is a combinatorial problem. For example, every boolean decision statement requires at least two tests: one with an outcome of "true" and one with an outcome of "false". As a result, for every line of code written, programmers often need 3 to 5 lines of test code.<a href="#cite_note-6">[6]</a> This obviously takes time and its investment may not be worth the effort. There are also many problems that cannot easily be tested at all – for example those that are <a href="/wiki/Nondeterministic_algorithm" title="Nondeterministic algorithm">nondeterministic</a> or involve multiple <a href="/wiki/Thread_(computer_science)" title="Thread (computer science)" class="mw-redirect">threads</a>. In addition, code for a unit test is likely to be at least as buggy as the code it is testing. <a href="/wiki/Fred_Brooks" title="Fred Brooks">Fred Brooks</a> in <a href="/wiki/The_Mythical_Man-Month" title="The Mythical Man-Month">The Mythical Man-Month</a> quotes: "Never go to sea with two chronometers; take one or three."<a href="#cite_note-7">[7]</a> Meaning, if two <a href="/wiki/Marine_chronometer" title="Marine chronometer">chronometers</a> contradict, how do you know which one is correct?Another challenge related to writing the unit tests is the difficulty of setting up realistic and useful tests. It is necessary to create relevant initial conditions so the part of the application being tested behaves like part of the complete system. If these initial conditions are not set correctly, the test will not be exercising the code in a realistic context, which diminishes the value and accuracy of unit test results.<a href="#cite_note-8">[8]</a>To obtain the intended benefits from unit testing, rigorous discipline is needed throughout the software development process. It is essential to keep careful records not only of the tests that have been performed, but also of all changes that have been made to the source code of this or any other unit in the software. Use of a <a href="/wiki/Version_control" title="Version control" class="mw-redirect">version control</a> system is essential. If a later version of the unit fails a particular test that it had previously passed, the version-control software can provide a list of the source code changes (if any) that have been applied to the unit since that time.It is also essential to implement a sustainable process for ensuring that test case failures are reviewed daily and addressed immediately.<a href="#cite_note-9">[9]</a> If such a process is not implemented and ingrained into the team's workflow, the application will evolve out of sync with the unit test suite, increasing false positives and reducing the effectiveness of the test suite.Unit testing embedded system software presents a unique challenge: Since the software is being developed on a different platform than the one it will eventually run on, you cannot readily run a test program in the actual deployment environment, as is possible with desktop programs.<a href="#cite_note-10">[10]</a><h2>Applications[<a href="/w/index.php?title=Unit_testing&action=edit&section=10" title="Edit section: Applications">edit</a>]</h2><h3>Extreme programming[<a href="/w/index.php?title=Unit_testing&action=edit&section=11" title="Edit section: Extreme programming">edit</a>]</h3>Unit testing is the cornerstone of <a href="/wiki/Extreme_programming" title="Extreme programming">extreme programming</a>, which relies on an automated <a href="/wiki/List_of_unit_testing_frameworks" title="List of unit testing frameworks">unit testing framework</a>. This automated unit testing framework can be either third party, e.g., <a href="/wiki/XUnit" title="XUnit">xUnit</a>, or created within the development group.Extreme programming uses the creation of unit tests for <a href="/wiki/Test-driven_development" title="Test-driven development">test-driven development</a>. The developer writes a unit test that exposes either a software requirement or a defect. This test will fail because either the requirement isn't implemented yet, or because it intentionally exposes a defect in the existing code. Then, the developer writes the simplest code to make the test, along with other tests, pass.Most code in a system is unit tested, but not necessarily all paths through the code. Extreme programming mandates a "test everything that can possibly break" strategy, over the traditional "test every execution path" method. This leads developers to develop fewer tests than classical methods, but this isn't really a problem, more a restatement of fact, as classical methods have rarely ever been followed methodically enough for all execution paths to have been thoroughly tested.[<a href="/wiki/Wikipedia:Citation_needed" title="Wikipedia:Citation needed">citation needed</a>] Extreme programming simply recognizes that testing is rarely exhaustive (because it is often too expensive and time-consuming to be economically viable) and provides guidance on how to effectively focus limited resources.Crucially, the test code is considered a first class project artifact in that it is maintained at the same quality as the implementation code, with all duplication removed. Developers release unit testing code to the code repository in conjunction with the code it tests. Extreme programming's thorough unit testing allows the benefits mentioned above, such as simpler and more confident code development and <a href="/wiki/Refactoring" title="Refactoring" class="mw-redirect">refactoring</a>, simplified code integration, accurate documentation, and more modular designs. These unit tests are also constantly run as a form of <a href="/wiki/Regression_test" title="Regression test" class="mw-redirect">regression test</a>.Unit testing is also critical to the concept of <a href="/wiki/Emergent_Design" title="Emergent Design">emergent design</a>. As emergent design is heavily dependent upon refactoring, unit tests are an integral component.<a href="#cite_note-11">[11]</a><h3>Techniques[<a href="/w/index.php?title=Unit_testing&action=edit&section=12" title="Edit section: Techniques">edit</a>]</h3>Unit testing is commonly <a href="/wiki/Test_automation" title="Test automation">automated</a>, but may still be performed manually. The <a href="/wiki/Institute_of_Electrical_and_Electronics_Engineers" title="Institute of Electrical and Electronics Engineers">IEEE</a> does not favor one over the other.<a href="#cite_note-12">[12]</a> The objective in unit testing is to isolate a unit and validate its correctness. A manual approach to unit testing may employ a step-by-step instructional document. However, automation is efficient for achieving this, and enables the many benefits listed in this article. Conversely, if not planned carefully, a careless manual unit test case may execute as an integration test case that involves many software components, and thus preclude the achievement of most if not all of the goals established for unit testing.To fully realize the effect of isolation while using an automated approach, the unit or code body under test is executed within a <a href="/wiki/List_of_unit_testing_frameworks" title="List of unit testing frameworks">framework</a> outside of its natural environment. In other words, it is executed outside of the product or calling context for which it was originally created. Testing in such an isolated manner reveals unnecessary dependencies between the code being tested and other units or data spaces in the product. These dependencies can then be eliminated.Using an automation framework, the developer codes criteria into the test to verify the unit's correctness. During test case execution, the framework <a href="/wiki/Computer_data_logging" title="Computer data logging" class="mw-redirect">logs</a> tests that fail any criterion. Many frameworks will also automatically flag these failed test cases and report them in a summary. Depending upon the severity of a failure, the framework may halt subsequent testing.As a consequence, unit testing is traditionally a motivator for programmers to create <a href="/wiki/Coupling_(computer_science)" title="Coupling (computer science)" class="mw-redirect">decoupled</a> and <a href="/wiki/Cohesion_(computer_science)" title="Cohesion (computer science)">cohesive</a> code bodies. This practice promotes healthy habits in software development. <a href="/wiki/Design_pattern_(computer_science)" title="Design pattern (computer science)" class="mw-redirect">Design patterns</a>, unit testing, and refactoring often work together so that the best solution may emerge.<h3>Unit testing frameworks[<a href="/w/index.php?title=Unit_testing&action=edit&section=13" title="Edit section: Unit testing frameworks">edit</a>]</h3><div class="hatnote boilerplate seealso">See also: <a href="/wiki/List_of_unit_testing_frameworks" title="List of unit testing frameworks">List of unit testing frameworks</a></div><table class="metadata plainlinks ambox mbox-small-left ambox-content" role="presentation"><tbody><tr><td class="mbox-image"><a href="/wiki/File:Wiki_letter_w_cropped.svg" class="image"><img alt="[icon]" src="//upload.wikimedia.org/wikipedia/commons/thumb/1/1c/Wiki_letter_w_cropped.svg/20px-Wiki_letter_w_cropped.svg.png" width="20" height="14" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/1/1c/Wiki_letter_w_cropped.svg/30px-Wiki_letter_w_cropped.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/1/1c/Wiki_letter_w_cropped.svg/40px-Wiki_letter_w_cropped.svg.png 2x" data-file-width="44" data-file-height="31"></a></td><td class="mbox-text">This section requires <a class="external text" href="//en.wikipedia.org/w/index.php?title=Unit_testing&action=edit">expansion</a>. (April 2010)</td></tr></tbody></table>Unit testing frameworks are most often third-party products that are not distributed as part of the compiler suite. They help simplify the process of unit testing, having been developed for <a href="/wiki/List_of_unit_testing_frameworks" title="List of unit testing frameworks">a wide variety of languages</a>. Examples of testing frameworks include open source solutions such as the various code-driven testing frameworks known collectively as <a href="/wiki/XUnit" title="XUnit">xUnit</a>, and proprietary/commercial solutions such as <a href="/wiki/LDRA_Testbed" title="LDRA Testbed">TBrun</a>, <a href="/w/index.php?title=Just_mock&action=edit&redlink=1" class="new" title="Just mock (page does not exist)">JustMock</a>, Isolator.NET, Isolator++, <a href="/wiki/Parasoft" title="Parasoft">Parasoft</a> Development Testing (<a href="/wiki/Jtest" title="Jtest">Jtest</a>, <a href="/wiki/Parasoft_C/C%2B%2Btest" title="Parasoft C/C++test">Parasoft C/C++test</a>, dotTEST), Testwell CTA++ and VectorCAST/C++.It is generally possible to perform unit testing without the support of a specific framework by writing client code that exercises the units under test and uses <a href="/wiki/Assertion_(computing)" title="Assertion (computing)" class="mw-redirect">assertions</a>, <a href="/wiki/Exception_handling" title="Exception handling">exception handling</a>, or other <a href="/wiki/Control_flow" title="Control flow">control flow</a> mechanisms to signal failure. Unit testing without a framework is valuable in that there is a <a href="/wiki/Barrier_to_entry" title="Barrier to entry" class="mw-redirect">barrier to entry</a> for the adoption of unit testing; having scant unit tests is hardly better than having none at all, whereas once a framework is in place, adding unit tests becomes relatively easy.<a href="#cite_note-13">[13]</a> In some frameworks many advanced unit test features are missing or must be hand-coded.<h3>Language-level unit testing support[<a href="/w/index.php?title=Unit_testing&action=edit&section=14" title="Edit section: Language-level unit testing support">edit</a>]</h3>Some programming languages directly support unit testing. Their grammar allows the direct declaration of unit tests without importing a library (whether third party or standard). Additionally, the boolean conditions of the unit tests can be expressed in the same syntax as boolean expressions used in non-unit test code, such as what is used for <code>if</code> and <code>while</code> statements.Languages that directly support unit testing include:<ul><li><a href="/wiki/ABAP" title="ABAP">ABAP</a></li><li><a href="/wiki/C_Sharp_(programming_language)" title="C Sharp (programming language)">C#</a></li><li><a href="/wiki/Clojure" title="Clojure">Clojure</a><a href="#cite_note-Clojure_Unit_Testing_Framework-14">[14]</a></li><li><a href="/wiki/D_(programming_language)" title="D (programming language)">D</a></li><li><a href="/wiki/Go_(programming_language)" title="Go (programming language)">Go</a><a href="#cite_note-15">[15]</a></li><li><a href="/wiki/Java_(programming_language)" title="Java (programming language)">Java</a></li><li><a href="/wiki/Obix_programming_language" title="Obix programming language" class="mw-redirect">Obix</a></li><li><a href="/wiki/Python_(programming_language)" title="Python (programming language)">Python</a><a href="#cite_note-16">[16]</a></li><li><a href="/wiki/Racket_(programming_language)" title="Racket (programming language)">Racket</a><a href="#cite_note-Racket_Unit_Testing-17">[17]</a></li><li><a href="/wiki/Ruby_(programming_language)" title="Ruby (programming language)">Ruby</a><a href="#cite_note-18">[18]</a></li><li><a href="/wiki/Rust_(programming_language)" title="Rust (programming language)">Rust</a><a href="#cite_note-19">[19]</a></li><li><a href="/wiki/Scala_(programming_language)" title="Scala (programming language)">Scala</a></li><li><a href="/wiki/Objective-C" title="Objective-C">Objective-C</a></li><li><a href="/wiki/Visual_Basic_.NET" title="Visual Basic .NET">Visual Basic .NET</a></li></ul><h2>See also[<a href="/w/index.php?title=Unit_testing&action=edit&section=15" title="Edit section: See also">edit</a>]</h2><div class="noprint portal tright" style="border:solid #aaa 1px;margin:0.5em 0 0.5em 1em"><table style="background:#f9f9f9;font-size:85%;line-height:110%;max-width:175px"><tbody><tr style="vertical-align:middle"><td style="text-align:center"><a href="/wiki/File:Green_bug_and_broom.svg" class="image"><img alt="Portal icon" src="//upload.wikimedia.org/wikipedia/commons/thumb/8/83/Green_bug_and_broom.svg/32px-Green_bug_and_broom.svg.png" width="32" height="28" class="noviewer" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/8/83/Green_bug_and_broom.svg/48px-Green_bug_and_broom.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/8/83/Green_bug_and_broom.svg/64px-Green_bug_and_broom.svg.png 2x" data-file-width="447" data-file-height="385"></a></td><td style="padding:0 0.2em;vertical-align:middle;font-style:italic;font-weight:bold"><a href="/wiki/Portal:Software_Testing" title="Portal:Software Testing" class="mw-redirect">Software Testing portal</a></td></tr></tbody></table></div><ul><li><a href="/wiki/Acceptance_testing" title="Acceptance testing">Acceptance testing</a></li><li><a href="/wiki/Characterization_test" title="Characterization test">Characterization test</a></li><li><a href="/wiki/Component-Based_Usability_Testing" title="Component-Based Usability Testing" class="mw-redirect">Component-Based Usability Testing</a></li><li><a href="/wiki/Design_predicates" title="Design predicates">Design predicates</a></li><li><a href="/wiki/Design_by_contract" title="Design by contract">Design by contract</a></li><li><a href="/wiki/Extreme_programming" title="Extreme programming">Extreme programming</a></li><li><a href="/wiki/Integration_testing" title="Integration testing">Integration testing</a></li><li><a href="/wiki/List_of_unit_testing_frameworks" title="List of unit testing frameworks">List of unit testing frameworks</a></li><li><a href="/wiki/Regression_testing" title="Regression testing">Regression testing</a></li><li><a href="/wiki/Software_archaeology" title="Software archaeology">Software archaeology</a></li><li><a href="/wiki/Software_testing" title="Software testing">Software testing</a></li><li><a href="/wiki/Test_case" title="Test case">Test case</a></li><li><a href="/wiki/Test-driven_development" title="Test-driven development">Test-driven development</a></li><li><a href="/wiki/XUnit" title="XUnit">xUnit</a> – a family of unit testing frameworks.</li></ul><h2>Notes[<a href="/w/index.php?title=Unit_testing&action=edit&section=16" title="Edit section: Notes">edit</a>]</h2><div class="reflist" style="list-style-type: decimal;"><ol class="references"><li id="cite_note-kolawa-1">^ <a href="#cite_ref-kolawa_1-0">Jump up to: a</a> <a href="#cite_ref-kolawa_1-1">b</a> Kolawa, Adam; Huizinga, Dorota (2007). <a rel="nofollow" class="external text" href="http://www.wiley.com/WileyCDA/WileyTitle/productCd-0470042125.html">Automated Defect Prevention: Best Practices in Software Management</a>. Wiley-IEEE Computer Society Press. p. 426. <a href="/wiki/International_Standard_Book_Number" title="International Standard Book Number">ISBN</a> <a href="/wiki/Special:BookSources/0-470-04212-5" title="Special:BookSources/0-470-04212-5">0-470-04212-5</a>.<span title="ctx_ver=Z39.88-2004&rfr_id=info%3Asid%2Fen.wikipedia.org%3AUnit+testing&rft.aufirst=Adam&rft.au=Huizinga%2C+Dorota&rft.au=Kolawa%2C+Adam&rft.aulast=Kolawa&rft.btitle=Automated+Defect+Prevention%3A+Best+Practices+in+Software+Management&rft.date=2007&rft.genre=book&rft_id=http%3A%2F%2Fwww.wiley.com%2FWileyCDA%2FWileyTitle%2FproductCd-0470042125.html&rft.isbn=0-470-04212-5&rft.pages=426&rft.pub=Wiley-IEEE+Computer+Society+Press&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"> </li><li id="cite_note-2"><a href="#cite_ref-2">Jump up ^</a> <a href="/w/index.php?title=Tao_Xie&action=edit&redlink=1" class="new" title="Tao Xie (page does not exist)">Xie, Tao</a>. <a rel="nofollow" class="external text" href="http://people.engr.ncsu.edu/txie/publications/ast07-diffut.pdf">"Towards a Framework for Differential Unit Testing of Object-Oriented Programs"</a>. Retrieved 2012-07-23.<span title="ctx_ver=Z39.88-2004&rfr_id=info%3Asid%2Fen.wikipedia.org%3AUnit+testing&rft.aufirst=Tao&rft.aulast=Xie&rft.au=Xie%2C+Tao&rft.btitle=Towards+a+Framework+for+Differential+Unit+Testing+of+Object-Oriented+Programs&rft.genre=book&rft_id=http%3A%2F%2Fpeople.engr.ncsu.edu%2Ftxie%2Fpublications%2Fast07-diffut.pdf&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"> </li><li id="cite_note-3"><a href="#cite_ref-3">Jump up ^</a> <a rel="nofollow" class="external text" href="http://guide.agilealliance.org/guide/unittest.html">"Unit Testing"</a>. Retrieved 2014-01-06.<span title="ctx_ver=Z39.88-2004&rfr_id=info%3Asid%2Fen.wikipedia.org%3AUnit+testing&rft.btitle=Unit+Testing&rft.genre=book&rft_id=http%3A%2F%2Fguide.agilealliance.org%2Fguide%2Funittest.html&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"> </li><li id="cite_note-4"><a href="#cite_ref-4">Jump up ^</a> <a rel="nofollow" class="external text" href="http://istqbexamcertification.com/what-is-component-testing/">"ISTQN Exam Certification"</a>. ISTQB Exam Certification. Retrieved 12 March 2015.<span title="ctx_ver=Z39.88-2004&rfr_id=info%3Asid%2Fen.wikipedia.org%3AUnit+testing&rft.atitle=ISTQN+Exam+Certification&rft.genre=article&rft_id=http%3A%2F%2Fistqbexamcertification.com%2Fwhat-is-component-testing%2F&rft.jtitle=ISTQB+Exam+Certification&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal" class="Z3988"> </li><li id="cite_note-mocksarentstubs-5"><a href="#cite_ref-mocksarentstubs_5-0">Jump up ^</a> <a href="/wiki/Martin_Fowler" title="Martin Fowler">Fowler, Martin</a> (2007-01-02). <a rel="nofollow" class="external text" href="http://martinfowler.com/articles/mocksArentStubs.html">"Mocks aren't Stubs"</a>. Retrieved 2008-04-01.<span title="ctx_ver=Z39.88-2004&rfr_id=info%3Asid%2Fen.wikipedia.org%3AUnit+testing&rft.aufirst=Martin&rft.au=Fowler%2C+Martin&rft.aulast=Fowler&rft.btitle=Mocks+aren%27t+Stubs&rft.date=2007-01-02&rft.genre=book&rft_id=http%3A%2F%2Fmartinfowler.com%2Farticles%2FmocksArentStubs.html&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"> </li><li id="cite_note-6"><a href="#cite_ref-6">Jump up ^</a> <a href="/w/index.php?title=Bob_Cramblitt&action=edit&redlink=1" class="new" title="Bob Cramblitt (page does not exist)">Cramblitt, Bob</a> (2007-09-20). <a rel="nofollow" class="external text" href="http://searchsoftwarequality.techtarget.com/originalContent/0,289142,sid92_gci1273161,00.html">"Alberto Savoia sings the praises of software testing"</a>. Retrieved 2007-11-29.<span title="ctx_ver=Z39.88-2004&rfr_id=info%3Asid%2Fen.wikipedia.org%3AUnit+testing&rft.au=Cramblitt%2C+Bob&rft.aufirst=Bob&rft.aulast=Cramblitt&rft.btitle=Alberto+Savoia+sings+the+praises+of+software+testing&rft.date=2007-09-20&rft.genre=book&rft_id=http%3A%2F%2Fsearchsoftwarequality.techtarget.com%2ForiginalContent%2F0%2C289142%2Csid92_gci1273161%2C00.html&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"> </li><li id="cite_note-7"><a href="#cite_ref-7">Jump up ^</a> <a href="/wiki/Fred_Brooks" title="Fred Brooks">Brooks, Frederick J.</a> (1995) [1975]. <a href="/wiki/The_Mythical_Man-Month" title="The Mythical Man-Month">The Mythical Man-Month</a>. Addison-Wesley. p. 64. <a href="/wiki/International_Standard_Book_Number" title="International Standard Book Number">ISBN</a> <a href="/wiki/Special:BookSources/0-201-83595-9" title="Special:BookSources/0-201-83595-9">0-201-83595-9</a>.<span title="ctx_ver=Z39.88-2004&rfr_id=info%3Asid%2Fen.wikipedia.org%3AUnit+testing&rft.au=Brooks%2C+Frederick+J.&rft.aufirst=Frederick+J.&rft.aulast=Brooks&rft.btitle=The+Mythical+Man-Month&rft.date=1995&rft.genre=book&rft.isbn=0-201-83595-9&rft.pages=64&rft.pub=Addison-Wesley&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"> <a class="external text" href="//en.wikipedia.org/w/index.php?title=Template:Cite_isbn/978020183595&action=edit">edit</a></li><li id="cite_note-8"><a href="#cite_ref-8">Jump up ^</a> <a href="/wiki/Adam_Kolawa" title="Adam Kolawa">Kolawa, Adam</a> (2009-07-01). <a rel="nofollow" class="external text" href="http://www.parasoft.com/unit-testing-best-practices">"Unit Testing Best Practices"</a>. Retrieved 2012-07-23.<span title="ctx_ver=Z39.88-2004&rfr_id=info%3Asid%2Fen.wikipedia.org%3AUnit+testing&rft.aufirst=Adam&rft.au=Kolawa%2C+Adam&rft.aulast=Kolawa&rft.btitle=Unit+Testing+Best+Practices&rft.date=2009-07-01&rft.genre=book&rft_id=http%3A%2F%2Fwww.parasoft.com%2Funit-testing-best-practices&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"> </li><li id="cite_note-9"><a href="#cite_ref-9">Jump up ^</a> <a href="/w/index.php?title=Nada_daVeiga&action=edit&redlink=1" class="new" title="Nada daVeiga (page does not exist)">daVeiga, Nada</a> (2008-02-06). <a rel="nofollow" class="external text" href="http://www.ddj.com/development-tools/206105233">"Change Code Without Fear: Utilize a regression safety net"</a>. Retrieved 2008-02-08.<span title="ctx_ver=Z39.88-2004&rfr_id=info%3Asid%2Fen.wikipedia.org%3AUnit+testing&rft.au=daVeiga%2C+Nada&rft.aufirst=Nada&rft.aulast=daVeiga&rft.btitle=Change+Code+Without+Fear%3A+Utilize+a+regression+safety+net&rft.date=2008-02-06&rft.genre=book&rft_id=http%3A%2F%2Fwww.ddj.com%2Fdevelopment-tools%2F206105233&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"> </li><li id="cite_note-10"><a href="#cite_ref-10">Jump up ^</a> <a href="/w/index.php?title=Marek_Kucharski&action=edit&redlink=1" class="new" title="Marek Kucharski (page does not exist)">Kucharski, Marek</a> (2011-11-23). <a rel="nofollow" class="external text" href="http://electronicdesign.com/article/embedded/Making-Unit-Testing-Practical-for-Embedded-Development">"Making Unit Testing Practical for Embedded Development"</a>. Retrieved 2012-05-08.<span title="ctx_ver=Z39.88-2004&rfr_id=info%3Asid%2Fen.wikipedia.org%3AUnit+testing&rft.aufirst=Marek&rft.au=Kucharski%2C+Marek&rft.aulast=Kucharski&rft.btitle=Making+Unit+Testing+Practical+for+Embedded+Development&rft.date=2011-11-23&rft.genre=book&rft_id=http%3A%2F%2Felectronicdesign.com%2Farticle%2Fembedded%2FMaking-Unit-Testing-Practical-for-Embedded-Development&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"> </li><li id="cite_note-11"><a href="#cite_ref-11">Jump up ^</a> <a rel="nofollow" class="external text" href="http://www.agilesherpa.org/agile_coach/engineering_practices/emergent_design/">"Agile Emergent Design"</a>. Agile Sherpa. 2010-08-03. Retrieved 2012-05-08.<span title="ctx_ver=Z39.88-2004&rfr_id=info%3Asid%2Fen.wikipedia.org%3AUnit+testing&rft.btitle=Agile+Emergent+Design&rft.date=2010-08-03&rft.genre=book&rft_id=http%3A%2F%2Fwww.agilesherpa.org%2f*gile_coach%2Fengineering_practices%2Femergent_design%2F&rft.pub=Agile+Sherpa&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"> </li><li id="cite_note-12"><a href="#cite_ref-12">Jump up ^</a> IEEE Standards Board, <a rel="nofollow" class="external text" href="http://s3.amazonaws.com/akitaonrails/files/std1008-1987.pdf">"IEEE Standard for Software Unit Testing: An American National Standard, ANSI/IEEE Std 1008-1987"</a> in IEEE Standards: Software Engineering, Volume Two: Process Standards; 1999 Edition; published by The Institute of Electrical and Electronics Engineers, Inc. Software Engineering Technical Committee of the IEEE Computer Society.</li><li id="cite_note-13"><a href="#cite_ref-13">Jump up ^</a> Bullseye Testing Technology (2006–2008). <a rel="nofollow" class="external text" href="http://www.bullseye.com/coverage.html#intermediate">"Intermediate Coverage Goals"</a>. Retrieved 24 March 2009.<span title="ctx_ver=Z39.88-2004&rfr_id=info%3Asid%2Fen.wikipedia.org%3AUnit+testing&rft.au=Bullseye+Testing+Technology&rft.aulast=Bullseye+Testing+Technology&rft.btitle=Intermediate+Coverage+Goals&rft.date=2006-2008&rft.genre=book&rft_id=http%3A%2F%2Fwww.bullseye.com%2Fcoverage.html%23intermediate&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"> </li><li id="cite_note-Clojure_Unit_Testing_Framework-14"><a href="#cite_ref-Clojure_Unit_Testing_Framework_14-0">Jump up ^</a> Sierra, Stuart. <a rel="nofollow" class="external text" href="http://clojure.github.io/clojure/clojure.test-api.html">"API for clojure.test - Clojure v1.6 (stable)"</a>. Retrieved 11 February 2015.<span title="ctx_ver=Z39.88-2004&rfr_id=info%3Asid%2Fen.wikipedia.org%3AUnit+testing&rft.aufirst=Stuart&rft.aulast=Sierra&rft.au=Sierra%2C+Stuart&rft.btitle=API+for+clojure.test+-+Clojure+v1.6+%28stable%29&rft.genre=book&rft_id=http%3A%2F%2Fclojure.github.io%2Fclojure%2Fclojure.test-api.html&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"> </li><li id="cite_note-15"><a href="#cite_ref-15">Jump up ^</a> golang.org. <a rel="nofollow" class="external text" href="http://golang.org/pkg/testing/">"testing - The Go Programming Language"</a>. Retrieved 3 December 2013.<span title="ctx_ver=Z39.88-2004&rfr_id=info%3Asid%2Fen.wikipedia.org%3AUnit+testing&rft.au=golang.org&rft.aulast=golang.org&rft.btitle=testing+-+The+Go+Programming+Language&rft.genre=book&rft_id=http%3A%2F%2Fgolang.org%2Fpkg%2Ftesting%2F&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"> </li><li id="cite_note-16"><a href="#cite_ref-16">Jump up ^</a> Python Documentation (1999–2012). <a rel="nofollow" class="external text" href="https://docs.python.org/2/library/unittest.html">"unittest -- Unit testing framework"</a>. Retrieved 15 November 2012.<span title="ctx_ver=Z39.88-2004&rfr_id=info%3Asid%2Fen.wikipedia.org%3AUnit+testing&rft.aulast=Python+Documentation&rft.au=Python+Documentation&rft.btitle=unittest+--+Unit+testing+framework&rft.date=1999-2012&rft.genre=book&rft_id=https%3A%2F%2Fdocs.python.org%2F2%2Flibrary%2Funittest.html&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"> </li><li id="cite_note-Racket_Unit_Testing-17"><a href="#cite_ref-Racket_Unit_Testing_17-0">Jump up ^</a> Welsh, Noel; Culpepper, Ryan. <a rel="nofollow" class="external text" href="http://docs.racket-lang.org/rackunit/index.html?q=unit-testing">"RackUnit: Unit Testing"</a>. PLT Design Inc. Retrieved 11 February 2015.<span title="ctx_ver=Z39.88-2004&rfr_id=info%3Asid%2Fen.wikipedia.org%3AUnit+testing&rft.au=Culpepper%2C+Ryan&rft.aufirst=Noel&rft.aulast=Welsh&rft.au=Welsh%2C+Noel&rft.btitle=RackUnit%3A+Unit+Testing&rft.genre=book&rft_id=http%3A%2F%2Fdocs.racket-lang.org%2Frackunit%2Findex.html%3Fq%3Dunit-testing&rft.pub=PLT+Design+Inc.&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"> </li><li id="cite_note-18"><a href="#cite_ref-18">Jump up ^</a> Ruby-Doc.org. <a rel="nofollow" class="external text" href="http://ruby-doc.org/stdlib-2.0/libdoc/test/unit/rdoc/Test/Unit/Assertions.html">"Module: Test::Unit::Assertions (Ruby 2.0)"</a>. Retrieved 19 August 2013.<span title="ctx_ver=Z39.88-2004&rfr_id=info%3Asid%2Fen.wikipedia.org%3AUnit+testing&rft.aulast=Ruby-Doc.org&rft.au=Ruby-Doc.org&rft.btitle=Module%3A+Test%3A%3AUnit%3A%3AAssertions+%28Ruby+2.0%29&rft.genre=book&rft_id=http%3A%2F%2Fruby-doc.org%2Fstdlib-2.0%2Flibdoc%2Ftest%2Funit%2Frdoc%2FTest%2FUnit%2FAssertions.html&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"> </li><li id="cite_note-19"><a href="#cite_ref-19">Jump up ^</a> The Rust Project Developers (2011–2014). <a rel="nofollow" class="external text" href="http://static.rust-lang.org/doc/master/guide-testing.html">"The Rust Testing Guide (Rust 0.12.0-pre-nightly)"</a>. Retrieved 12 August 2014.<span title="ctx_ver=Z39.88-2004&rfr_id=info%3Asid%2Fen.wikipedia.org%3AUnit+testing&rft.aulast=The+Rust+Project+Developers&rft.au=The+Rust+Project+Developers&rft.btitle=The+Rust+Testing+Guide+%28Rust+0.12.0-pre-nightly%29&rft.date=2011-2014&rft.genre=book&rft_id=http%3A%2F%2Fstatic.rust-lang.org%2Fdoc%2Fmaster%2Fguide-testing.html&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"> </li></ol></div><h2>External links[<a href="/w/index.php?title=Unit_testing&action=edit&section=17" title="Edit section: External links">edit</a>]</h2><ul><li><a rel="nofollow" class="external text" href="http://c2.com/cgi/wiki?TestDrivenDevelopment">Test Driven Development (Ward Cunningham's Wiki)</a></li></ul>NewPP limit reportParsed by mw1149CPU time usage: 0.512 secondsReal time usage: 0.612 secondsPreprocessor visited node count: 2274/1000000Preprocessor generated node count: 0/1500000Post‐expand include size: 62232/2097152 bytesTemplate argument size: 5133/2097152 bytesHighest expansion depth: 19/40Expensive parser function count: 12/500Lua time usage: 0.155/10.000 secondsLua memory usage: 4.26 MB/50 MB-->Transclusion expansion time report (%,ms,calls,template)100.00% 477.561 1 - -total 35.26% 168.388 1 - Template:Reflist 34.20% 163.303 4 - Template:Ambox 27.21% 129.958 1 - Template:Multiple_issues 13.40% 64.003 16 - Template:Cite_web 10.47% 50.004 9 - Template:Category_handler 9.43% 45.016 1 - Template:Cleanup 8.26% 39.468 4 - Template:Citation_needed 7.00% 33.419 2 - Template:Cite_book 6.55% 31.297 1 - Template:Refimprove--> --><noscript><img src="//en.wikipedia.org/wiki/Special:CentralAutoLogin/start?type=1x1" alt="" title="" width="1" height="1" style="border: none; position: absolute;" /></noscript></div> <div class="printfooter"> Retrieved from "<a dir="ltr" href="http://en.wikipedia.org/w/index.php?title=Unit_testing&oldid=651088294">http://en.wikipedia.org/w/index.php?title=Unit_testing&oldid=651088294</a>" </div> <div id="catlinks" class="catlinks"><div id="mw-normal-catlinks" class="mw-normal-catlinks"><a href="/wiki/Help:Category" title="Help:Category">Categories</a>: <ul><li><a href="/wiki/Category:Extreme_programming" title="Category:Extreme programming">Extreme programming</a></li><li><a href="/wiki/Category:Software_testing" title="Category:Software testing">Software testing</a></li><li><a href="/wiki/Category:Unit_testing" title="Category:Unit testing">Unit testing</a></li></ul></div><div id="mw-hidden-catlinks" class="mw-hidden-catlinks mw-hidden-cats-hidden">Hidden categories: <ul><li><a href="/wiki/Category:Pages_using_duplicate_arguments_in_template_calls" title="Category:Pages using duplicate arguments in template calls">Pages using duplicate arguments in template calls</a></li><li><a href="/wiki/Category:Articles_needing_additional_references_from_November_2007" title="Category:Articles needing additional references from November 2007">Articles needing additional references from November 2007</a></li><li><a href="/wiki/Category:All_articles_needing_additional_references" title="Category:All articles needing additional references">All articles needing additional references</a></li><li><a href="/wiki/Category:Articles_needing_cleanup_from_July_2009" title="Category:Articles needing cleanup from July 2009">Articles needing cleanup from July 2009</a></li><li><a href="/wiki/Category:All_articles_needing_cleanup" title="Category:All articles needing cleanup">All articles needing cleanup</a></li><li><a href="/wiki/Category:Cleanup_tagged_articles_without_a_reason_field_from_July_2009" title="Category:Cleanup tagged articles without a reason field from July 2009">Cleanup tagged articles without a reason field from July 2009</a></li><li><a href="/wiki/Category:Wikipedia_pages_needing_cleanup_from_July_2009" title="Category:Wikipedia pages needing cleanup from July 2009">Wikipedia pages needing cleanup from July 2009</a></li><li><a href="/wiki/Category:All_articles_with_unsourced_statements" title="Category:All articles with unsourced statements">All articles with unsourced statements</a></li><li><a href="/wiki/Category:Articles_with_unsourced_statements_from_January_2013" title="Category:Articles with unsourced statements from January 2013">Articles with unsourced statements from January 2013</a></li><li><a href="/wiki/Category:Articles_with_unsourced_statements_from_October_2010" title="Category:Articles with unsourced statements from October 2010">Articles with unsourced statements from October 2010</a></li><li><a href="/wiki/Category:Articles_with_unsourced_statements_from_January_2010" title="Category:Articles with unsourced statements from January 2010">Articles with unsourced statements from January 2010</a></li><li><a href="/wiki/Category:Articles_with_unsourced_statements_from_November_2008" title="Category:Articles with unsourced statements from November 2008">Articles with unsourced statements from November 2008</a></li><li><a href="/wiki/Category:Articles_to_be_expanded_from_April_2010" title="Category:Articles to be expanded from April 2010">Articles to be expanded from April 2010</a></li><li><a href="/wiki/Category:All_articles_to_be_expanded" title="Category:All articles to be expanded">All articles to be expanded</a></li><li><a href="/wiki/Category:Use_dmy_dates_from_January_2011" title="Category:Use dmy dates from January 2011">Use dmy dates from January 2011</a></li></ul></div></div> <div class="visualClear"></div> </div> </div>[/dohtml]

Last Edit: Mar 24, 2015 23:57:19 GMT -5 by Eton Bones

test

Eton Bones Administrator "Please apologize for your stupidity, there are many, thank you" Posts: 140	Vid Apr 3, 2015 17:57:09 GMT -5 Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by Eton Bones on Apr 3, 2015 17:57:09 GMT -5 [pod]2015-04-03T12_55_15-07_00[/pod]
	Last Edit: Apr 5, 2015 1:27:54 GMT -5 by Eton Bones test

Eton Bones Administrator "Please apologize for your stupidity, there are many, thank you" Posts: 140	Vid Apr 7, 2015 19:50:44 GMT -5 Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by Eton Bones on Apr 7, 2015 19:50:44 GMT -5
	Last Edit: Apr 7, 2015 23:41:37 GMT -5 by Eton Bones test

Eton Bones Administrator "Please apologize for your stupidity, there are many, thank you" Posts: 140	Vid Apr 7, 2015 22:15:49 GMT -5 Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by Eton Bones on Apr 7, 2015 22:15:49 GMT -5
	Last Edit: Apr 8, 2015 10:28:17 GMT -5 by Eton Bones test

Eton Bones Administrator "Please apologize for your stupidity, there are many, thank you" Posts: 140	Vid Apr 9, 2015 17:37:53 GMT -5 Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by Eton Bones on Apr 9, 2015 17:37:53 GMT -5 [pdfview]http://www.analysis.im/uploads/seminar/pdf-sample.pdf[/pdfview]
	test

Eton Bones Administrator "Please apologize for your stupidity, there are many, thank you" Posts: 140	Vid Apr 10, 2015 14:56:25 GMT -5 Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by Eton Bones on Apr 10, 2015 14:56:25 GMT -5 PCaDPxEz
	test

Eton Bones Administrator "Please apologize for your stupidity, there are many, thank you" Posts: 140	Vid Apr 10, 2015 15:04:09 GMT -5 Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by Eton Bones on Apr 10, 2015 15:04:09 GMT -5 w9sTgbvd
	test

Eton Bones Administrator "Please apologize for your stupidity, there are many, thank you" Posts: 140	Vid Apr 10, 2015 15:18:55 GMT -5 Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by Eton Bones on Apr 10, 2015 15:18:55 GMT -5 GA9BZzSA Lorem ipsum dolor sit amet, non dum animae ait est amet Cur meae ad te princeps coniungitur vestra felicitate facientibus nulla facilius de his carpens
	test

Eton Bones Administrator "Please apologize for your stupidity, there are many, thank you" Posts: 140	Vid Apr 10, 2015 17:39:50 GMT -5 Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by Eton Bones on Apr 10, 2015 17:39:50 GMT -5 J6ez52Sp
	test

Eton Bones Administrator "Please apologize for your stupidity, there are many, thank you" Posts: 140	Vid Apr 10, 2015 17:44:08 GMT -5 Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by Eton Bones on Apr 10, 2015 17:44:08 GMT -5 G9u_INQ4
	test

Eton Bones Administrator "Please apologize for your stupidity, there are many, thank you" Posts: 140	Vid Apr 11, 2015 9:10:33 GMT -5 Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by Eton Bones on Apr 11, 2015 9:10:33 GMT -5 q3n9ClIB
	test

Eton Bones Administrator "Please apologize for your stupidity, there are many, thank you" Posts: 140	Vid Apr 11, 2015 9:26:10 GMT -5 Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by Eton Bones on Apr 11, 2015 9:26:10 GMT -5 dwnKzC64
	test