Part 2: Create a Test script with Studio

A. Create a test script with Mobile

I. Create a Precondition

• Precondition can be created and used for multiple scripts with the same precondition. Please follow these steps:

Step 1: Click on the [Manage Test Precondition] button.

Step 2: Click on the [Add Precondition] button.

Step 3: Select a device to start creating a precondition. When “Available” is checked, it only shows device available.

Step 4: Select a precondition parent (if applicable).

Step 5: Click on the [Record script] button to switch to the recording mode to create steps for the precondition.

➩ After selecting the pre-condition => the [Preview script] button will be displayed. You can select the [Preview script] button to run the pre-condition. (Follow step 10, 11)

Step 6: Select an element from the streaming screen of the device to perform actions.

Step 7: Choose the appropriate actions to take => The steps taken are recorded below.

Step 8: Click on the [Stop] button => the [Preview script] button will be enabled.

Step 9: Click on the [Preview script] button to run and view all created steps.

Step 10: Click on the [Run all] button to run all preconditions.

Step 11: Click on the [Run script] button to run the recorded steps one at a time => After running the script, the device’s streaming screen will show the live execution of whatever steps that were recorded. The step status will be displayed at the end of each step.

Step 12: Click on the [Back] button => The “Create script” screen will be displayed => Click on the [Save] button.

Step 13:  Popup “Save as Pre-condition” will be displayed => Enter the information of the precondition that you want to save => Click on the [Save] button => This Precondition will be saved in the “Manage Precondition” screen.

II. Create a new test script

• The script creation screen is displayed by step: Click on the [Manage Test Script] item => Click [Create with ATOMP Studio] => Select any device.

1.      Upload a CSV file (if necessary)

Users can upload a CSV file containing two columns of data (key/value pairs) and use those pairs as variables inside ATOMP Studio.

From the “Predefined Actions” tab, click on “Expand” at “CSV External Input”, then click “Upload” to upload a CSV file.

A CSV file has the following format (Column A: Variable Name, Column B: Value)

After uploading the CSV file, users can use those variables in any textbox while creating test script by typing “$+variable name”

2.      Switch to the [Recording] mode

• To start creating a test script, you need to switch to the [Recording] mode by clicking on the button [Record script] or the Eye icon   => below is a sample of the Recording mode.
  

• Users can select a screen element (icon, button, text, etc…) to execute some actions.

3.      Select Precondition(s)

Step 1: On the script creation screen, click on the [add new] button.

Step 2: Select one or more preconditions from the precondition list of the project

➩ When the script is running, these selected preconditions will run from top to bottom. List of selected preconditions will be displayed as below:

4.      Create Test Steps

Step 1: Switch to the “Select Element” mode (by clicking on the icon   )

Step 2: Select an element on the streaming screen

Step 3: Select an action you want to take with the element selected in step 2

• If the selected element is an icon or a button, the available actions are (Tap, Double Tap, Long Press)
• If the selected element is a Text Input box, click on the [Send Keys] button to input text to the element.
• If you want check 2 images by AI when having automatic action to change screen, click on the [Add Blank Action] button to create a blank action, when this step is run, the automation script will not perform any action on the device.

Step 4:  If the action is [Send Keys] -> a popup will be shown for users to input characters.

=> After executing 1 action, the tool automatically generates a test script for that action and displays as a step (refer to the picture below)

If you want to delete the text on the filled textbox, you select the element that needs deleting text then select Clear action.

Step 5: If the action is [Swipe], you need to switch to the “Swipe By Coordinates” mode (by clicking on the icon ). Then users select 2 points in the middle of the screen to scroll.

=> After executing 1 action, the tool automatically generates a test script for that action and displays as a step (refer to the picture above).

If users want to perform other actions (Tap, Double tap, send keys,..), users need to switch to the “Select Element” mode.

Step 6: If you want to click on a point on the streaming screen, you switch to the “Tap by Coordinates” mode (by clicking on the icon ). Users click on the point  on the streaming screen, then the tool generates automatically a test step for that action and displays as below.

If users want to perform other actions (Tap, Double tap, send keys,..), users need to switch to the “Select Element” mode.

Step 7: To long press on a point on the screen, you switch to the “Long Press By Coordinates” mode (by clicking on the icon ).  The Duration of Press pop up is displayed, users set a time interval for this action, then click OK button. Users click on the point  on the streaming screen, then the tool generates automatically a test step for that action and displays as below.

Step 8: When you can’t select the desired element on the streaming screen, you need to click on the icon  to refresh source code. Then the source code has matched the element on the screen,  users select element and perform action normally.

5.      Create an Expectation

Step 1: Select an element that you need to check on the Streaming screen

