Test suite

<h2 id="types">Types</h2>
<p>Occasionally, test suites are used to group similar test cases together. A system might have a smoke test suite that consists only of <a href="/facts/Smoke_testing_(software)/kWJBtv3m">smoke tests</a> or a test suite for some specific functionality in the system. It may also contain all tests and signify if a test should be used as a smoke test or for some specific functionality.
</p><p>In <a href="/facts/Model-based_testing/fzRyEpU8">model-based testing</a>, one distinguishes between <i>abstract test suites</i>, which are collections of abstract test cases derived from a high-level model of the <a href="/facts/System_under_test/tyuXCvy9">system under test</a>, and <i>executable test suites</i>, which are derived from abstract test suites by providing the concrete, lower-level details needed to execute this suite by a program.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> An abstract test suite cannot be directly used on the actual <a href="/facts/System_under_test/tyuXCvy9">system under test</a> (SUT) because abstract test cases remain at a high abstraction level and lack concrete details about the SUT and its environment. An executable test suite must work on a sufficiently detailed level to correctly communicate with the SUT and a <a href="/facts/Test_harness/AyrtsIcR">test harness</a> is usually present to interface the executable test suite with the SUT.
</p><p>A test suite for a <a href="/facts/Primality/L20FLkgn">primality</a> testing <a href="/facts/Subroutine/9vFJrg0A">subroutine</a> might consist of a list of numbers and their primality (prime or composite), along with a testing subroutine. The testing subroutine would supply each number in the list to the primality tester, and verify that the result of each test is correct.
</p>
<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Scenario_test/59Hgq31c">Scenario test</a></li>
<li><a href="/facts/Software_testing/VoXzG9Tb">Software testing</a></li>
<li><a href="/facts/Test_case/TVWkj0AQ">Test case</a></li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1"><p>Pinto, Leandro Sales; Sinha, Saurabh; Orso, Alessandro (11 November 2012). "Understanding myths and realities of test-suite evolution". Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering. Association for Computing Machinery. pp. 1–11. doi:10.1145/2393596.2393634. ISBN 9781450316149. S2CID 9072512. <a href="9781450316149" target="_blank">9781450316149</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li>
<li id="fn:2"><p>Hakim Kahlouche, César Viho, and Massimo Zendri, "An Industrial Experiment in Automatic Generation of Executable Test Suites for a Cache Coherency Protocol", Proc. International Workshop on Testing of Communicating Systems (IWTCS'98), Tomsk, Russia, September 1998. <a href="http://cadp.inria.fr/vasy/publications/Kahlouche-Viho-Zendri-98.html" target="_blank">http://cadp.inria.fr/vasy/publications/Kahlouche-Viho-Zendri-98.html</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li>
</ol>

Test suite open-in-new

Test suite