Solving Common Issues – Wait-Time
Solving Common Issues – Wait-Time
Learn how to use the Katalon Studio test automation framework to solve certain failures that can occur in automated testing due to the use of wait.
Join the DZone community and get the full member experience.Join For Free
DevOps involves integrating development, testing, deployment and release cycles into a collaborative process. Learn more about the 4 steps to an effective DevSecOps infrastructure.
Automation execution usually does not carry out exactly as scripted due to many factors involved during execution such as network stability, internet bandwidth, the performance of the AUT, and the performance of the executing computer. This article will guide users through leveraging delayed time to handle such situations.
What Is Wait?
Using delayed time is a common practice in test automation scripts to create a pause in-between automation steps as you wait for web elements to load or for the AUT to respond.
Here are some examples of test failure due to insufficient waiting time:
- False Fail: One of the most common failures is when a script fails due to waiting on the application. It is often caused by network latency, delayed database requests, or simply because the system needs more time to process and respond to the request.
- Targeted element not present on the page: This kind of failure occurs when waiting for elements to be displayed or rendered in the browser. The application may be up and running but certain elements may not be loaded, thus causing test scripts to fail.
How to Address Failures Related to Wait
Katalon provides keywords dedicated to delay explicitly. You can use the following options to address the situation:
- Wait For Page Load – This logic will wait for a page to completely load before running a step in your script.
- Wait For Element Present – It happens sometimes that web elements take a longer time to appear on the page. This keyword pauses execution until the targeted element appears on the page. Once the element appears, the test continues to execute the next action.
- Global variable – This variable has the global scope, meaning that it is visible throughout the program. Thus, you can use this variable in your test scripts according to the response time of your web application. You may consider defining 3 kinds of global variables in your test scripts, for short, medium, and long waits.
For example, the script below shows the usage of a global variable and the use of Katalon Studio built-in keyword Wait For Element Present to deliberately wait for a specific test element.
Figure 1: Katalon Studio Test Script.
import com.kms.katalon.core.checkpoint.Checkpoint as Checkpoint
import com.kms.katalon.core.checkpoint.CheckpointFactory as CheckpointFactory
import com.kms.katalon.core.mobile.keyword.MobileBuiltInKeywords as MobileBuiltInKeywords
import com.kms.katalon.core.model.FailureHandling as FailureHandling
import com.kms.katalon.core.testcase.TestCase as TestCase
import com.kms.katalon.core.testcase.TestCaseFactory as TestCaseFactory
import com.kms.katalon.core.testdata.TestData as TestData
import com.kms.katalon.core.testdata.TestDataFactory as TestDataFactory
import com.kms.katalon.core.testobject.ObjectRepository as ObjectRepository
import com.kms.katalon.core.testobject.TestObject as TestObject
import com.kms.katalon.core.webservice.keyword.WSBuiltInKeywords as WSBuiltInKeywords
import com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords as WebUiBuiltInKeywords
import internal.GlobalVariable as GlobalVariable
import com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords as WebUI
import com.kms.katalon.core.mobile.keyword.MobileBuiltInKeywords as Mobile
import com.kms.katalon.core.webservice.keyword.WSBuiltInKeywords as WS
'Open browser and navigate to Katalon site'
'Wait for Katalon Studio page to load with wait used as Global Variable'
'Click on \'Login\' button to navigate to Login page'
'Click on \'Login\' button to login'
'Wait for failed message to be present'
When to Use Wait Commands
Quite often test execution get failed due to the exceptions such as ‘NoSuchElementException‘, ‘ElementNotFoundException‘, ‘ElementNotVisibleException‘. In order to handle these exceptions, conditional Synchronization has to be implemented. Katalon Studio supports many built in “Wait for….” keywords to deal with such exceptions. For example:
|Wait For Element Present||Wait for the given element to present (appear) within the given time in seconds.|
|Wait For Element Visible||Wait until the given web element is visible within timeout.|
|Wait For Alert||Wait for a browser’s alert to present.|
|Wait for Element Clickable||Wait for the given element to be clickable within the given time in seconds.|
For more tutorials about automation testing tools, please visit Katalon Tutorials.
Opinions expressed by DZone contributors are their own.