<p>&nbsp;</p>

<p><ins class="ice-ins ice-cts-1" data-changedata="" data-cid="333" data-last-change-time="1554738592929" data-time="1554738592929" data-userid="162" data-username="Author"><b>Software testing</b>&nbsp;is an investigation conducted to provide stakeholders with information about the&nbsp;<a href="https://en.wikipedia.org/wiki/Software_quality" title="Software quality">quality</a>&nbsp;of the&nbsp;<a href="https://en.wikipedia.org/wiki/Software" title="Software">software</a>&nbsp;product or service under test.<sup id="cite_ref-Kaner_1_1-0"><a href="https://en.wikipedia.org/wiki/Software_testing#cite_note-Kaner_1-1">[1]</a></sup>&nbsp;Software testing can also provide an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation. Test techniques include the process of executing a program or application with the intent of finding&nbsp;<a href="https://en.wikipedia.org/wiki/Software_bug" title="Software bug">software bugs</a>&nbsp;(errors or other defects), and verifying that the software product is fit for use.</ins></p>

<p><ins class="ice-ins ice-cts-1" data-changedata="" data-cid="333" data-last-change-time="1554738592929" data-time="1554738592929" data-userid="162" data-username="Author">Software testing involves the execution of a software component or system component to evaluate one or more properties of interest. In general, these properties indicate the extent to which the component or system under test:</ins></p>

<ul>
	<li><ins class="ice-ins ice-cts-1" data-changedata="" data-cid="333" data-last-change-time="1554738592929" data-time="1554738592929" data-userid="162" data-username="Author">meets the requirements that guided its design and development,</ins></li>
	<li><ins class="ice-ins ice-cts-1" data-changedata="" data-cid="333" data-last-change-time="1554738592929" data-time="1554738592929" data-userid="162" data-username="Author">responds correctly to all kinds of inputs,</ins></li>
	<li><ins class="ice-ins ice-cts-1" data-changedata="" data-cid="333" data-last-change-time="1554738592929" data-time="1554738592929" data-userid="162" data-username="Author">performs its functions within an acceptable time,</ins></li>
	<li><ins class="ice-ins ice-cts-1" data-changedata="" data-cid="333" data-last-change-time="1554738592929" data-time="1554738592929" data-userid="162" data-username="Author">it is sufficiently usable,</ins></li>
	<li><ins class="ice-ins ice-cts-1" data-changedata="" data-cid="333" data-last-change-time="1554738592929" data-time="1554738592929" data-userid="162" data-username="Author">can be installed and run in its intended&nbsp;<a href="https://en.wikipedia.org/wiki/Operating_environment" title="Operating environment">environments</a>, and</ins></li>
	<li><ins class="ice-ins ice-cts-1" data-changedata="" data-cid="333" data-last-change-time="1554738592929" data-time="1554738592929" data-userid="162" data-username="Author">achieves the general result its stakeholders desire.</ins></li>
</ul>

<p><ins class="ice-ins ice-cts-1" data-changedata="" data-cid="333" data-last-change-time="1554738592929" data-time="1554738592929" data-userid="162" data-username="Author">As the number of possible tests for even simple software components is practically infinite, all software testing uses some strategy to select tests that are feasible for the available time and resources. As a result, software testing typically (but not exclusively) attempts to execute a program or application with the intent of finding&nbsp;<a href="https://en.wikipedia.org/wiki/Software_bug" title="Software bug">software bugs</a>&nbsp;(errors or other defects). The job of testing is an iterative process as when one bug is fixed, it can illuminate other, deeper bugs, or can even create new ones.</ins></p>

<p><ins class="ice-ins ice-cts-1" data-changedata="" data-cid="333" data-last-change-time="1554738592929" data-time="1554738592929" data-userid="162" data-username="Author">Software testing can provide objective, independent information about the quality of software and risk of its failure to users or sponsors.<sup id="cite_ref-Kaner_1_1-1"><a href="https://en.wikipedia.org/wiki/Software_testing#cite_note-Kaner_1-1">[1]</a></sup></ins></p>

<p><ins class="ice-ins ice-cts-1" data-changedata="" data-cid="333" data-last-change-time="1554738592929" data-time="1554738592929" data-userid="162" data-username="Author">Software testing can be conducted as soon as executable software (even if partially complete) exists. The&nbsp;<a href="https://en.wikipedia.org/wiki/Software_development_process" title="Software development process">overall approach to software development</a>&nbsp;often determines when and how testing is conducted. For example, in a phased process, most testing occurs after system requirements have been defined and then implemented in testable programs. In contrast, under an&nbsp;<a href="https://en.wikipedia.org/wiki/Agile_software_development" title="Agile software development">agile approach</a>, requirements, programming, and testing are often done concurrently</ins></p>

<p>&nbsp;</p>

<p>&nbsp;</p>

<p>&nbsp;</p>

<p>&nbsp;</p>
