3.31.2. Tips and tricks for using the observation mode
Prev | 3.31. Observing Test Cases | Next

### 3.31.2. Tips and tricks for using the observation mode

We have designed the observation mode to help you get started with your tests and to help you understand what sort of user actions correspond to actions in the library.

The ITE is first and foremost a keyword-driven tool, and the library of Test Cases installed means that you have various benefits over simple recording:

- You can create tests without needing the AUT - you don’t have to wait for each version of the AUT to begin test specification.

- Your tests aren’t so dependent on the actual implementation of the AUT, so they can be a lot more general in terms of data, component implementations etc. and therefore a lot more robust and maintainable.

- Using keywords encourages you to think about your test structure a lot more, which also helps maintenance later.

Nevertheless, we understand that you may want to observe some Test Cases. Here are some tips that might help you:

- Think about your test structure at the beginning: what modules will you want to reuse? Start by observing small Test Cases, e.g. a Test Case to login, a Test Case to open a dialog etc.

- Check while you are observing that the actions you carry out are observed in the way you meant.

- Supplement your observed Test Cases with other Test Cases from the library of Test Cases installed.

- Refactor as you go! If you have recorded a Test Case with specific data, but you will want to use it for any type of data, then add a reference for the data.