Test automation framework: Difference between revisions

Revision as of 19:50, 8 January 2011

Revision as of 19:45, 10 January 2011

Line 1:

{{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. Ideall, there is no need to update the scripts in case of changes to the application.

Ideall, yhere's no need to update the scripts in case of changes to the application.

CostsChoosing the right framework/scripting technique helps in maintaining lower costs. The 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.

Choosing the 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)

Line 24 ⟶ 23:

'''Another view'''

Automation Framework is not a tool to perform some specific task, but is an infrastructure that provides thea complete solution where different tools canwork plug itself and do their jobtogether in an unified manner. Hencehence providing a common platform to the automation engineer doing theirusing jobthem.

Ref: http://code.google.com/p/vauto/