Test automation framework: Difference between revisions

Revision as of 20:32, 11 December 2011

Revision as of 20:48, 11 December 2011

Line 30:

==Test automation interface==

Test automation interface are platforms that provides 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.{{Citation<ref name needed|date=December 2011}}"Interface">{{cite web

| url = http://www.qualitycow.com/Docs/ConquestInterface.pdf

| title = Conquest: Interface for Test Automation Design

| accessdate = 2011-12-11

}}</ref>

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

Line 41 ⟶ 45:

==Interface engine==

Interface engines are built on top of Interface Environment. Interface engine comprises of a [[parser]] and a test runner. The parser is present to parse the object files coming from the object repository in to the test specific scripting language. Test runner deals with executing the test scripts using a [[test harness]].{{Citation<ref name needed|date=December 2011}}"Interface" />

==Interface environment==

Interface environment comprises of Product/Project Library and Framework Library. Framework Library have modules related with the overall test suite while the Product/Project Library have modules specific to the application under test.{{Citation<ref name needed|date=December 2011}}"Interface" />

==Object repository==

Object repositories are a collection of UI/Application object data recorded by the testing tool while exploring the application under test.{{Citation<ref name needed|date=December 2011}}"Interface" />