Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Creating Test Cases Using Manual Mode With Katalon Studio

DZone's Guide to

Creating Test Cases Using Manual Mode With Katalon Studio

This tutorial will show you how to create automation test cases in manual mode of Katalon Studio, using keyword-driven testing.

· DevOps Zone
Free Resource

Learn more about how CareerBuilder was able to resolve customer issues 5x faster by using Scalyr, the fastest log management tool on the market. 

Katalon Studio supports keywords-driven testing, where test cases consist of keywords that represent actions of users on the AUT (Applications Under Test). This allows users with less experience in programming to easily generate automation tests. The below tutorial will give you step-by-step instructions in order to create an automation test case in manual mode.

To create a test case using script mode, see this article.

Given a sample test case with the following steps:

  • Open the browser
  • Navigate to a website
  • Click on a certain control
  • Validate if the control exists on the page
  • Close the browser

Follow these steps to automate the above test scenario in Manual view:

Select File > New > Test Case from the main menu to create a test case. Provide the name for the new test case, then click OK.

Katalon Studio new test case dialog

Once a new test case is created, it is opened in Manual view. This view allows users to define steps for the test case easily with little programming skills required.

Katalon Studio Manual Mode

Select Add > Web UI Keyword from the command toolbar.

Web UI Keyword Katalon Studio

Select the Open Browser keyword. This keyword opens a browser and navigates to the specified URL if provided (the detail of a selected keyword is shown in the popup screen as shown below)

Open Browser Keyword Katalon Studio

Add the Navigate To Url keyword. This keyword navigates to a specified URL. Double click on the Input cell to provide additional data (parameters) for the keyword.

Provide additional data

The Input dialog is displayed as below. Each row represents one parameter.

Input dialog Katalon Studio

Where:

Field Description
No The parameter order for the selected keyword.
Param Name The name of the parameter.
Param Type The data type of the parameter (e.g. String,Variable or Test Data Value…)
Value Type The type of input value (e.g. String, Variable or Test Data Value…)
Value The input value for this parameter.
Input value varies depending on the specified Value Type. Refer to Value Types in Katalon for more details.

For now, enter the URL of Katalon demo AUT (http://demoaut.katalon.com) into the Value column then click OK.

Add the Click keyword. This keyword represents a click action on a given object. You need to associate this keyword to an object. Double click on the Object cell to open the Test Object Input dialog.

click keyword Katalon Studio

All captured objects in Object Repository are displayed in the Test Object Input dialog (Refer to Spy Object for details regarding how to capture objects). Select your object then click OK.

Test Object Input Dialog

Add the Verify Element Present keyword. This keyword validates if a certain object is displayed on the executing browser. Similar to the previous step, you need to associate this keyword with an object.

Verify element present

Add the Close Browser keyword and save your test case.

Close Browser Keyword Katalon Studio

Click on Run in the main toolbar to execute the test case.

Execute test Katalon Studio

Katalon Studio should be able to execute all of the steps specified in the test case. Test execution results are shown in Log Viewer as below:

Log view dialog Katalon Studio

For more tutorials, please visit the Katalon Studio Resources Center!

Find out more about how Scalyr built a proprietary database that does not use text indexing for their log management tool.

Topics:
automated testing ,test automation ,software testing ,manual testing ,katalon studio ,quality assurance ,devops

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}