Context represents a state of the Application-Under-Test and presents a cohesive set of user actions available in the test application. Various types of Contexts are supported.
For the sake of simplicity, in a web based application, you can consider each page of the test application to be a UI Context. UI Contexts are usually named after the page name with a “page” or “screen” suffix.
- Bank Login Page
- Account Summary Page
- Transfer Initiation Page
In order to ensure long term modularity and reusability of test assets, it is very important to identify Context boundaries appropriately. Keep the following guidelines in mind.
- A Context should offer a distinct set of user actions, not just a few visual differences
- If a page resulted from a trip to the server, it may likely indicate a new Context (but not always).
- If incremental new functionality is a result of slight alteration in a portion of a screen, it may better be considered as an alternate View of the same Context.