Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Software testing
open-in-new
<p>Software testing is the act of checking whether <a href="/facts/Software/RP79lVSW">software</a> satisfies expectations. </p><p>Software testing can provide objective, independent information about the <a href="/facts/Quality_(business)/V3IzcDc3">quality</a> of software and the <a href="/facts/Risk/tbBEDA0V">risk</a> of its failure to a <a href="/facts/User_(computing)/zQRzG0KG">user</a> or sponsor. </p><p>Software testing can determine the <a href="/facts/Correctness_(computer_science)/m4yxw3gw">correctness</a> of software for specific <a href="/facts/Scenario_(computing)/TqGyhf23">scenarios</a> but cannot determine correctness for all scenarios. It cannot find all <a href="/facts/Software_bug/I1uSXySv">bugs</a>. </p><p>Based on the criteria for measuring correctness from an <a href="/facts/Test_oracle/rR9jNEma">oracle</a>, software testing employs principles and mechanisms that might recognize a problem. Examples of oracles include <a href="/facts/Specification/xEMUsktp">specifications</a>, <a href="/facts/Design_by_Contract/PjacMRRd">contracts</a>, comparable products, past versions of the same product, inferences about intended or expected purpose, user or customer expectations, relevant standards, and applicable laws. </p><p>Software testing is often dynamic in nature; running the software to verify actual output matches expected. It can also be static in nature; reviewing <a href="/facts/Source_code/o9J6Jv23">code</a> and its associated <a href="/facts/Documentation/IdrD9jer">documentation</a>. </p><p>Software testing is often used to answer the question: Does the software do what it is supposed to do and what it needs to do? </p><p>Information learned from software testing may be used to improve the process by which software is developed.: 41–43 </p><p>Software testing should follow a "pyramid" approach wherein most of your tests should be <a href="/facts/Unit_tests/SYoGGS3T">unit tests</a>, followed by <a href="/facts/Integration_testing/FcPo9Fmn">integration tests</a> and finally <a href="/facts/End-to-end_testing/ThxRDsAy">end-to-end (e2e) tests</a> should have the lowest proportion. </p>