Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Introduction 

You will find some actions listed in strikethrough text on the Test Cases and Tasks screens. We recommend not to use these actions when developing a new test case as there are better options available now for the same operation. While these actions will continue to work in this release, they might be taken away in future releases with appropriate migration methods.

In reports also, you will find these actions in the strike-through text.

Following is the complete list of deprecated actions:

AnswerForNextDialog

We recommend using the WaitForAlertAndSendText action instead of this action. In WaitForAlertAndSendText, Qualitia gives you provision to set and send the desired string in the next pop up being displayed. This action gives you more control by its ability to provide timeout and polling interval for the expected condition to be achieved.

ClickAndWaitClickandchooseOkOnNextConfirmation

ClickandchooseOkOnNextConfirmation

Instead of using this action, you can divide this into 2 steps for better maintenance and control;

  1. Click (based on the object class) and
  2. WaitForAlertAndSpecifyBehavior.

The WaitForAlertAndSpecifyBehavior allows  allows you specifying the action to be taken on the next pop up window as Alert Box as a first parameter (accept or or dismiss). This action gives you more control by its ability to provide timeout and polling interval for the expected condition to be achieved.

List of deprecated actions

Table of Contents
maxLevel2
minLevel2

ClickLinkAtCellandchooseOkOnConfirmation

Instead of using this action, you can divide this into 2 steps;

  1. ClickLinkAtCell
and
  1.  and 
  2. WaitForAlertAndSpecifyBehavior.

The WaitForAlertAndSpecifyBehavior allows  allows you specifying the action to be taken on the next pop up window as a first parameter (accept or dismiss). This  This action gives you more control by its ability to provide timeout and polling interval for the expected condition to be achieved.

ClickAndWait

We strongly recommend not to use this action. Instead of using this action, we recommend you dividing it into two 2 steps;

  1. Click and
  2. WaitForExistence or WaitForVisibility (
element
  1. based on the object class).

These actions give you more control by its ability to provide timeout and polling interval for the expected condition to be achievedfulfilled.

You can also control the page's loading time by specifying page timeouts under Configuration Settings or using the SetPageLoadTimeOut action.

SelectItemAndWait

configure maximum wait time for the page to load using Page timeout (under Configuration Settings) or using the SetPageLoadTimeOut action.

DragAndDropToOffset (Deprecated)

This action drags and drops the specified web element at the specified location.  You are recommended to use DragAndDropToObject.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

offsetX

Enter the offset in pixels from the current location to which the element should be moved. The offset parameter can be as +100,100 , -100, 10, and so on.

Yes

String

offsetY

Enter the offset in pixels from the current location to which the element should be moved. The offset parameter can be as -100,100 , +100, and so on.

Yes

String

Example:

DragAndDropOffset            "100"              "500" 

StoreSubString

This action should be replaced with StoreSubStringNew. This new action does not have any change in the functionality but you will have better control and consistency during the test case execution.

SelectItemAndWait

We strongly recommend not to use this action. Instead of using this action, we recommend you dividing it into 2 steps;

This action can be divided into two 2 different steps for better performance and consistency. We recommend you using :

  1. SelectItems and
followed by
  1. WaitForExistence or WaitForVisibility based on the next object you are going to
work
  1. operate on.

These actions give you more control by its ability to provide timeout and polling interval for the expected condition to be fulfilled.

WaitForPageToLoad

We strongly recommend not to use this action. Instead of using this action, we recommend you using WaitForExistence or WaitForVisibility based on the next object you are going to work operate on.

StoreSubString

This action should be replaced with StoreSubStringNew. This new action does not have any change in the functionality but you will have better control and consistency during the test case executionDeveloping the test case this way gives you better control over your test case and help you find defects more effectively saving your time when debugging the test case

WaitForObject

We strongly recommend replacing not to use this action. Replace this action with WaitForExistence.  

ClickLinkAtCellTH

ClickCheckboxInCellTH

ClickImageInCellTH

GenerateAndStoreMaximumValue
Using WaitForExistence gives you better control over the test case resulting consistent test case execution.