Thursday, November 13, 2008

Automation Framework

Just imagine a car. We can make it move, turn, play music, reduce/ increase the temperature, slow down, stop, etc. How are all these things happening? It has many things in it which are "coordinating" with each other to make these happen. A car has a body, seats, steering wheel, engine, gear box and what not! All these things have been somehow "glued" together, enabling them to talk to each other; to form a single working system - a car.
A framework may be regarded as a "skeleton" upon which various parts are placed into to form a "system". In software sense, a framework may include support programs, code libraries, a scripting language, or other software to help develop and glue together the different components of a software project. Various parts of the framework may be exposed through APIs enabling communication among them.
Thinking on the same lines, Automation Framwork consists of an automation tool, test management tool, a driver script and may also have as additions library functions, supporting applications and a reporting mechanism.
A framework is formed by mainly studying the application under test - commonly referred to as AUT. Based on various factors the different aforementioned tools are selected and are interface tested before actual beginning of automating the testing proces.

No comments: