Data-driven testing: Difference between revisions

Content deleted Content added
Edit for brevity and flow
 
(2 intermediate revisions by 2 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]].
 
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.
Line 10:
 
==See also==
* [[{{Annotated link |Control table]]}}
 
* [[{{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]]
* [[Modularity{{Annotated link |Model-drivenbased testing]]}}
* [[Model-based testing]]
 
==References==
{{Reflist}}
{{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}}
 
[[Category:Software testing]]