What can we help you with?
< All Topics
Print

Test Development

What is Test Development?

Test Development is the workplace where the scripts are written.

How helpful is Test Development?

  • To maintain all the scripts in one place, we use Test Development.
  • It is the concept of keeping all the scripts systematically.

How does Test Development work?

  • A user should create a “Module” before creating the Scripts.
  • A Single module can contain any number of “Scripts” and it can contain any number of “Sub-Modules” as well.
  • A sub-module can further contain any number of sub-modules and scripts within it.
  • Once the script is created, inside the script you can add the NLP’s using the steps page.
  • After adding all the steps, you can execute the script by clicking on the “Run” icon.

Pre-requisites

The user should create the project.

Navigation for Test Development

FireFlink > Left Navigation Panel > Test Development>Home

Module

What is Module?

  • A module is a container that contains any number of sub-modules, and scripts in it.
  • A user should create a “Module” before creating the Scripts.
  • A user can create any number of modules in the “Test development” section.
  • It is not mandatory to have a sub-module inside a module. A user can directly create scripts inside a module.

Why do we need modules?

A user cannot create a script without a module. The creation of a module is mandatory for a user to create a script.

Creating Module

  • Click on the “+ Module” button.

  • The “Create Module” popup appears.

  • Enter the required data into all the mandatory fields.
  • Enter a name in the “Name” text field, enter a description in the “Description” text field (Optional), and choose the parent module from the ‘Parent Module’ dropdown.

  • Initially, before creating any of the Modules, only the “Root module” is present in the “Parent Module” dropdown.

  • Click on the “Create” button.

Columns under Module Table

1. Module

  • Under this column, the Module Tree structure is displayed.
  • The Module Tree includes all the Sub-Modules, Scripts, and Pre-Post conditions.

2. Test Case Type

  • Under this column, the “Test Case Type” of the script is displayed, which will differentiate between the automation test case and the manual test case.

3. Type

  • Under this column, the “Type” of the script is displayed, which is created during “Create Script”.
  • “Type” columns for “Module” and “Sub-Module” will be empty.
  • The “Type” of the script can be ‘WEB’, ‘WEB SERVICES’, or ‘DATABASE’ for the “WEB” Project type.
  • The “Type” of the script can be ‘ANDROID’, ‘WEB SERVICES’, ‘DATABASE’ for the “MOBILE” Project type, and “ANDROID” platform type.
  • The “Type” of the script can be ‘ANDROID’, ‘iOS’, ‘WEB SERVICES’, ‘DATABASE’ for the “MOBILE” Project type, and, “ANDROID & iOS” Platform type.
  • The “Type” of the script can be ‘WEB SERVICES’, or ‘DATABASE’ for the ‘WEB SERVICE’ Project type.

4. State

  • Under this column, the three states “New”, “Commit”, and “Publish” are displayed.

5. Actions

  • Under this column the three icons “Edit”, “Delete”, and “More Actions” are displayed.

Edit and Delete the Module

1. Edit Module

  • Hover the mouse on a Module, which you need to Edit.
  • Click on the ‘Edit’ icon.

  • A popup with the header ‘Edit Module -<<Module Name>>’ appears.

  • Users can make changes in the Pop-up.
    Note: Parent Module is disabled, the user can only edit the name and description.
  • Click on the “Update” button.

2. Delete a Module

Note: To delete any module, that module should not have any resources under it (Should not contain any of the Sub-Modules or Scripts in it)

  • You can hover the mouse over a module that you need to “Delete”.
  • Click on the ‘Delete’ icon.

  • A “Warning message” popup is prompted.

  • Click on the “Delete” button.

What is a Sub-Module?

  • A Module inside the Module is called a “Sub-Module”.
  • A user can create any number of sub-module inside a module.
  • A sub-module can contain any number of modules and scripts.

Why do we need a Sub-Module?

  • It is convenient to have sub-modules, though it is not mandatory.
  • Having a sub-module helps in grouping the scripts thus, a user can easily identify the scripts.

Pre-requisites for Sub-Module

It is mandatory to create a “Module” before creating a “Sub-Module”.

Creating Sub-Module

  • Click on the “+” button beside the module, for which Sub-Module has to be created.
  • Choose the ‘Add Module’ option.

  • The “Create Module” popup appears.
  • Enter the sub-module name into the ‘Name’ text field.
  • Here ‘Parent Module’ is selected by default and will be disabled. You cannot edit the ‘Parent Module’.
  • Click on the ‘Create’ button.

Edit and Delete the Sub-Module

1. Edit a Module

  • Hover the mouse on a Sub-Module that you need to Edit.
  • Click on an ‘Edit’ icon.

  • A popup with the header ‘Edit Module -<<Module Name>>’ appears.
  • Users can make changes in the Pop-up.
    Note: Parent Module is disabled, the user can only edit the name and description.
  • Click on the “Update” button.

2. Delete a Sub-Module

Note: To delete a Sub-Module, it cannot contain any resources under it (Should not contain any of the Scripts).

  • Hover the mouse on a sub-module, which you need to “Delete”.
  • Click on the ‘Delete’ icon.

  • A “Warning message” popup is prompted.

  • Click on the “Delete” button.

Icons

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

2. Collapse all: On clicking this icon, the Module Tree Collapses, and all the Sub-Modules, Pre-Post Conditions for Root level and Module level, and Scripts of the module are hidden and only Modules are displayed under the Module tree.