Step 2: The PROPERTIES box will show the properties of the selected element –> choose a property to create an expectation that you want.

• If you want to check the UI of the screen, select the icon camera inside the “Expectation” column to capture screen as reference for future comparison.

• To verify relative position of an element, you choose one of properties: isOnTopOf, isOnBottomOf, isOnLeftOf, isOnRightOf.

For example: On the All apps screen, you need to verify that the [Approve Now] text is on left of the [Recognition] text. Please follow the steps as below:

– Select the [Approve Now] element on the streaming screen.

– Click on the [+] button next to the [isOnLeftOf] property. Then popup Relative Position Comparison is displayed.

– Users select the [Recognition] element on the streaming screen, the [Recognition] element will be displayed on the pop up. Then users click on the [Select] button.

– Finally, the expectation will be added to script as picture:

• If you want to use AI Visual check, select icon to add AI Visual check expectation to compare visual images which help you increase accuracy and reduce effort for testing. AI Visual check will capture the screen to be a visual reference for later test and let you know if during regression test, the actual screen has difference with the captured screen.

1. You can drag mouse to specify which part is dynamic data and can be excluded in visual comparison. After that, you click on “OK” button to save Expectation or click on icon    to delete selected data area.

2. You can also click the link reference image in Expectation to view again or edit chosen data by following part (1). Click on icon if you want to delete AI Visual check expectation.

User can view evidence at Tester40 [Test Result] page.

The system also supports comparing images of element when confirming exepectation. Please follow these steps:

• Click on an element on the streaming screen à Click on [+] button besides  [Image] text in Custom Properties.

• Then [Compare image] pop up display. Popup has 2 options:

– Upload image:  Allowing  uploading an existing image or an image cutted from an xd file (JPG, JPEG, PNG format).

– Use current image: Allowing  to automatically capture the current screenshot, then based on the element position, automatically crop the image of that element.

Option 1: Upload image

Firstly, Users must click on tab Upload image then select image file and press OK. After selecting image, photo is uploaded  to ATOM Storage. If there is an existing image, the new uploaded image will replace the old one. ==> After uploading, the added expectation <Element> is displayed the same as <filename of the uploaded image>

Option 2: Use current image

Click on button to  use current element’s image as reference then click on [OK] button, image is used as expectation.

6.      Feature IF – THEN – ELSE

Step 1: Add [IF] block

• On the [PREDEFINED ACTIONS] tab, click on [Command] menu to expand it
• Expand [Conditional] sub-menu
• Click on [IF Statement] to add IF block to script

➩  After that, new block will appear on Recorded Script section.

1) Hover on  to open menu

• Click on “Add condition” add a new condition to current [IF] block, it will open input form as above.
• Click on “Add Sub-IF” to add a [Sub-IF] block to current block.
• Click on “Add ELSE IF” to add [ELSE IF] block after current [IF] block.
• Click on “Add ELSE” to add [ELSE] block after current [IF] block.
• Click on “Delete Block” to delete current block. If deleting a [IF] block will delete all [ELSE IF] and [ELSE] blocks that come with it. User must confirm before action to be executed.

2) Click on  to stop working on current block.

3) Click on  to stop working on current block,  to work on a block (pin – unpin block).

4) Delete a condition.

5) Edit condition.

6) Logical operator (uses when block has 2 more conditions).

7) Element to do comparison operation.

8) Property of element (must be specified in order to save condition).

9) Operator.

10) Value to compare (default is element’s property value).

11) Click to save condition.

12) Click to cancel input condition.

13) Block action (will be executed if condition is met).

✤ Some cases when working with IF – THEN – ELSE function.

• When adding condition without selecting element or property to do comparison operation, a message will appear like bellow and condition will not be saved until user specify element & property.

• When deleting all [IF] – [ELSE IF] block condition, a notification will appear with below content to inform user that block condition is empty.

• When working on [IF] – [ELSE IF] block which does not contain any condition, script will not be recorded and a notification with below content will appear.

• When trying to save script with an empty condition [IF] – [ELSE IF] block, script will not be saved and notify an error message like below.

✤ Preview Script with IF – THEN – ELSE function.

• All [IF], [ELSE IF], [ELSE] block which condition(s) does not meet will be ignore & show error message like above.
• When previewing script with empty condition [IF] – [ELSE IF] block, script will break at block which condition is empty!

7.      Feature Select Step to take evidence on Tester 4.0

Step 1: Tick on checkbox in the last column of test script which step you want to take evidence when running on Tester 4.0.

Step 2: After running sprint done, you click “Download evidence” button to get the evidence ticked in step 1.

User can view evidence at Tester40 [Test Result] page.

8.      Feature clone

Step 1:

