Context represents a state of the test application. A UI based Context can be associated with one or more Views that capture the visual essence of the Context.
Determining when to mark something as an additional View of an existing Context vs. creating as a brand new Context is very important in ensuring right level of modularity and reusability in the test assets. Consider following guidelines, which should be evaluated in totality to arrive at right boundaries for Context vs. Views.
- A Context should offer a distinct set of user actions, not just a few additional visual elements.
- If a page has resulted from a trip to the server, it may likely indicate a new Context.
- If incremental new functionality is a result of slight alteration in a portion of a screen, it may be better considered as an alternate View of the same Context.
For example, consider following:
- Bank Login Page is a different Context from Account Summary Page
- Personal Login and Corporate Login are two separate Views of the Bank Login Page which offer Login functionality two different types of users.