The lead sentence about data-driven testing was incorrect in its reference to a framework rather than a methodology. Changed table-driven to keyword-driven which is more widely used.
'''Data-driven testing''' is a frameworkmethodology used in [[Test automation]] where [[Test script|test inputscripts]] are executed and outputverified based on the data values arestored readin fromone or more central data filessources or [[Database|databases]]. These databases can range from (datapools, [[Open Database Connectivity|ODBC]] sources, [[Comma-separated values|csv files]], [[Microsoft Office Excel|Excel]] files, [[Data Access Object|DAO]] objects, [[ActiveX Data Objects|ADO]] objects, and such). andThe areestablishment loadedof intoseveral variablesinteracting test scripts together with their related data results in captureda orframework manuallyused codedfor scriptsthe methodology. In this framework, variables are used for both input values and output verification values.: Navigationnavigation through the [[System Under Test|program]], reading of the data filessources, and logging of test status and information are all coded in the test script. Thus, the logic executed in the script is also dependant on the data values.
This is similar to table[[Keyword-driven testing]] in that the test case is contained in the data filevalues and not in the test script; the script is just a "driver," or delivery mechanism, for the data. Unlike in tablekeyword-driven testing, though, the navigation data isn't contained in the tabletest structurescript. In data-driven testing, only test data is contained in the data filessource.