• Clone one test step: Click on one test step which you want to clone => Right mouse and choose “Clone”.

• Clone some test steps:

If the test steps are continuous: Click on the first or the last test step and mouse hover all test steps which you want to clone => Right mouse and choose “Clone”.

If the test steps are not continuous: Click on any test steps and hold Ctrl and click on other test steps => Right mouse and choose “Clone”

Step 2:

• Choose one step to clone before or clone after

Click on one test step what you want to clone after or before that => Right mouse and choose “Clone before” or “Clone after”

• Choose some step to clone before or clone after

If the test steps are continuous: Click on the first or the last test step and mouse hover all test steps which you want to clone => Right mouse and choose “Clone before” or “Clone after”.

If the test steps are not continuous: Click on any test steps and hold Ctrl and click on other test steps => Right mouse and choose “Clone before” or “Clone after”.

9.      Preview Script

Step 1: Click the [Stop] button to finish recording the test script

Step 2: You can preview the created script from any available device by clicking on the [Preview script] button

From this screen, users can preview the script from another device by clicking on the [Select device] button => The Selecting device screen will be displayed. (The selected device for creating the script will be selected as default for preview).

-> After selecting device, click the  button to start previewing the script.

10.      Save a script

Step 1: Click on the [Save script] button -> A dialog will be displayed.

Step 2: Input the reference ID and description for the script.

Step 3: Click on the [Save Test Script] button.

➩  After a test script is saved, it can be found in the screen “Manage Test script” in Tester 4.0.

11.      Edit a script

Users can edit the created script by following these steps:

Step 1: From the “Manage Test Script” screen, select the “Edit” icon from the script you want to edit => Select device screen will be displayed => Perform a device selection just like creating a normal script.

Step 2:  After the device is selected => The script creation screen will be displayed, and the users can edit the script normally => Then the users can save the script by 2 methods:

• Save to the existing script
• Save as a new script

12. Select other script

On the “Create script with ATOMP Studio” screen, users can easily choose other script from the created script list to edit by following these steps:

Step 1: From the “Create script with ATOMP Studio” screen, select the “Select other script”.

Step 2:The created script list will be displayed, and the users can choose “Test script” or “Test precondition” to choose the script you want to edit.

13. Clone scripts

Users can clone the created script by following these steps:

Step 1: From the “Manage Test Script” screen, select the “Options” icon from the script you want to clone => Choose “Clone” button.

Step 2: Enter New Information => Choose “Clone” button, then script will be saved in Manage Test Script.

III.  Mirror 1 action on multiple devices

Step 1: Click on the icon mirror   -> The popup list of available devices will be displayed.

Step 2: Select a device that will mirror the actions of the main device.

• After selecting a mirror device, the streaming of all mirror devices will be shown.

• User’s actions in the main device will also be performed in the mirror devices.

Step 3: Capture the evidence on all devices by clicking on the icon capture screenshot  from the tab bar.

=> Screenshots in all devices will be shown (both main device and mirror devices).

Step 4: Click on the icon under each image => screenshot will be copied to the clipboard.

Step 5: Click on the [Download] button => download evidence (screenshot) from all devices.

IV. Ruler Measurement

This function is intended to increase productivity comparing the difference between UI and XD.

To use this function, please follow the steps below:

Step 1: Click on the “Ruler” icon from the navigation bar to open the MEASUREMENT screen.

Step 2: If you want to measure size and position please click [Ruler] tab, if you want to measure color code then click [Color] tab.

– “Ruler” tab

To pin an element, click on the [Measure] button, then click on any element from the streaming screen, or from the Source list.

– “Color” tab

To pin an element, Click on the [Filter] button, then click on any element from the streaming screen, or from the Source list.

B.      Create a test script with PC Web

I.      Create a Precondition

Precondition can be created and used for multiple scripts with the same precondition. There are two ways to create a precondition: Create with ATOMP Studio and Import precondition.

Option 1: Create with ATOMP Studio

Step 1: Click on the [Manage Test Precondition] button.

Step 2: Click on the [Create with ATOMP Studio] button. The Studio Web primary screen will be displayed.

Step 3: Select a precondition parent (if applicable) by clicking on [+] button besides text [Precondition].

After [Add Precondition] popup is displayed, user can tick precondition which you want to add then click on [Add Precondition] button. The Parent Precondition will added to current precondition.

When you add parent precondition, you can click on button to preview precondition.

Step 4: Click on the button [Record script]   to start recording your browser’s interactions.

Step 5: Before you can start recording, you must specify a valid base URL for your project by clicking  on the [START RECORDING] button to open your URL. Your test will start by navigating to this URL.

