What can we help you with?
< All Topics
Print

Steps

Posted
Updated
ByAdmin

What are Steps?

Steps are the individual lines of NLP (Natural Language Processing) instructions formed either by typing an Action or a Verification in the NLP search box.

What is the use of a Step?

  • Steps are added to execute and generate the result of the script.
  • The added steps can be NLPs or Program Elements.

Navigation for Steps screen

Home icon > Test Development > <<Module name>> > <<Script name>> > Steps

Pre-requisites

Before creating a step, a “Module” and a “Script” has to be created.

Columns present under Steps Table:

1. Description:

  1. This column displays the added steps. How to “Add a step” is explained below.
  2. The added steps depend upon the Script, Pre-Conditions, Steps, and Post-Conditions.

2. Result:

  1. This column displays the result of executed steps.
  2. The “Passed” message is displayed in green, the “Failed” message is displayed in red, the “Warning” message is displayed in yellow and the “Skipped” message is displayed in grey.

3. State:

  1. This column displays the status of executed steps.
  2. The “Passed” message is displayed in green, the “Failed” message is displayed in red, the “Warning” message is displayed in yellow and the “Skipped” message is displayed in grey.

4. Actions:

  1. This column displays the various icons for that particular step when hovered with a mouse.
  2. Below is a detailed explanation of these icons.

Adding a Step

  • Click on the “+Step” button.

  • The “NLP dropdown” is displayed. It is a Searchable dropdown where you can select the NLP, Step Group, or Program Element from the dropdown list to add it as a step. When you select any step from the dropdown, which is explained below.

“NLP Input parameter” div:

  • When you select a particular NLP, Step Group, or Program Element from the dropdown list, an “NLP Input parameter div” is displayed in the right section of the screen.
  • Below the div header, “NLP Description” is displayed for the selected NLP. Ex: List box: verify if an option with text *string* is deselected in *element*.
  • If the NLP accepts “Elements” then “Element”, “Case Sensitive”, “Timeout-In Seconds”, and “expected value” fields are displayed below the “NLP description”.
  • If the user clicks on the “Element” field, the elements which are created in the “Repository” section, will be displayed in the dropdown, which can be selected from the dropdown. On hovering the mouse on the element field, “View element details” and “Edit element” hyperlinks will be displayed.
    • “View element details” hyperlink: On clicking on this link, the “Element Details- <<Element name>>” popup with all the details of the element will be displayed (same as in the “Repository” section).
    • “Edit element” hyperlink: On clicking on this link, the “Edit element- <<Element name>>” popup will be displayed, where the user can edit the element (same as in the “Repository” section).
  • In the “Case Sensitive”, “Timeout in Seconds”, and “expected value” fields, the data can be hard-coded or by clicking on the “+” icon which is displayed beside the text field (“Create as variable”), the “Create variable” popup will be displayed. On entering “Name” (mandatory), “Value” (non-mandatory) fields and “Type” (Local, Global, or Project environment) should be selected. On clicking the “Create” button, the “Variable” can be created, and to call that variable from the dropdown list, it is preferred to use the “$” symbol in the field. If the user has not hard-coded the variables, on the mouse hovering over the field, “View variable details” and “Edit variable” hyperlinks will not be displayed.
    • “View variable details” hyperlink: On clicking on this link, the “Variable details – <<Variable name>>” popup with all the variable details will be displayed (same as in the “Variables” tab in test development).
    • “Edit variable” hyperlink: On clicking on this link, the “Edit variable- <<Variable name>>” popup will be displayed where the user can edit the “Name” and “Value” fields, the “Type” field will be disabled, and upon clicking “Update” button, the variable will be updated (same as in “Variables” tab in test development).
      Ex: List box: verify if an option with text *string* is deselected in *element*.
  • If the step returns some value, the “Assign Step Return Value to” field is displayed in the “NLP input parameter” div. In this field, the value cannot be hard coded. The user has to click on the icon to” Create as variable”, and the “Create variable” popup will be displayed. On entering “Name” (mandatory), “Value” (non-mandatory) fields and “Type” (Local or Global) should be selected. On clicking the “Create” button, the variable will be created for the return value field.
    Ex: Get all broken links.
  • If the element is “Dynamic”, “Locator type” and “Locator value” tables are displayed in the “NLP input parameter” div.

    The user can pass the “dynamic values” for the “XPath”, “id”, or for any locators in the “Locator Value” fields for that particular step.

“NLP Description” div:

  • NLP Description will give the information for a particular NLP, i.e Name, Description, Input, and Output.
  • Hover the mouse on NLP.
  • To the right, NLP Description will be displayed.

In the “If Failed” dropdown, there are five options available. This is a mandatory field. They are:

  • Mark this step as Failed and continue script execution.
  • Mark this step as a Warning and continue script execution.
  • Mark this step as Failed and stop script execution.
  • Mark this step as Failed and stop the current module execution.
  • Mark this step as Failed and stop complete execution.

    NOTE: By default, “Mark this step as Failed and continue script execution” will be selected.

  • Add: Upon clicking on the “Add” button, the data entered will be added to the step as shown in the example above.
  • Cancel: Upon clicking on the “Cancel” button, it will cancel the operation and close the div.

Edit a Step

  • Click on the “Edit” icon present under the “Actions” column.
  • You can choose another NLP from the “NLP dropdown”.
  • “NLP input parameter” div for the particular NLP will be displayed. All the mandatory data should be entered in the respective fields.
  • Click on the “Update” button.

Delete a Step

  • Click on the “Delete” icon present under the “Actions” column.
  • This will delete the Step from the table.

Icons:

1. Search: On clicking this icon, you can search for the steps added to the table.

2. Run: 

  • Once clicked, the steps are executed and the result is displayed in the “Result column”.
  • If the user has not set the default machine and clicks on the run icon, it will pop up a message, i.e default machine is not selected.

3. Clear Result: Clicking this icon, the executed steps result is cleared.

4. Edit step: On clicking this icon, you can edit the step in the “NLP” field.

5. Add step: Clicking this icon, you can add a new step to the table.

6. Clear NLP: On clicking this icon, you can clear the NLP added in the “NLP field”.

7. Delete step: On clicking this icon, the step that is added is deleted from the table.

8. Drag and drop: On clicking this icon, the steps that are added can be dragged and dropped.

9. Run Until: On clicking this icon, the step will be executed until the specified step, and the result is displayed in the table only up to that step.

10. Quick run settings: Clicking this icon, the “Quick run settings” pop-up is displayed. The details are explained in the Modules section.

Possible scenarios for the “Quick Run Settings” icon based on user selection:

Scenario 1: When you click on the “Quick Run Settings” icon without selecting even a single script/module/precondition/postcondition. Inside the “Quick Run Settings” popup, the content will be displayed as explained above.

Scenario 2: When the user clicks on the “Quick Run Settings” icon, by selecting at least one script/module/pre-condition/post-condition. Inside the “Quick Run Settings” popup, the content displays as explained above and details of the changes to be considered are as follows:

  1. Here everything will be the same as in scenario 1 except, for the “Make these settings as default” checkbox. In this scenario, the checkbox is “Unchecked” by default.
  2. Below the text “Quick Run Settings”, an “Information” banner is provided with the text: “This setting is specific to this execution-only”. This banner is not a timer banner; this is a static banner.
  3. A button will be present on the right-hand side of the “Information” banner row, with the placeholder “Dismiss”, to dismiss the banner.
Table of Contents