|
#REDIRECT[[Test_automation#Framework_approach_in_automation]]
{{Merge|Test harness|date=February 2010}}
{{Cleanup|date=December 2007}}
A '''test automation framework''' is a set of assumptions, concepts and tools that provide support for [[test automation|automated software testing]]. The main advantage of such a framework is the low cost for maintenance. If there is change to any test case then only the test case file needs to be updated and the [[Driver Script]] and [[Startup script]] will remain the same.
There's no need to update the scripts in case of changes to the application.
Choosing right framework/scripting technique helps in maintaining the costs and maintaining
Costs associated with test scripting are due to the development effort and the maintenance efforts. The approach of scripting used during test automation has effect on the costs
Various framework/scripting techniques are generally used:
# Linear (procedural code, possibly generated by tools like those that use record and playback)
# Structured (uses control structures - typically ‘if-else’, ‘switch’, ‘for’, ‘while’ conditions/ statements)
# [[Data-driven_testing|Data-driven]] (data is persisted outside of tests in a database, spreadsheet, or other mechanism)
# [[Keyword-driven_testing|Keyword-driven]]
# Hybrid (two or more of the patterns above are used)
The Testing framework is responsible for:<ref>{{cite web
| url = http://www.youtube.com/watch?v=qf2i-xQ3LoY
| title = Selenium Meet-Up 4/20/2010 Elisabeth Hendrickson on Robot Framework 1of2
| accessdate = 2010-09-26
}}</ref>
# defining the format in which to express expectations
# creating a mechanism to hook into or drive the application under test
# executing the tests
# reporting results
{{Portal|Software Testing}}
==References==
{{Reflist|2}}
[[Category:Automation]]
[[Category:Software_testing]]
[[http://code.google.com/p/vauto/ Detailed analysis of Automation framewok]]
| 