Step 6: Once the URL has been opened, after executing 1 action, the tool automatically generates a test script for that action and displays as a step (refer to the picture below)

Step 7: Click on the  button to stop recording => the  button will be enabled.

Step 8: Click on the button to run and view all created steps.

Step 9: Click on  button to save precondition. Popup “Save  Pre-condition” will be displayed.

=> Enter the information of the precondition that you want to save => Click on the [Save] button => This Precondition will be saved in the “Manage Precondition” screen.

Option 2: Import precondition

If you have  available precondition’s test scripts, users can import it into the system. Please follow these steps:

Step 1: Click on the [Import Precondition] button to open the [Import Precondition] pop up.

Step 2: Select the test script file you want to import (file format must be correct as defined by the system), then click the [Open] button.

II.       Create a new test script

• Click on the [Manage Test Script] button => Click [Create with ATOMP Studio]. The Studio Web primary screen will be displayed.

1.   Start the [Recording] mode

• Click on the button [Record script]  to start recording your browser’s interactions. Below is a sample of the Recording mode.

• Before you can start recording, you must specify a valid base URL for your project and click on the [START RECORDING] button to open your URL.

2.      Select Precondition(s)

Step 1: On the script creation screen, click on the [+] button beside the [Precondition] text.

Step 2: Select one or more preconditions from the precondition list of the project then click on [Add precondition] button.

When the script is running, these selected preconditions will run from top to bottom. List of selected preconditions will be displayed as below:

3.      Create Test Steps

• Once the URL has been opened, after executing 1 action, the tool automatically generates a test script for that action and displays as a step (refer to the picture below).

• Additionally, users can create a step manually by utilizing the “Command” input box.

Customize steps

• Command has a series of commands that users can use to interact with the web app.
• Target has some element types for users to choose from: (list target to find element).

+ xpath: attributes

+ css

+ xpath: position

• Description: a step description.
• Delay(ms): a delay time before executing the current step.
• Capture: capture web app screen during this current step’s execution.
• Value: input value for each command.
• User can select different element types for the target by clicking this icon

✤  Here are some commands that are commonly used:

   3.1. Click command

• The purpose of click command is to click on any UI element in the application.
• While the row is selected, enter the ATOMP Studio command ‘click’ to the Command box field and enter the XPath locating strategy into the Target box field.

3.2.      Assert text command

• The purpose of assert text command is to check the text on the UI element ( Checking  the text on this button is a per our requirement)
• While the row is selected, enter the command ‘assert text’ to the Command box field, enter the id locating strategy into the Target box field:

• In addition, the user can select the Mouse Over/Assert/Store/Verify/Wait For command by right clicking on the object that the user wants to check and show as below: 

+ Mouse over : The purpose of the mouse over command is to perform mouse the hover action on the given UI element.

+ Assert: The purpose of the assert command is to check the value stored in a variable is according to the expected result. (Ex: assert text, assert not text,…).

+ Store: The purpose of the store command is to store any text into a variable for easy re-use. Follow  (Ex: store xpath count, store text,…).

+ Verify: The purpose of the verify command is to check the value stored in a variable. The variable’s value will be converted to a string for comparison. (Ex: verify check, verify not text,…).

+ Wait for element visible: The purpose of the wait for element visible command is to wait for the element to get displayed on the page. (Ex: wait for element not visible, wait for element present,…).

3.3.      Store xpath count

The purpose of the store xpath count command is to retrieve and store the count of the UI elements located using the given XPath Locating strategy into a variable in ATOMP Studio

+ Gets the number of nodes that match the specified xpath

3.4.      Echo command

• The purpose of echocommand is to print the messages given in ATOMP Studio. Useful for debugging
• The echo command usually comes with the store command (Ex: store attribute/ store xpath count/ store text….)

3.5.      If and end command

The purpose of the if command is to check whether the given condition is true or false. If the condition results in true, the ATOMP Studio statements inside the if and end commands will be executed. If the condition results in false, the ATOMP Studio statements inside the if and end commands won’t be executed.

3.6.      Else if/ send keys command

• Else if is the command in ATOMP Studio will be executed when the if condition results in false and we have another condition to be validated before going to the else block.
• Simulates keystroke events on the specified element, as though you typed the value key-by-key.

• All if and else/else/else if commands end with “end” command

3.7.      Add selection

Add a selection to the set of options in a multi-select element.

3.8.      Answer on next prompt

Affects the next alert prompt. This command will send the specified answer string to it. If the alert is already present, then use “webdriver answer on visible prompt” instead.

3.9.      Assert

Check that a variable is an expected value. The variable’s value will be converted to a string for comparison. The test will stop if the assert fails.

+ Pass: same

+ Fail: different

3.10.  Assert alert

