Content deleted Content added
Yorkyabroad (talk | contribs) →See also: Removing link to hybrid testing - the article has been listed as confusing since 2015, it is not referenced or defined (in the article) and so adds no value in this article. |
Jack Baflon (talk | contribs) m add more details about advantage of Data driven testing |
||
Line 2:
==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]]. 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.
==Methodology overview==
Line 32:
{{Reflist}}
{{refbegin}}
* Carl Nagle: ''Test Automation Frameworks''[http://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]]
| |||