Keyword-driven testing

Keyword-driven testing separates test logic from implementation by defining action keywords that map to underlying code. Each keyword, such as "Login" or "CheckBalance", corresponds to a reusable function in a test library. Test cases are written as tables of keywords and their parameters, often in spreadsheets or simple text files. This abstraction allows testers to focus on business workflows without needing programming skills.¹ The approach is closely related to table-driven testing and shares conceptual roots with domain-specific languages.

Keyword-driven frameworks require a test library that interprets keywords and executes corresponding functions. Popular tools include Robot Framework, which natively supports keyword-driven syntax, and Selenium, often used with custom keyword layers. Implementations typically involve a driver script that reads keyword tables, dispatches calls to libraries, and reports results. The design encourages modularity: keywords for common actions (e.g., "Click", "EnterText") can be shared across test suites, reducing redundancy.²

The approach reduces maintenance costs by decoupling test scripts from application changes.¹ When a UI element changes, only the underlying keyword implementation needs updating, not each test case. This makes keyword-driven testing attractive for teams with limited programming resources. However, challenges include defining the right granularity: too coarse keywords lose flexibility, while too fine-grained ones increase complexity. Additionally, the initial framework setup requires significant investment, and poorly documented keyword libraries can become unmanageable.³

Despite its age, keyword-driven testing shares conceptual roots with domain-specific languages and has influenced modern behavior-driven development (BDD).¹ Its origins trace back to the early 2000s, notably through practitioners like Hans Buwalda, who advocated for "action-word testing." Interestingly, the technique is sometimes called table-driven testing because of its spreadsheet-like format. In agile environments, keyword-driven testing is less common than BDD, but it remains a staple in regulated industries where traceability and non-technical involvement are paramount. Few realize that the method can be applied to non-UI testing, such as API or database validation, by defining appropriate keywords.

Keyword

A named action (e.g., "Login") that triggers a reusable test function, hiding implementation details.

Test library

A collection of functions that implement the actual behavior behind each keyword, often written in a programming language.

Action word

Synonym for keyword, emphasizing the imperative nature of the command.