Data-driven testing: Difference between revisions

Revision as of 23:40, 7 August 2025

Revision as of 09:19, 8 August 2025

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]] to direct test execution by specifying input, expected outputs 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> The multitude of techniques for testing [[software]] co-exist because they differ in the effort required to create and subsequently maintain. One advantage of data-driven testing isover other testing techniques theis relative ease to cover an additional [[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.