Confirm that an alert has been rendered with the provided text. The test will stop if the assert fails.

+ Pass: displayed

+  Fail: not displayed

3.11.  Assert checked

• Confirm that the target element has been checked. The test will stop if the assert fails.

Different from assert checked and verify checked

assert checked	verify checked
Hard assertion	Soft assertion

3.12.  Assert confirmation

• Confirm that a confirmation has been rendered. The test will stop if the assert fails.

+ Pass: displayed

+ Fail: not displayed

3.13.  Assert element not present command

Assert element not present is one of the commands in ATOMP Studio web.

The purpose of assert element not present command in ATOMP Studio web, is to check whether the given UI  element is not present on the page.

3.14.  Assert not checked command

Assert not checked is one of the commands in ATOMP Studio web.

The purpose of assert not checked command in ATOMP Studio web, is to check whether the given checkbox option is not selected.

3.15.  Assert not editable command

Assert not editable is one of the commands in ATOMP Studio web.

The purpose of assert not editable command in ATOMP Studio web, is to check whether the given field is in a non-editable state.

3.16.  Assert not selected value command

Assert not selected value is one of the commands in ATOMP Studio web. This option works in opposite to the assert selected value command.

The purpose of assert not selected value command in ATOMP Studio web, is to check whether the given option is not in the selected state in dropdown field.

3.17.  Assert not text command

Assert not text is one of the commands in ATOMP Studio web and is the opposite of assert text command.

The purpose of assert not text command in ATOMP Studio web, is to check that the given text is not available on the UI element. (i.e. The text between the HTML tags of the located UI element)

3.18.  Assert prompt command

Assert prompt is one of the commands in ATOMP Studio web.

The purpose of assert prompt command in ATOMP Studio web, is to check whether the prompt dialog is displayed during execution.

3.19.  Assert selected value command

Assert selected value is one of the commands in ATOMP Studio web.

The purpose of assert selected value command in ATOMP Studio web, is to check whether the given option is selected in the dropdown field.

3.20.  Assert selected label command

Assert selected label is one of the commands in ATOMP Studio web.

The purpose of assert selected label command in ATOMP Studio web, is to check whether the given option is selected in the dropdown field using its label text or display text.

3.21.  Assert text command

Assert text is one of the commands in ATOMP Studio web.

The purpose of assert text command in ATOMP Studio web, is to check the text on the UI element (i.e. The text between the HTML tags of the located UI element)

3.22.  Assert value command

Assert value is one of the commands in ATOMP Studio web.

The purpose of assert value command in ATOMP Studio web, is to check that the value attribute value of the given UI element.

3.23.  Assert title command

Assert title is one of the commands in ATOMP Studio web.

The purpose of assert title command in ATOMP Studio web, is to check the title of the current page.

3.24.  Check command

Check is one of the commands in ATOMP Studio web.

The purpose of check command in ATOMP Studio web, is to select the radio button.

3.25.  Choose cancel on next confirmation command

Choose cancel on next confirmation is one of the commands in ATOMP Studio web.

The purpose of choose cancel on next confirmation command in ATOMP Studio web, is to plan for cancelling the confirmation dialog before it is displayed. i.e. Once the confirmation dialog is displayed on the page, it will be cancelled.

3.26.  Choose cancel on next prompt command

Choose cancel on next prompt is one of the commands in ATOMP Studio web.

The purpose of choose cancel on next prompt command in ATOMP Studio web, is to plan for cancelling the prompt before it is displayed. i.e. Once the prompt is displayed on the page, it will be cancelled.

3.27.  Choose ok on next confirmation

Choose ok on next confirmation is one of the commands in ATOMP Studio web.

The purpose of choose ok on next confirmation command in ATOMP Studio web, is to plan for accepting the confirmation dialog before it is displayed. i.e. Once the confirmation dialog is displayed on the page, it will be accepted.

3.28.  Click command

Click is one of the commands in ATOMP Studio web.

The purpose of click command in ATOMP Studio web, is to click on any UI element in the application.

3.29.  Click at command

Click at is one of the commands in ATOMP Studio web.

The purpose of click at command in ATOMP Studio web, is to click on any UI element at the given x & y coordinate position of the UI element.

3.30.  Close command

Close is one of the commands in ATOMP Studio web.

The purpose of close command in ATOMP Studio web, is to close the browser window.

3.31.  Debugger command

Debugger is one of the commands in ATOMP Studio web.

The purpose of debugger command in ATOMP Studio web, is to pause the execution of the ATOMP Studio web Automation script for debugging purpose (i.e. for identifying the root cause of any problem and rectifying it)

3.32.  Double click command

Double click is one of the commands in ATOMP Studio web.

