Data-driven testing: Difference between revisions

Revision as of 23:50, 23 March 2016

Latest revision as of 11:36, 16 August 2025

(31 intermediate revisions by 17 users not shown)

Line 1:

'''Data-driven testing''' (DDT), also known as '''table-driven testing''' or '''parameterized testing''', is a [[software testing]] technique that uses a table of [[data]] that directs test execution by encoding input, expected output and test-environment settings.<ref>{{cite web |title=golang/go TableDrivenTests |url=https://github.com/golang/go/wiki/TableDrivenTests |website=GitHub |language=en}}</ref><ref>{{cite web |title=JUnit 5 User Guide |url=https://junit.org/junit5/docs/current/user-guide/#writing-tests-parameterized-tests |website=junit.org}}</ref> One advantage of DDT over other testing techniques is relative ease to cover an additional [[test case (software)|test case]] for the [[system under test]] by adding a line to a table instead of having to modify test [[source code]].

'''Data-driven testing'' (DDT) is a term used in the testing of [[computer]] [[software]] to describe testing done using a table of conditions directly as test inputs and verifiable outputs as well as the process where test environment settings and control are not hard-coded. In the simplest form the tester supplies the inputs from a row in the table and expects the outputs which occur in the same row. The table typically contains values which correspond to boundary or partition input spaces. In the control methodology, test configuration is "read" from a database.

Often, a table provides a complete set of stimulus input and expected outputs in each row of the table. Stimulus input values typically cover values that correspond to boundary or partition input spaces.

==Introduction==

In the testing of [[Computer software|software]] or [[Computer program|programs]], 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 [[System Under Test]]. The cost aspect makes DDT cheap for automation but expensive for manual testing.

DDT involves a [[software framework |framework]] that executes tests based on input data. The framework is a [[software reuse |re-usable]] test asset that can reduce maintenance of a test [[codebase]]. DDT allows for anything that has a potential to change to be segregated from the framework; stored in an external asset. The framework might manage storage of tables and test results in a [[database]] such as [[data pool]], [[Data access object |DAO]] and [[ActiveX Data Objects |ADO]]. An advanced framework might harvest data from a running system using a purpose-built tool (sniffer). The DDT framework can playback harvested data for [[regression testing]].

==Methodology Overview==

* '''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 [[database]]s, the actual format and organisation can be implementation specific.

Automated test suites contain user 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 ''reference'' "post test" database is compared to the "post test" database, using a tool.<ref>{{cite web |url=http://www.diffkit.org/ |title=Home |website=diffkit.org}}</ref> Differences reveal probable regression. Navigation the [[System Under Test]] user interface, reading data sources, and logging test findings may be coded in the table.

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.

Navigation through the [[System Under Test|program]], reading of the data sources, and logging of test status and information are all coded in the test script.

[[Keyword-driven testing]] 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.

==Data Driven==

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. [[Keyword-driven testing]] is similar except that the test case is contained in the set of data values and not embedded or "hard-coded" in the test script itself. The script is simply a "driver" (or delivery mechanism) for the data that is held in the data source.

The databases used for data-driven testing can include:

* [[Data pool]]s

* [[Data Access Object|DAO]] objects

* [[ActiveX Data Objects|ADO]] objects

==See also==

* [[{{Annotated link |Control table]]}}

{{Portal|Software Testing}}

* [[{{Annotated link |Keyword-driven testing]]}}

* [[Control table]]

* [[{{Annotated link |Test automation framework]]}}

* [[Keyword-driven testing]]

* [[{{Annotated link |Test-driven development]]}}

* [[Test automation framework]]

* [[{{Annotated link |Modularity-driven testing]]}}

* [[Test-driven development]]

* [[Metadata{{Annotated link |Model-drivenbased testing]]}}

* [[Modularity-driven testing]]

* [[Hybrid testing]]

* [[Model-based testing]]

==References==

{{reflistReflist}}

{{refbegin}}

* Carl Nagle: ''Test Automation Frameworks''[httphttps://safsdev.sourceforge.net/FRAMESDataDrivenTestAutomationFrameworks.htm], Software Automation Framework Support on SourceForge [http://safsdev.sourceforge.net/Default.htm], Data-driven testing approach [https://www.katalon.com/resources-center/tutorials/data-driven-testing/#]{{refend}}

{{refend}}

[[Category:Software testing]]