Test automation: Difference between revisions

Revision as of 13:48, 8 August 2025

Revision as of 13:53, 8 August 2025

Line 78:

* Unit testing {{endash}} some frameworks are intended primarily for [[unit testing]] such as [[xUnit]], [[JUnit]] and [[NUnit]]

===Test automation interface===

TestA test automation interfacesinterface areis a platformsplatform that provideprovides a single [[workspace]] for incorporating multiple testing tools and frameworks for [[system testing |Systemsystem/Integrationintegration testing]]. of application underA test. Theautomation goalinterface of Test Automation Interface is tomay simplify the process of mapping tests to business criteria without coding. comingA in the way of the process. Testtest automation interface are expected tomay improve the efficiency and flexibility of maintaining test scriptstests.<ref name="Interface">{{cite web

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

| title = Conquest: Interface for Test Automation Design

Line 90:

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

TestA Automationtest Interfaceautomation interface consists of the following core modulesaspects:

Interface engines are built on top of Interface Environment.; Interface engine: consistsConsists 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" />

* Interface Engine

* Interface Environment

* Object Repository

; Object repositoriesrepository: are a collectionCollection of UI/Application object data recorded by the testing tool while exploring the application under testSUT.<ref name="Interface" />

====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" />

==Defining boundaries between automation framework and a testing tool==