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.

ClickandchooseOkOnNextConfirmation

Instead of using this action, you can divide this into 2 steps; Click (based on the object class) and WaitForAlertAndSpecifyBehavior. The WaitForAlertAndSpecifyBehavior allows you specifying the action to be taken on the next pop up window as a first parameter (accept or dismiss). This action gives you more control by its ability to provide timeout and polling interval for the expected condition to be achieved.

ClickLinkAtCellandchooseOkOnConfirmation

Instead of using this action, you can divide this into 2 steps; ClickLinkAtCell and WaitForAlertAndSpecifyBehavior. The WaitForAlertAndSpecifyBehavior allows you specifying the action to be taken on the next pop up window as a first parameter (accept or dismiss). This action gives you more control by its ability to provide timeout and polling interval for the expected condition to be achieved.

ClickAndWait

Instead of using this action, we recommend you dividing it into two steps; Click and WaitForExistence or WaitForVisibility (element based). These actions give you more control by its ability to provide timeout and polling interval for the expected condition to be achieved.

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

SelectItemAndWait

This action can be divided into two different steps for better performance and consistency. We recommend you using SelectItems and followed by WaitForExistence or WaitForVisibility based on the next object you are going to work on.

WaitForPageToLoad

Instead of using this action, we recommend you using WaitForExistence or WaitForVisibility based on the next object you are going to work on. Developing 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. 

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. 

WaitForObject