Organize Automation Artifacts using Quick Extract

abstract For maintainable automation, we need to organize UI Element identifiers, the data values being passed etc. meaningfully.
Quick Extract extracts UI Elements and data values and stores them with the relevant Entity Attribute.
goal Store the UI Element in a single place so that UI Element can be reused across steps.
Extract the data into a data variable so that data can be passed externally to a step.
  1. In the User Registration flowchart, click on Enter $user details and click on Automate.
  2. Click on Quick Extract button at the bottom of the Automate dialog.
  3. Quick Extract All dialog will open. You will see a list of all UI Elements and data that we have used in the recorded steps.
    info We will now associate each UI Element and data with a meaningful Entity Attribute.
    For example, the first row contains _textbox("firstname") and Mahi.
    These represent the UI Element and Data for a user's firstname.
    So we will associate this with $user.firstname.
    $user is an Entity and firstname is an Attribute of that Entity
    Fill in the details as follows and click on Extract button.
  4. Click on Save Keywordbutton.
  5. Observe the changes in Automate dialog after Quick Extract. Clicking on $user link will open the Entities tab. Under the $user entity, we can now see the various attributes we just extracted, along with their UI Elements.
    • The UI Element tab is equivalent to an Accessor Repository or Object Repository in other frameworks.
    • UI Elements can be stored against relevant entity attributes and used as a reference from any automation step.
    • UI Error Elements are placeholders/container elements where error messages appear for a particular UI Element.
      For example, an error message may appear in an error div just under the firstname textbox. This error element can also be stored alongside the UI Element
    • A firstname can have multiple UI Elements too. One can be in a registration form. Another can be in the user profile page. Another can be as a non-editable view in a welcome screen etc. They can all be kept together in multiple rows in the UI Elements tab for $user.firstname.
    • UI Elements which are not related to any specific entity attribute can be kept in screens. Screens are represented as @screen_name. Eg. @registration, @login
      A Screen represents a page or a screen in the UI.
      The _submit("Continue") UI Element could have been stored with @registration screen.
    The $user entity and its attributes are also available on the Add Step dialog's Entity/Screen tab.
    info Quick Actions can be performed on these attributes by clicking on the + icon.
    The UI Elements and values can also be dragged and dropped to set the Add Step Parameters.
outcome We have extracted UI Elements and data, and stored it along side the relevant Entity Attribute.
Any change to a UI Element can be done in just one place.
We are now ready to use the data-driving capabilities of Flowcharts.
  • Entity
  • Attribute
  • UI Element
  • Quick Extract