3. Show all scripts: Clicking on this icon, the Module expands and all the Sub-Modules, Pre-Post Conditions, and Scripts under that Module are visible.

4. Hide all scripts: Clicking on this icon, Module Collapses, and all the Sub-Modules, Pre-Post Conditions, and Scripts of the module are hidden and only Modules are displayed under the Module tree.

5. Show Pre/Post Conditions: Clicking on this icon, all the Pre-Post conditions are expanded.

6. Hide Pre/Post Conditions: On clicking this icon, all the Pre-Post conditions are collapsed.

7. Edit Module :

  • This icon is visible when you hover a mouse over a particular Module in the Module tree.
  • This icon is used when you need to change the information related to the module.
  • On Clicking on this icon, a popup header with “Edit Module-<<Module Name>>” is prompted.
  • Enter the data that is to be changed.
  • Click on the ‘Update’ button.

8. Edit Script :

  • This icon is visible when you hover a mouse over a particular Script in a Module tree.
  • This icon is used when you need to change the information related to the script.
  • On Clicking on this icon, a popup header with “Edit Module/Script-<<Script Name>>” is prompted.
  • Enter the data that has to be changed.
  • Click on the ‘Update’ button.

9. Delete :

  • This icon is visible when you hover a mouse over a particular Module/Sub-Module/Script in the Module tree.
  • This icon is used to delete Script, Sub-module, or Module.
  • When clicked on this icon a, warning popup is prompted with the ‘Delete’ button
  • Click on the ‘Delete’ button.
  • In the popup, on clicking on the ‘Cancel’ button, it will not be deleted.
  • A Module consisting of resources cannot be deleted.

10. More Actions :

  • More Actions, at the top corner, contains three options such as:
    • Optimizer
    • NLP Help
    • Download client
  • When hovering with the mouse on More Actions on Row. This contains two options such as:
    • Details: In this, it will display the details of Modules/Scripts.
    • History
    • Clone

11. Run:

  • This icon is used to execute.
  • 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.

12. Quick Run Settings: On clicking this icon, the “Quick run settings” popup appears. The details view of Quick Run Settings is explained below.

13. Search: This icon is used to search a particular module, Sub-module, and script.

14. Automation button: Clicking on this icon, will navigate to the automation steps.

15. Manual button: Clicking on this icon, will navigate to the manual test case.

Quick Run Settings

  • On clicking on this icon, a popup with the header ‘Quick Run Settings’ is prompted.
  • In this popup, by default, the ‘Make these settings as default’ radio button is checked.
  • This popup mainly consists of three sections:

1. System:

The column under the System table:

  • Download Client:
    1. If the user clicks on the “Download client” button, the “Download Client” popup will be displayed.
    2. The user can choose the OS like “Windows”, “Mac” or “Linux” and click on the “Download” button.
  • Client Machine:
    1. This column displays the set of Machines.
    2. By default, ‘Machine1’ is selected.
  • Execution Environment:
    1. Under the Execution environment, seven options are available- ‘Local’, ‘Browser Stack’, ‘Sauce labs’, ’lambda test’, ’GoogleCloud’, ’AWS’, and azure.
    2. By default, ‘Local’ is selected.
  • OS:
    This column displays the OS (Operating System) of a particular machine.
  • Browser:
    1. Under this column, the browser can be selected for a particular Machine.
    2. The user can select ‘Chrome’, ‘Internet Explorer, and ‘Microsoft Edge browsers for a particular machine.
  • Access:
    1. Under this column, Access specifiers are displayed for a specific Machine.
    2. Under the “Environment configuration”, in “System configuration” the one in which the user opts for the access specifier will be reflecting the same in the quick run settings popup.
    3. The Access may be ‘Private’, ‘Public’, or ‘Partial Public’.
  • Status:
    1. The status of the machine is displayed under this column.
    2. Under the “Environment configuration”, in “Environment configuration”, the access specifier will be reflecting the same in the quick run settings popup.
    3. The status may be ‘Available’, ‘Busy’, ‘Disabled’, or ‘Inactive’.

2. Steps:

  1. In this section, the user can specify the delay between steps.
  2. By default, the ‘Delay Between Steps’ is “0”.
  3. Using the up and down arrow, you can change the value for delay.
  4. You can also specify the unit, by selecting it from the dropdown.
  5. ‘Millisecond’ is selected by default.
  6. The two available options are ‘Millisecond’ and ‘Seconds’.

3. Result:

This section consists of three options:-

  • Capture a screenshot of the result:
    This has three options, such as,
    1. For failed steps only: When selecting this option, a screenshot for only failed steps is captured. By default, this option is selected.
    2. For all steps: If this option is selected, screenshots for all steps are captured.
    3. Don’t capture: If this option is selected, the screenshot is not captured.
  • Capture video in result:
    We have three options here, such as,
    1. Don’t capture: If the user selects this option, the video is not captured. By default, this option is selected.
    2. For failed scripts only: If the user selects this option, videos for only failed scripts are captured.
    3. For all scripts: If the user selects this option, videos for all the scripts are captured.
  • Display logs in results:
    Error logs:
    1. By default, this option is selected.
    2. This is non-editable.
    3. As a result, it displays the reasons for errors or exceptions after the execution of scripts.

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