The purpose of double click command in ATOMP Studio web, is to double click on any UI element.

3.33.  Double click at command

Double click at is one of the commands in ATOMP Studio web.

The purpose of double click at command in ATOMP Studio web, is to double click on any UI element at the given x & y coordinate position of the UI element.

3.34.  Echo command

Echo is one of the commands in ATOMP Studio web.

The purpose of echo command in ATOMP Studio web, is to print the messages given in ATOMP Studio web.

3.35.  Edit content command

Edit content is one of the commands in ATOMP Studio web.

The purpose of edit content command in ATOMP Studio web, is to change the value of the given UI element.

3.36.  Execute script commnad

Execute script is one of the commands in ATOMP Studio web.

The purpose of execute script command in ATOMP Studio web, is to execute the JavaScript code in ATOMP Studio web.

3.37.  For each command

For each is one of the commands in ATOMP Studio web.

For each is the command in ATOMP Studio web used for executing a set of same statements multiple times until all the values in the given array (i.e. multiple set of values stored in a single variable) are completed.

3.38.  Pause Command

Pause command in ATOMP Studio Web is used to pause the execution in ATOMP Studio web for the required period of time.

3.39.  Remove selection command

Remove selection is one of the commands in ATOMP Studio.

The purpose of the remove selection command is to remove the selection of selected options in the multi-selection box field. In the dropdown field, we can only select one option, but whereas in multi-selection box field, we can select more than one options. Hence using add selection command in ATOMP Studio Web, we can select more than one option in a Multi-selection box field.

3.40.  Run Scripts Command

Run Script is one of the commands in ATOMP Studio Web.

The purpose of run script command in ATOMP Studio, is to execute the JavaScript code snippets in ATOMP Studio.

3.41.  Execute Async Script command

Execute async script is one of the commands in ATOMP Studio.

The purpose of execute async script command in ATOMP Studio, is to execute the async snippet of JavaScript code in ATOMP Studio.

3.42.  Select command

Select command is one of the commands in ATOMP Studio Web.

The purpose of select command in ATOMP Studio Web is to select an option from the dropdown list.

3.43.  Select window command

Select window is one of the command in ATOMP Studio Web.

The purpose of the select window command is to select or switch to another window. We can either use the window title or window tab index to select a window using the select window command.

3.44.  Select Command

Select is one of the commands in ATOMP Studio.

The purpose of select command in ATOMP Studio, is to select an option from the dropdown field.

3.45.  Do and Repeat if command

Do and repeat if are the commands in ATOMP Studio Web, which needs to be used together.

Do and repeat if are the command in ATOMP Studio Web used for executing a set of same statements multiple times until the repeat if condition becomes false.

Difference between while and  do commands

In while command, the condition to be checked for entering into the iterative loop block will be at the beginning. Whereas in do command, we will check the condition at the end of the iterative loop block using repeat if command.

3.46.  Set Speed Command

Set speed is one of the commands in ATOMP Studio Web.

The purpose of the set speed command is to modify the default speed of ATOMP Studio Web execution (i.e. 0 seconds) to the required milliseconds.

3.47.  Type command

Type is one of the commands in ATOMP Studio.

The purpose of type command in ATOMP Studio, is to type any given text into the text fields in the application.

3.48.  Store attribute Command

Store attribute is one of the commands in ATOMP Studio web.

The purpose of the store attribute command is to retrieve and store the value of the given attribute name of the located UI element into a variable in ATOMP Studio.

3.49.  Store json command

Store json is one of the commands in ATOMP Studio.

The purpose of the store json command is to retrieve and store json content into a variable in ATOMP Studio.

3.50.  Store window handle command

Store window handle is one of the commands in ATOMP Studio.

The purpose of the store window handle command is to store the window using its locator i.e. tab index or title.

3.51.  Store title command

Store title is one of the commands in ATOMP Studio web

The purpose of the store title command is to retrieve and store the title of the page into a variable in ATOMP Studio web.

3.52.  Store text command

Store text is one of the commands in ATOMP Studio web

The purpose of the store text command is to retrieve and store the text between the HTML tags of the located UI element into a variable in ATOMP Studio web.

3.53.  Store value command

Store value is one of the commands in ATOMP Studio web.

The purpose of the store value command is to retrieve and store the value attribute value of the located UI element into a variable in ATOMP Studio web.

3.54.  Store Command

Store is one of the commands in ATOMP Studio web.

The purpose of the store command is to store any text into a variable in ATOMP Studio web

3.55.  Store window handle command

Store window handle is one of the commands in ATOMP Studio.

The purpose of the store window handle command is to store the window using its locator i.e. tab index or title.

3.56.  Send keys command

