Keyword-driven testing

From Wikipedia, the free encyclopedia

You have new messages (last change).
There are very few or no other articles that link to this one.
Please help introduce links in articles on related topics. After links have been created, remove this message.
This article has been tagged since November 2006.

Please wikify (format) this article or section as suggested in the Guide to layout and the Manual of Style.

Remove this template after wikifying. This article has been tagged since September 2006.

Keyword-driven testing is a technique that separates much of the programming work from the actual test steps so that the test steps can be developed earlier and can often be maintained with only minor updates,even when the application or testing needs change significantly. The keyword-driven testing methodology divides test creation into two stages:

Planning Stage

Analyzing the application and determining which objects and operations are used by the set of business processes that need to be tested.

Determining which operations require customized keywords to provide additional functionality, to achieve business-level clarity, and/or to maximize efficiency and maintainability.

Implementation Stage

Building the object repository and ensuring that all objects have clear namesthat follow any predetermined naming conventions.

Developing and documenting business-level keywords in function libraries.Creating function libraries involves developing customized functions for the application you want to test.

Although this methodology requires more planning and a longer initialtime-investment than going directly to the test creation stage and recording your steps, this methodology makes the test creation and test maintenance stages more efficient and keeps the structure of individual tests more readable and easier to modify.

Retrieved from "http://en.wikipedia.org../../../k/e/y/Keyword-driven_testing.html"