Target System in Breez

Overview

This document is part of the User Manual for Breez – No Script Unified Automation Solution. This document is part of the series of User Guides created for Configuration and Automation of Test Execution using Breez.


Configuration Hierarchy

Following picture depicts the Configuration Hierarchy in Breez Solution.

breez-hierarchy
*Screen can be reused across processes in the same system
**Processes can be reused across the same system by creating parent processes

Hierarchy has been explained in UG-Breez-Hierarchy-General-Help.pdf

To know Object Creation and XPath Mapping, please watch the video https://www.youtube.com/watch?v=Vq2ASP_FohE

Pre-requisites

Following are the pre-requisites for creation of a Target System:

  • Organization should already have been created and Active
  • User is logged in to Breez System
  • User should have rights to create System

Definition and Description

In Breez, “Target System” is the Application that the user wants to Test using Breez automation solution. Target System is the highest point in hierarchy in an Organization. Multiple Target Systems can be created under one organization. It is used to group all the processes under an application, so that Screens or Processes can be created once and used multiple times. For setting up the Automation hierarchy, first step is to create a Target System. System Code and Name are unique to the Organization. If User wants to create for the same Application across various stages like SIT, UAT etc., they can be created as Application1-SIT, Application1-UAT to differentiate the Application being tested in different stages.

Target System Configuration Process

Following is the Process for configuring a new “Target System” in Breez:

  1. User once logged in, will be taken to the landing page of the application
  2. From the Menu displayed on the Left Hand Side, Select ORG Artefatcs -> Target System
  3. On Selecting the Target System, List of Target Systems already created for the Organization is displayed. Check whether the required system is already existing in the list. If it is already existing, user can click on the respective button on the right side under “Actions” column to View / Edit / Delete the existing Target System
  4. If the Target System does not exist, Click on “Create Target System” Button on the Top Right Corner of the Screen. Breez will display a Screen for creation of Target System
  5. System Code and System Name are mandatory fields and are unique within the organization. System Name defaults from the System Code Entered, but can be modified
  6. System Type is a drop-down field to be selected mandatorily. It shows the type of Target System. Currently Web, API, Mobile and AS/400 options are available in the drop-down. This is an important field as some of Breez Flows depend on System Type. Default Value is “Web”
  7. URL is the Link / IP Address OR location of the Target application
  8. User can select the Browser he would like to invoke for executing the automation.Please note that in headless mode, user will not be able to see the actual execution,but the screenshots are displayed as per the execution progress
  9. Browser Language: The Language in which the UI contents are displayed and input from the data file. Default Language is “English”
  10. User can set values for Implicit / Explicit Wait times ( Time Breez will wait for the objects to appear and become actionable) & Sleep Time for the system. Default Values automatically set are 10 seconds,but user can modify them as per the responsiveness of the System. These can be modified later also post gaining experience post automation
  11. Credential Required Checkbox : For applications which requires Credentials (Username/password) for logging in to main screen, user needs to select this check box. For example if user is creating configuration for Breez, user needs to check this as Username and password are required for logging into Breez. For Applications that can accessed without login credentials, this box should be unchecked
  12. If user Checks the “Credentials Required Checkbox”, another Check Box appears “Xpath Required for Login Page”
  13. This “Xpath Required for Login Page” is to be checked if User wants to extract the Xpath and other locators for the login page. On Selection of this checkbox, Breez will automatically navigate and extract the elements / Objects, Steps, Xpath and Other locators of the login page ( like Username, Password, Submit button etc.,)
  14. [NOTE: IF “CREDENTIALS REQUIRED” CHECKBOX IS NOT CHECKED, BREEZ TAKES A DIFFERENT FLOW.PLEASE REFER “CREDENTIALS NOT REQUIRED” SECTION BELOW]
  15. Click on Create Button after all the above information is provided
  16. Breez will create Target system and also a Project and Batch automatically and takes the user to “Element Extraction Screen” for extraction of Objects and Steps for the Login Credentials Page
  17. User can extract all the elements on the credentials page ( URL given for the system) OR can use filter to extract only required Elements. For more details on Element Extraction, please refer UG-Breez-Element Extraction V1.0.pdf.Extracted Objects appears as below
  18. Once the Credentials Screen is created, go to ORG Artefacts Credentials Menu option to create the login credentials for that system. These credentials will be stored by Breez and will be used as part of automation without the need for user to provide the credentials every time, at the time of automation. Click on “Create Credentials” Button on Top Right Corner
  19. Breez Will display the following Screen. Enter System Code. Click on “Object of Username” and “Object of Password”, system will display a popup screen
  20. Select the relevant objects from the popup screen
  21. Enter Data Values ( Actual credentials that will be used to login to the Target
    System) in “Username” and “Password” fields
  22. On clicking “Create” button, credentials for the Target System get created
  23. This completes the Target System Creation wherein Project, Batch are created by default and if “Credentials Required Checkbox” is checked, Login screen, required elements and credentials are also created in the flow

Credentials Not Required

If the Target System does not require any login credentials ( like customer onboarding flows etc.,), login screen and credentials are not required. Hence there is a slight deviation in the process. Refer Steps 1 to 12 of “Target System Configuration Process” above.

  1. “Credentials Required Checkbox” is NOT checked in the “Create Target System” screen and Create button clicked
  2. System will display popup window - “Project and Batch Created with default values”
  3. Breez will display “Create Screen Configuration” List screen. This Screen will be the default landing page for the application under test and is automatically created by Breez using the URL given for the Target System
  4. Breez will also create Two Elements and their steps – Open Browser and Navigate to the page ( as per the URL / IP Address given)
  5. This completes the Target System Creation wherein Project, Batch are created by default and if “Credentials Required Checkbox” is NOT checked, Landing Page, Two basic elements are also created in the flow
  6. Other Objects as required can be created using “Create Test Steps” Process OR using Element Extraction process