Editing Test automation (section)

==Framework approach in automation==
A test automation framework is an integrated system that sets the rules of automation of a specific product. This system integrates the function libraries, test data sources, object details and various reusable modules. These components act as small building blocks which need to be assembled to represent a business process. The framework provides the basis of test automation and simplifies the automation effort.

The main advantage of a [[Software framework|framework]] of assumptions, concepts and tools that provide support for automated software testing is the low cost for [[Software maintenance|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. Ideally, there is no need to update the scripts in case of changes to the application.

Choosing the right framework/scripting technique helps in maintaining lower costs. The costs associated with test scripting are due to development and maintenance efforts. The approach of scripting used during test automation has effect on 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)
# Agile automation framework

The Testing framework is responsible for:<ref>{{cite web
 | url = https://www.youtube.com/watch?v=qf2i-xQ3LoY
 | title = Selenium Meet-Up 4/20/2010 Elisabeth Hendrickson on Robot Framework 1of2
 | website = [[YouTube]]
 | date = 28 April 2010
 | access-date = 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

===Unit testing frameworks===
A growing trend in software development is the use of [[unit testing]] frameworks such as the [[xUnit]] frameworks (for example, [[JUnit]] and [[NUnit]]) that allow the execution of unit tests to determine whether various sections of the [[code]] are acting as expected under various circumstances. [[Test case]]s describe tests that need to be run on the program to verify that the program runs as expected.

===Test automation interface===
Test automation interfaces are platforms that provide a single [[workspace]] for incorporating multiple testing tools and frameworks for [[system testing|System/Integration testing]] of application under test. The goal of Test Automation Interface is to simplify the process of mapping tests to business criteria without coding coming in the way of the process. Test automation interface are expected to improve the efficiency and flexibility of maintaining test scripts.<ref name="Interface">{{cite web
 | url = http://www.qualitycow.com/Docs/ConquestInterface.pdf
 | title = Conquest: Interface for Test Automation Design
 | access-date = 2011-12-11
 | archive-date = 2012-04-26
 | archive-url = https://web.archive.org/web/20120426044210/http://www.qualitycow.com/Docs/ConquestInterface.pdf
 | url-status = dead
 }}</ref>

[[File:Test Automation Interface.png|thumb|Test Automation Interface Model]]

Test Automation Interface consists of the following core modules:

* Interface Engine
* Interface Environment
* Object Repository

====Interface engine====
Interface engines are built on top of Interface Environment. Interface engine consists of a [[parser]] and a test runner. The parser is present to parse the object files coming from the object repository into the test specific scripting language. The test runner executes the test scripts using a [[test harness]].<ref name="Interface" />

====Object repository====
Object repositories are a collection of UI/Application object data recorded by the testing tool while exploring the application under test.<ref name="Interface" />