Toolbars and Views
Since version 5.6
The main Toolbar contains the most common actions which you usually perform (e.g. creating test resources or executing automation tests).
|Save the current opened test artifact.|
|Save all opened test artifacts.|
Create new test artifacts. You can select these options by selecting from dropdownlist:
|Open Web Object Spy dialog for capturing elements on websites.|
|Open Mobile Object Spy dialog for capturing elements on mobile applications.|
|Open Web Record dialog for recording WebUI test cases.|
|Open Mobile Recorder dialog for recording Mobile test cases.|
Run the current open test case. You can select these options by selecting from dropdownlist:
Debug the current open test case. You can select these options by selecting from dropdownlist:
|Stop the current execution|
|Open Command Builder for generating commands for console execution|
Command for Git activities. You can select these options by selecting from dropdownlist (after enabling Git):
|Import test case from JIRA integrated account|
|Execution profile (testing environments) to be applied when run tests|
|Allowing you to search for help on Katalon Documentation and our Forum|
|If you have any further questions, you can also submit it in our Gitter channel. Katalon experts and users will try to help you as soon as possible.|
Tests Explorer View
The Tests Explorer view allows you to browse the structure of your projects and access all test artifacts quickly. Using the context menu on the view, you can create new artifacts, organize the view's items or drag and drop them to certain editor views if needed.
|Test Cases||List all test cases within current project|
|Object Repository||List all test objects of the current project|
|Test Suites||List all test suites and test suite collections of the current project|
|Data Files||List all test data of the current project|
|Checkpoints||List all checkpoints of the current project|
|Keywords||List all custom keywords of the current project|
|Reports||List all generated reports of the current project|
|Profiles||List all execution profiles of the current project|
|Include||Contains Cucumber Features File and Step Definitions|
Starting from Katalon Studio version 7.0.0, you can customize Tests Explorer by selecting Project > Settings > Explorer. By default, Tests Explorer displays all test artifacts; hence, uncheck the test artifacts you want to hide and click OK.
Keywords Browser View
The Keywords Browser view displays all available keywords supported by Katalon Studio. You can drag and drop the keywords here to the Test Case editor when scripting.
The editor is used to modify the detailed information of an object. Each test artifact has its own editor.
Test Case Editor
When you open a test case, its detailed information is shown in the editor that contains the following tabs:
- Manual tab
- Script tab
- Variables tab
- Integration tab
- Properties tab
The Manual tab displays the Manual view where the basic keyword-driven-configuration allows novice users to create automation tests effortlessly. Refer to Manual View for more details.
This tab displays the Script view where advanced users with programming background can modify test scripts easily using either Groovy or Java. Refer to Script View for more details.
The Variables tab shows all variables defined for the test case. Refer to Public Variables for more details.
Information regarding your test case integration with qTest is displayed in this tab. Refer to Integrate test case for more details.
General information about the test case is displayed in this tab.
- Description: Users can add or edit this field to provide detail information about a test case
- **Comment: **This field is read-only. The content is extracted and populated from Comment keyword in the test case. Business users can leverage comment field to involve in development process by providing the requirements. The example below shows the description of a test case that verify successful login and comment field shows the scenario written in BDD's Gherkin syntax.
Test Object Editor
When you open a test object, its detailed information including properties and object identification mechanism is displayed in the Test Object editor. Refer to Spy Object for more details.
Web Service Editor
RESTful Request Object Editor
When you open a RESTful request object, its detailed information including the resource URL, request methods, parameters... is displayed in the editor. Refer to RESTful for more details.
SOAP Request Object Editor
When you open a SOAP request object, its detailed information including the resource URL, request methods, parameters... is displayed in the editor. Refer to SOAP for more details.
Test Suite Editor
When you open a test suite, its detailed information is displayed in the Test Suite editor that contains the following tabs:
- Main tab
- Integration tab
The main tab displays basic information about the test suite such as the test cases to be executed, the execution mechanism and data binding. Refer to Execute a test suite for more details.
Information regarding your test suite integration with qTest is displayed in this tab. Refer to Integrate test suite for more details.
Test Suite Collection Editor
Basically, a Test Suite Collection contains a set of test suites to allow users to execute test suites together. Refer to Test suite collection for more details.
Data File Editor
When you open a data file, its detailed information including the data source and preview data set... is displayed in the editor. Refer to Manage Test Data for more details.
If the test data is from an Excel file:
If the test data is from a CSV file:
If the test data is defined internally inside your test project:
If the test data is from a database query:
When you open a checkpoint, its detailed information including the data source and its taken snapshot... is displayed in the editor. Refer to Manage Checkpoints for more details.
- If the data source is from an Excel file:
- If the data source is from a CSV file:
- If the data source is from a database:
- If the data source is from existing test data:
When you open a custom keyword, its content is displayed in the scripting editor. This scripting editor is similar to the Script view of test cases where you can define new custom keywords easily using Groovy or Java. Refer to Introduction to Custom Keywords for more details.
Global Variables View
The Global Variables view allows you to browse the list of available global variables defined in your project. Refer to Global Variables for more details.
Job Progress View
The Job Progress view allows you to see the progress of executing test cases and test suites.
The Problems view shows errors and warning messages raised when you are setting up a project or designing the test case, test suite, test object or test data.
The messages displayed in the Problems view can be configured via the drop-down menu of this view.
The Console view shows the system logs of all run-time activities performed while the automation test is being executed. The console output generated from test scripts is also displayed here.
Log Viewer View
The Log Viewer view shows the real-time report/log of the test execution. Refer to View Execution Log for more details.
The Search view shows the search results from the search function. You can double-click on a search entry to navigate to the corresponding position in the editor.
The Report view allows you to view detailed information of a completed test execution for a certain test suite. Refer to Test Suite Report for more details.
Test Suite Collection Report view
The Test Suite Collection Report view allows you to view detailed information of a completed test execution for a certain test suite collection. Refer to Test Suite Collection Report for more details.