Evolving The Framework - Structuring Step Classes

Now that we have a fair bit of understanding around pages and the locator strategies, let us look back at the step classes.

The primary job that we have for the step classes so far is to:

• Provide the glue code for the english like scenario so that it finds something to execute.
• Delegate the actual action to the pages which encapsulate the actual method to interact with the browser.

Given the fact that we will have a fair number of test scenarios in any given applications and hence quite a lot of steps across the applications, we also need to think of a strategy to manage the various steps in an elegant fashion.