This example uses Windowlicker to test a simple calculator application.

The end to end tests use a Calculator Driver to control the user interface. The Calculator Driver provides task-based abstractions (performing arithmetic) to the tests and implements them in terms of low-level activities (pressing buttons, typing keys).

The calculator application defines a few constants for window names to support refactoring. We don't want the tests to break when the application is refactored. However, the tests exercise the application functionality entirely through the user interface.