So what is a keyword? A good example is Login. It is obvious from the name what this Test Case does. It contains three of the Jubula unbound modules from the library Project :
In this keyword, the two TEXT parameters from the replace text modules would be referenced as "=USERNAME" and "PASSWORD" 3.12.3.
Any time you need to perform a login in your test, you can reuse this keyword and enter the specific use data each time. This has the advantage that your tests will be easy to read, and that any maintenance you need to do to this keyword can be done in one place.
Other things that lend themselves well to being made into keywords are:
Many of these keywords will use the same modules from the unbound modules Project . However, the advantage of making a keyword is that all or most of the data that you need, and the component names, can be encapsulated into a module which has a recognizable name.
Some actions cannot be entirely encapsulated into a keyword with no parameters. Actions to enter text or select items from trees often require a different text or textpath each time they are reused. In this case, it is probably not worth writing a separate keyword for each possible data set.
![]() |
If you realise later on in your test that you will need a module again, use the refactor function 3.9.7 to extract a reusable Test Case . |