Skip to content

Keyword Driven Testing

Keyword Driven Testing

What is Keyword Driven Testing?

Keyword Driven Testing uses reusable building blocks, known as keywords, to create test cases. These keywords form an easy-to-learn language that connects technical experts, testers and automation engineers. Each building block stands for a clearly defined test step, which makes the test cases easier to understand and facilitates collaboration within the team. This creates a common vocabulary for specific domains and application areas.

Special challenges in the specification of tests

Test managers face several challenges when defining and specifying tests:

Abstraction level of the test cases

The trick is to design test cases in such a way that they are understandable for non-technical stakeholders on the one hand and technically precise enough for implementation on the other. This balance is difficult to achieve.

Reusability of test steps

In the traditional test case specification, similar or identical test steps lead to redundant entries. This not only makes maintenance more difficult, but also increases the susceptibility to errors.

Independence from the implementation

Test cases that are closely linked to the implementation details of an application often require extensive adjustments when software changes are made.

Specifications for test automation

In order for test cases to serve as a basis for automation, they must be defined very precisely. At the same time, they must not lose their readability for humans.

Let’s find a solution together!

Advantages of Keyword Driven Testing

Keyword-driven testing offers numerous advantages that improve both the efficiency and the quality of the tests:

  • Reusability and maintainability: as each keyword is managed centrally, changes to a keyword immediately affect all associated test cases. Redundant adjustments are no longer necessary, which makes maintenance considerably easier.
  • Simplified test automation: Automation is limited to the implementation of individual keywords instead of automating complete test cases. This significantly reduces the implementation effort.
  • Speed and efficiency: Test cases can be quickly compiled from existing keywords. New keywords are only required for additional functionalities.
  • Collaborative: Keywords create a common foundation that enables subject matter experts and automation specialists to work together efficiently.

When is Keyword Driven Testing recommended?

Keyword Driven Testing is particularly suitable for system or acceptance tests where both technical precision and abstract documentation are required.

Areas of application:

Test cases that need to be repeated or adapted frequently.

Projects in which close co-operation between specialist departments and technology is required.

Automation projects with high demands on efficiency and maintainability.


The easy readability of test specifications and the ability to quickly achieve a high level of automation coverage make Keyword Driven Testing a versatile method.

How does Keyword Driven Testing work with TestBench?

TestBench is a tool that supports the practical application of Keyword Driven Testing. Keywords are defined as test steps and managed centrally.

Central functions of TestBench:

  • Test element view: Keywords are created and organised here. They can be integrated into test sequences and used multiple times.
  • Parameters and data: Each keyword can contain parameters that can be flexibly customised. This creates dynamic and reusable tests.
  • Versioning: Changes to keywords are tracked centrally to avoid errors caused by unintentional adjustments.

This structured approach not only supports compliance with standards such as ISO 29119-5, but also enables Keyword Driven Testing to be combined with Data Driven Testing.

Test procedure from keywords
Simple sequence without parameters

The illustration shows a simple test sequence without parameters. As an example, test sequences of a test are composed of individual keywords as follows.

Test sequence list for a car configurator showing six steps: start Car Configurator, choose vehicle, choose special model, choose add-on, check price, and close Car Configurator. Each step is marked with a gear icon representing automated test actions.
Keyword with description
Precisely document what happens

“Screenshot of the ‘choose special model’ test step in TestBench. The status is marked as ‘released’, with default type set to ‘Flow’. The description instructs the user to select a special model from a dropdown list, which includes options such as Gomera, Jazz, and Luxus.

Where-used list
All keyword views at a glance

If a keyword is called up in a test sequence, a list of all calls is automatically generated – the so-called where-used list. The illustration shows a where-used list that only includes test case records.

TestBench usage list panel showing three linked test cases: '2.1.3 Configure base vehicle', '2.2.1 Configure base vehicle with currency', and '5.1 Configure base vehicle without discount'. The view includes an update option and a last updated timestamp.
Parameters in the keyword
Flexible data control

When specifying tests, it makes sense to separate the process from the data used in it. This makes it possible to use necessary values as variables. Therefore, each keyword in TestBench can contain any number of parameters. The illustration shows a test sequence with parameters.

