The implementation of this methodology is framework dependent. This framework
requires the development of data tables and keywords, independent of the test
automation tool used to execute them and the test script code that "drives" the
application-under-test and the data.
In a keyword-driven test, the functionality
of the application-under-test is documented in a table as well as in
step-by-step instructions for each test.
If we were to map out the actions we perform with the mouse when we test our
Windows Calculator functions by hand, we could create the following table. The
"Window" column contains the name of the application window where we're
performing the mouse action (in this case, they all happen to be in the
Calculator window). The "Control" column names the type of control the mouse is
clicking. The "Action" column lists the action taken with the mouse (or by the
tester). And the "Arguments" column names a specific control (1, 2, 3, 5, +, -,
and so on).