Data-driven testing

<h2 id="introduction">Introduction</h2>
<p>In the testing of <a href="/facts/Computer_software/RP79lVSW">software</a> or <a href="/facts/Computer_program/e38jH9N9">programs</a>, several methodologies are available for implementing this testing. Each of these methods co-exist because they differ in the effort required to create and subsequently maintain. The advantage of Data-driven testing is the ease to add additional inputs to the table when new partitions are discovered or added to the product or <a href="/facts/System_under_test/tyuXCvy9">system under test</a>. Also, in the data-driven testing process, the test environment settings and control are not hard-coded. The cost aspect makes DDT cheap for automation but expensive for manual testing.
</p>
<h2 id="methodology-overview">Methodology overview</h2>
<p>Data-driven testing is the creation of test scripts to run together with their related data sets in a framework. The framework provides re-usable test logic to reduce maintenance and improve test coverage. Input and result (test criteria) data values can be stored in one or more central data sources or <a href="/facts/Database/VYcpkevb">databases</a>, the actual format, organization and tools can be implementation specific.
</p><p>The data comprises variables used for both input values and output verification values. In advanced (mature) automation environments data can be harvested from a running system using a purpose-built custom tool or sniffer, the DDT framework thus performs playback of harvested data producing a powerful automated regression testing tool.
</p><p>Automated test suites contain user's interactions through the system's GUI, for repeatable testing. Each test begins with a copy of the "before" image reference database. The "user interactions" are replayed through the "new" GUI version and result in the "post test" database. The <i>reference</i> "post test" database is compared to the "post test" database, using a tool.<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a> Differences reveal probable regression.
</p><p>Navigation through the <a href="/facts/System_Under_Test/tyuXCvy9">program</a>, reading of the data sources, and logging of test status and information are all coded in the test script.
</p>
<h2 id="data-driven">Data driven</h2>
<p>Anything that has a potential to change (also called "variability," and includes elements such as environment, end points, test data, locations, etc.) is separated out from the test logic (scripts) and moved into an 'external asset'. This can be a configuration or test dataset. The logic executed in the script is dictated by the data values.
</p><p><a href="/facts/Keyword-driven_testing/yLtnfzN0">Keyword-driven testing</a> is similar except that the logic for the test case itself is encoded as data values in the form of a set of "action words", and not embedded or "hard-coded" in the test script. The script is simply a "driver" (or delivery mechanism) for the data that is held in the data source.
</p><p>The databases used for data-driven testing can include:
</p>
<ul><li><a href="/facts/Data_pool/oIWhAf40">Data pools</a></li>
<li><a href="/facts/Data_access_object/x82qDLxx">DAO</a> objects</li>
<li><a href="/facts/ActiveX_Data_Objects/dU8V95sx">ADO</a> objects</li></ul>
<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Control_table/AMkFG0mQ">Control table</a></li>
<li><a href="/facts/Keyword-driven_testing/yLtnfzN0">Keyword-driven testing</a></li>
<li><a href="/facts/Test_automation_framework/UAVXbSTV">Test automation framework</a></li>
<li><a href="/facts/Test-driven_development/fDCzXkt1">Test-driven development</a></li>
<li>Metadata-driven testing</li>
<li><a href="/facts/Modularity-driven_testing/JhHvmNBd">Modularity-driven testing</a></li>
<li><a href="/facts/Model-based_testing/fzRyEpU8">Model-based testing</a></li></ul>

<ul><li>Carl Nagle: <i>Test Automation Frameworks</i><a href="http://safsdev.sourceforge.net/FRAMESDataDrivenTestAutomationFrameworks.htm">[1]</a>, Software Automation Framework Support on SourceForge <a href="http://safsdev.sourceforge.net/Default.htm">[2]</a>, Data-driven testing approach <a href="https://www.katalon.com/resources-center/tutorials/data-driven-testing/#">[3]</a></li></ul>

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

<ol>
<li id="fn:1"><p>"golang/go TableDrivenTests". GitHub. <a href="https://github.com/golang/go/wiki/TableDrivenTests" target="_blank">https://github.com/golang/go/wiki/TableDrivenTests</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li>
<li id="fn:2"><p>"JUnit 5 User Guide". junit.org. <a href="https://junit.org/junit5/docs/current/user-guide/#writing-tests-parameterized-tests" target="_blank">https://junit.org/junit5/docs/current/user-guide/#writing-tests-parameterized-tests</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li>
<li id="fn:3"><p>"Home". diffkit.org. <a href="http://www.diffkit.org/" target="_blank">http://www.diffkit.org/</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li>
</ol>

Data-driven testing open-in-new

Data-driven testing