TestBench test sequence with six automated steps for a car configurator, each linked to parameters: choose vehicle (vehicle), choose special model (special model), choose add-on (add-on list), and check price (total price). Each step is represented with an automation icon, with 'check price' marked as completed.
Individual parameter lists
Customized per test sequence

This makes it possible to define an individual parameter list for each test sequence. The illustration shows an example of such a list.

Parameter mapping table from TestBench showing four data types and their associated parameter names: vehicle name (vehicle), special model name (special model), add-on name (add-on list), and price (total price). Icons indicate different parameter input types or list structures.
Test case table
Values per run clearly defined

This creates a test that consists of a test sequence and the associated parameter list. The values for the parameters are stored in a table, with each row representing a data set for a specific run of the test sequence. The illustration shows a test case table for the parameter list.

TestBench data table showing combinations of vehicles, special models, add-ons, and total prices. Entries include vehicles like Rolo, Rassant, Rassant Family, and I5 with associated special models such as Jazz, Gomera, and Luxus, and detailed add-on lists. Prices range from 12,300.0 to 29,000.0.
One test, many cases
Scalable through data rows

In TestBench, a test consists of a test sequence, the corresponding parameter list and a data table with the values to be used. This creates not just a single test case, but a whole set of test cases. Each test case combines the test sequence, the parameter list and a specific data row from the data table. An additional test case can easily be created by adding another row to the data table. The illustration shows a test sequence with parameter list and a data set from the test case table.

TestBench interface displaying three sections: a test sequence with six steps for configuring a car, a parameter list linking data types to parameter names, and a test case showing values for vehicle 'Rassant', special model 'Jazz', add-ons including radio and mats, and a total price of 19529.0.

How is the test data managed?

In TestBench, test data is organised using data types. These bundle values of the same specialised type, e.g. vehicle names or special models, and serve as parameters for keywords. When a keyword is called, the parameter is transferred with a suitable value of the associated data type. Similar to test cases, keywords can use multiple parameters, which facilitates the management and flexibility of complex tests.

TestBench also seamlessly integrates Data Driven Testing with Keyword Driven Testing, as recommended by ISO 29119-5.

TestBench test sequence table showing six automated steps for a car configurator. Each step includes associated parameters: vehicle, special model, add-on list, total price, and currency. Step 5, 'check price with currency', uses both 'total price' and 'currency' as input parameters.

How can tests become even easier to understand?

TestBench test sequence showing a composed test case titled 'calculate price without discount' consisting of four main steps: start Car Configurator, configure vehicle with parameters (vehicle, special model, add-on list), check price with parameter 'total price', and close Car Configurator. The composed test case expands to display nested actions and parameter usage in detail.

Long keyword sequences can make it difficult to capture the test idea. TestBench offers a solution for this: keywords can contain their own test sequences. This allows several steps to be summarised in a new keyword, which shortens the test sequence and makes the test content clearer.

This abstraction makes it easier to understand complex tests without losing details. Additional abstraction levels mean that even long end-to-end tests can be designed in a comprehensible way while retaining the necessary level of detail for test execution.

Why Keyword Driven Testing for automation?

Efficiency: Only individual keywords are automated, which keeps the effort constant.

Flexibility: Changes to technical specifications are easy to implement.

Reduction of technical complexity: Specialist details can be presented at a higher level of abstraction, while technical details remain in subordinate keywords.

A detailed explanation can be found on the Test Automation page.

Why Keyword Driven Testing for manual testing?

Keyword Driven Testing also shows its strength in manual tests:

Simpler test specification

Test sequences can be quickly recognised and clearly displayed thanks to keywording.

Consistency and quality

Tests are carried out consistently regardless of the experience of the person performing the test.

Speed

Test execution can be up to 40 % faster, as the focus is on the actual test execution rather than on understanding the specification.


This approach not only improves efficiency, but also the reproducibility and reliability of the test results.

Further information on test execution can be found on the Test Execution page and in the blog post ‘Less effort, more efficiency: the iTORX assistant’

Your questions – our answers

Do you have questions about Keyword Driven Testing or are you looking for support in optimizing your testing processes? Our experts will be happy to help you. Contact us and we will help you to design your test strategies efficiently and successfully

How can we help?