Table of Contents

1. What is Data-driven testing?

Data-driven testing (DDT) is a term used in the testing of computer software to describe testing done using a table of conditions directly as test inputs and verifiable outputs as well as the process where test environment settings and control are not hard-coded.

It is the creation of test scripts to run together with the related data sets in a framework. The framework provides re-usable test logic to reduce maintenance and improve test coverage. Input and result (test criteria) data values can be stored in one or more central data sources or databases, the actual format and organization can be implementation specific. In the simplest form, the tester supplies the inputs from a row in the table and expects the outputs which occur in the same row. The table typically contains values which correspond to boundary or partition input spaces. In the control methodology, test configuration is “read” from a database that can be any of the below data files.

  • Datapools
  • Excel files
  • ADO objects
  • CSV filesODBC sources

Data Driven Testing can be best understood by the following diagram:

Data Driven Testing

2. Data-driven testing approach with Katalon Studio

Katalon Studio supports data-driven testing which allows users to define data sets and execute test scripts that use these data sets.

This tutorial will provide you a simple example on how to create an automation test case and execute it multiple times using different sets of data.

Given a sample test case whose scenario is as below:

Open the login page of the Katalon demo AUT website (http://demoaut.katalon.com/profile.php#login)

Login using three different accounts

Validate if the login is success

Close the browser

You can use the following steps to automate the above test scenario:

1. Create a new test case and proceed to generate the steps to:

Access http://demoaut.katalon.com/profile.php#login

Enter username/password

Click Login

Validate if the Appointment page is displayed Katalon demo

You can utilize the Web Record function to quickly generate test steps. Refer to this guide for more details on the Record & Playback feature of Katalon Studio.

2. The generated test case should be similar to the following: Katalon test case

You can see that the input values for username and password are hard-coded as what you typed during recording (in this case it’s admin/abc123). In order to run this script multiple times using different accounts, you need to parameterize these values. Please continue to the next step.

  1. Switch to the Variables tab of the test case and create two variables named ‘demo_usn’ and ‘demo_pwd’.

Katalon variables

  1. Switch back to the Manual view of the test case and set those two variables as inputs for the username/password fields.

Katalon manual view

Now that you have done the necessary steps to parameterize the required fields for login, proceed to the next steps to prepare data for execution.

  1. Create a data file in Katalon to have a dataset containing three login accounts. You can generate data file from sources such as Excel, CSV, Database etc…. Refer to Manage Test Data for more details on how to create test data from different sources. The following example shows the internal data file with three login accounts for http://demoaut.katalon.com (note that only ‘John Doe’ is valid):

Katalon data file

Data-driven tests execution

From here you can apply Data-driven using two methods, either using Test Suites or Loop statement in Test Scripts.

A. Execution from test suites

  1. Next, create a test suite to execute the test case using the defined dataset.

Create a test suite

  1. Expand the Data Binding section, add the created data file to the Test Data section and proceed to bind the two variables ‘demo_usr’ and ‘demo_pwd’ to the respective columns of the data file. You may refer to Data for test execution for more details about variable binding.

Katalon test data

  1. Finally, you can run the test suite, and your login test case will be executed three times using the accounts defined in the test data file.

B. Execute from a test case

  1. We can also implement Data-driven tests in a test case. Just create a new test case and switch to Script Mode. To iterate tests with multiple sets of data, we need to use FOR statement and call the test data objects. Copy and paste below code:
import com.kms.katalon.core.testdata.InternalData
 
InternalData data = findTestData("Demo_Account")
 
for (def index : (0..data.getRowNumbers() - 1)) {
    WebUI.openBrowser('')
    
    WebUI.navigateToUrl('http://demoaut.katalon.com/profile.php')
    
    WebUI.setText(findTestObject('Page_Login/txt_UserName'), data.internallyGetValue("demo_usn", index))
    
    WebUI.setText(findTestObject('Page_Login/txt_Password'), data.internallyGetValue("demo_pwd", index))
    
    WebUI.click(findTestObject('Page_Login/btn_Login'))
    
    WebUI.verifyElementPresent(findTestObject('Page_CuraHomepage/btn_MakeAppointment'), 0)
    
    WebUI.closeBrowser()
}

KatalonTutorial-DataDrivenTests.groovy hosted with by GitHub

Where:

  • Import InternalData class from Katalon built in library and define data variable to locate test data table
  • For statement to loop through all row of test data table which indicates how many times the test case will run
  • To get a row value in test data table, use getRowNumbers() method syntax. For example:

Username field: data.internallyGetValue(“demo_usn”, index)

Password field:  data.internallyGetValue(“demo_pwd”, index)\

  1. When you done in Scripts view, switch back to Manual view, the test case will look as the following screenshot:

Katalon script view

  1. Finally, you can run the test case, and your login test case will be executed three times using the accounts defined in the test data file.

Congratulations! You now understand how to approach Data-driven testing with Katalon Studio. To kickstart your web automation testing project, please refer to A sample web automation test project, a step by step tutorial that helps you start working on your testing project easily.

How to use synchronization commands while recording
How to use synchronization commands while recording
Previous Article
The Top 3 Gartner’s Latest Findings On The Software Testing Industry In 2020
The Top 3 Gartner’s Latest Findings On The Software Testing Industry In 2020
Next Article

Similar Articles

Feedback