Send keys is one of the commands in ATOMP Studio web.

The purpose of the send keys command is to press the required keyboard key using any of the below-specified keyboard keycodes:

Key Code	Function
KEY_LEFT	Navigation Left
KEY_UP	Navigation Up
KEY_RIGHT	Navigation Right
KEY_DOWN	Navigation Down
KEY_PGUP or KEY_PAGE_UP	Page up
KEY_PGDN or KEY_PAGE_DOWN	Page down
KEY_BKSP or KEY_BACKSPACE	Backspace
KEY_DEL or KEY_DELETE	Delete
KEY_ENTER	Enter
KEY_TAB	Tab

3.57.  Set window size command

Set window size is one of the commands in ATOMP Studio web

The purpose of set window size command in ATOMP Studio web, is to resize the browser window.

3.58.  Times command

Times is one of the commands in ATOMP Studio web and we can end it with end command.

Times is the command in ATOMP Studio web used for executing a set of statements the required number of times.

3.59.  Uncheck command

Uncheck is one of the commands in ATOMP Studio web.

The purpose of uncheck command in ATOMP Studio web, is to deselect the radio button.

3.60.  Verify Command

Verify is one of the commands in ATOMP Studio.

The purpose of the verify command is to check the value stored in a variable is according to the expected result.

3.61.  Verify title command

Verify title is one of the commands in ATOMP Studio.

The purpose of verify title command in ATOMP Studio is to check the title of the current page.

3.62.  Verify text Command

Verify text is one of the commands in ATOMP Studio.

