In production environments, it's common to have multiple presentations of any given feature operating within a single application. For example, different pages within a single application may use different incarnations of a common navigation menu component, depending on whether each page has been updated to use the latest version or not.
To accommodate this reality, add an annotation that associates the base class with a context-matching resolver that returns the component subclass that corresponds to the component version presented by the system under test.
In production environments, it's common to have multiple presentations of any given feature operating within a single application. For example, different pages within a single application may use different incarnations of a common navigation menu component, depending on whether each page has been updated to use the latest version or not. To accommodate this reality, add an annotation that associates the base class with a context-matching resolver that returns the component subclass that corresponds to the component version presented by the system under test.