- A Workflow pattern enables to turn customer journies of the application into reusable workflows
- Page Object Model provides an abstraction for a page (a webpage or mobile screen).The Workflow pattern could then be leveraged on top of POM to build workflows that represent a user journey
- UseCase: Acts as a data structure to store test data for the current test and the current state of the application. In this we have taken the product details and user details has test data and we have loaded it to Usecase using Usecase generator.
- Workflow Definition: Define a portion of customer journey, We have written definition for each page starting from selecting a product till payment
- Get the page/screen object for the current work definition by means of create() method
- Define the criteria to go to the next workflow definition by means of fulfillCondition() - fulfillment criteria is to move to the next page/screen in the workflow / customer journey
- Proceed to the next workflow definition by means of next() method - next page/screen in the workflow / customer journey
- Workflow Doc: A workflow doc is the blueprint of your customer journey. It ties workflow definitions to construct end-to-end customer journies. We have written a SingleProductDoc, where it has blue print of purchasing a single product