The purpose of verify text command in ATOMP Studio, is to check the text on the UI element. (i.e. The text between the HTML tags of the located UI element

3.63.  Verify not text command

Verify not text is one of the commands in ATOMP Studio and is the opposite of verify text command.

The purpose of verify not text command in ATOMP Studio, is to check that the given text is not available on the UI element. (i.e. The text between the HTML tags of the located UI element)

3.64.  Verify selected value command

Verify selected value is one of the commands in ATOMP Studio.

The purpose of verify selected value command in ATOMP Studio, is to check whether the given option is selected in the dropdown field.

3.65.  Verify not selected value command

Verify not selected value is one of the commands in ATOMP Studio. This option works in opposite to the verify selected value command.

The purpose of verify not selected value command in ATOMP Studio, is to check whether the given option is not in the selected state in dropdown field.

3.66.  Verify selected label command

Verify selected label is one of the commands in ATOMP Studio.

The purpose of verify selected label command in ATOMP Studio, is to check whether the given option is selected in the dropdown field using its label text or display text.

3.67.  Verify checked command

Verify checked is one of the commands in ATOMP Studio.

The purpose of verify checked command in ATOMP Studio, is to check whether the given checkbox is in the selected state.

3.68.  Verify not checked command

Verify not checked is one of the commands in ATOMP Studio.

The purpose of verify not checked command in ATOMP Studio, is to check whether the given checkbox option is not selected.

3.69.  Verify editable command

Verify editable is one of the commands in ATOMP Studio.

The purpose of verify editable command in ATOMP Studio, is to check whether the given field is in an editable state.

3.70.  Verify not editable command

Verify not editable is one of the commands in ATOMP Studio.

The purpose of verify not editable command in ATOMP Studio, is to check whether the given field is not in an editable state.

3.71.  Verify element present command

Verify element present is one of the commands in ATOMP Studio.

The purpose of verify element present command in ATOMP Studio, is to check whether the given UI  element is present on the page.

3.72.  Verify element not present command

Verify element not present is one of the commands in ATOMP Studio.

The purpose of verify element not present command in ATOMP Studio, is to check whether the given UI  element is not present on the page.

3.73.  Verify value command

Verify value is one of the commands in ATOMP Studio.

The purpose of verify value command in ATOMP Studio, is to check that the value attribute value of the given UI element.

3.74.  Mouse down, mouse move at and mouse up command

Mouse down, mouse move at and mouse up are commands in ATOMP Studio web.

• The purpose of the mouse down command is to perform mouse left click operation.
• The purpose of the mouse move at command is to move the holder UI element to the target element.
• The purpose of the mouse up command is to release the mouse click to release the so far held UI element to the desired element in ATOMP Studio web.

3.75.  Mouse down at, mouse move at and mouse up at command

Mouse down at, mouse move at and mouse up at are commands in ATOMP Studio web.

• The purpose of the mouse down at command is to perform mouse left click operation at the given x & y coordinate position.
• The purpose of the mouse move at command is to move the holder UI element to the target element at the given x & y coordinate position.
• The purpose of the mouse up at command is to release the mouse click to release the so far held UI element to the desired element at given x & y coordinate position in ATOMP Studio web.

3.76.  Mouse out and Mouse over command

Mouse over and mouse out are the commands in ATOMP Studio web.

The purpose of the mouse over command is to perform mouse the hover action on the given UI element. And the purpose of the mouse out command is to move the mouse outside of the hovered UI element.

3.77.  Open command

Open is one of the commands in ATOMP Studio web.

The purpose of open command in ATOMP Studio web, is to open the given Application base URL in the browser.

3.78.  Wait for element editable command

Wait for element editable is one of the commands in ATOMP Studio.

The purpose of the wait for element editable command is to wait for the element to get editable. i.e. If any required element on the application is by default in non-editable state and gets editable in some time, we can use wait for element editable command to wait for the element to get editable, before editing the element.

3.79.  Wait for element not editable command

Wait for element not editable is one of the commands in ATOMP Studio.

The purpose of the wait for element not editable command is to wait for the element to get non-editable. i.e. If any required element on the application is by default in editable state and gets non-editable in some time, we can use wait for element not editable command to wait for the element to get non-editable.

3.80.  Wait for element not present command

Wait for element not present is one of the commands in ATOMP Studio.

The purpose of the wait for element not present command is to wait for the element to be not present on the UI and also its HTML code is not present in the HTML DOM of the page.

3.81.  Wait for element not visible command

Wait for element not visible is one of the commands in ATOMP Studio.

The purpose of the wait for element not visible command is to wait for the element to get disappear from the page i.e. If any required element on the application is by default displayed and then disappear in some time, we can use wait for element not visible command to wait for the element to disappear from the page.

3.82.  Wait for element present command

Wait for element present is one of the commands in ATOMP Studio.

The purpose of the wait for element present command is to wait for the element to be present on the UI and also the HTML DOM of the page.

3.83.  Wait for element visible command

Wait for element visible is one of the commands in ATOMP Studio.

The purpose of the wait for element visible command is to wait for the element to get displayed on the page i.e. If any required element on the application is by default not displayed and gets displayed in some time, we can use wait for element visible command to wait for the element to get displayed before performing any operation on the element.

3.84.  Webdriver answer on visible prompt command

Webdriver answer on visible prompt is one of the commands in ATOMP Studio.

The purpose of webdriver answer on visible prompt command in ATOMP Studio, is to enter the answer into the prompt when the prompt is actually displayed.

3.85.  Webdriver choose cancel on visible confirmation command

Webdriver choose cancel on visible confirmation is one of the commands in ATOMP Studio.

The purpose of webdriver choose cancel on visible confirmation command in ATOMP Studio, is to select the ‘Cancel’ button on the displayed confirmation dialog.

3.86.  Webdriver choose cancel on visible prompt command

Webdriver choose cancel on visible prompt is one of the commands in ATOMP Studio.

The purpose of webdriver choose cancel on visible prompt command in ATOMP Studio, is to cancel the prompt when it is actually displayed.

3.87.  Webdriver choose OK on visible confirmation command

Webdriver choose ok on visible confirmation is one of the commands in ATOMP Studio.

The purpose of webdriver choose ok on visible confirmation command in ATOMP Studio, is to select the ‘OK’ button on the displayed confirmation dialog.

3.88.  While command

While is one of the commands in ATOMP Studio and we can end it with end command.

While is the command in ATOMP Studio used for executing a set of same statements multiple times until the while condition becomes false.

3.89.  Drag and drop to object command

Drag and drop to object is one of the commands in ATOMP Studio web.

The purpose of drag and drop to object command in ATOMP Studio web, is to drag an UI element and drop it at another UI element.

3.90.  Select Frame Command

Select Frame is one of the commands in ATOMP Studio Web.

The purpose of select frame command in ATOMP Studio web, is to select the required frame before performing any UI element inside it.

3.91. Screen shot full page

Screen shot full page is one of the commands in ATOMP Studio web.

The purpose of the Screen shot full page command in ATOMP Studio web is to capture full page to check overall layout.

4.      Preview script

Step 1: Click the [Stop] button to finish recording the test script.

Step 2: You can preview the created script by clicking on the icon. If you add precondition to test script, you can preview all precondition and test script by clicking on the  icon .

5.     Save scripts

Step 1: Click on the [Save script] button -> A dialog will be displayed.

Step 2: Input the reference ID and description for the script.

Step 3: Click on the [Save Test Script] button.

➩  After a test script is saved, it can be found in the screen “Manage Test script” in Tester 4.0.

6.     Edit script

• Users can edit the created script by following these steps:

Step 1: From the “Manage Test Script” screen, select the “Edit” icon from the script you want to edit => ATOMP Studio web screen will be displayed => Perform editing test script just like creating a normal script.