Web testing using Builder or Editor mode
Overview
Test cases are steps to perform an action. They contain a series of inputs to be provided, as well as expected outcomes to be validated for an action or a function that has to be tested.
Zoho QEngine offers the flexibility to create test cases for various platforms, such as web browser, Android, iOS, and API. For testing on the web browser platform, users can either choose to record or write using the builder or editor mode. These modes are designed in such a way that the user can choose between task blocks or scripting to create their test flow.
- Editor mode
The editor mode is written on a “pro-code” basis for those automation experts who prefers to script directly. It offers greater flexibility and control over test case scenarios, enabling users to create reusable and custom automation scripts.
- Builder mode
The builder mode is the easiest one to follow because it’s created on a “low-code” basis. Users can drag and drop the tasks onto the test editor, with each of them encapsulating the necessary functionality, eliminating the need for coding or writing detailed instructions manually.
Learn more on builder and editor modes.
Writing a test case
To begin writing a test case using either the editor or builder modes, first, you need to create a test case. Once the test case is created, follow the steps below.
Editor mode
- The editor mode is displayed by default. Write your test cases with the tasks using the auto-complete option, by double-clicking the tasks, or dragging and dropping them to the editor from the task panel.
- After adding the required task, provide the relevant parameters to them. The parameters can contain the following:
- Elements: Locators for the interacted elements can be set in two ways. The first method involves manually hard-coding the locators by enclosing it with double quotes (" ") after inspecting the relevant webpage, web, or mobile applications. For example, to use the locator inside the task Click, enclose it in double quotes: click ("#zs-guest-login")
Alternatively, testers can leverage the auto-complete feature by typing "ui." to access the list of created elements.Additionally, the Refer Elements option allows users to copy, edit, and create new elements. To copy or edit existing elements, select the webpage or application page name, and hover over the copy or edit icons for the required element. To create new elements, click +Add.
- Variables: To access the variables created, start typing in the format $<variable>. You can view the list of all global and environment variables in addition to the system variables that are present by default.
- Functions: The format of a function in a parameter should be like the format below:
<module_linkname>.<function_linkname>(<parameters>).
where,
<module_linkname> is the link name of the module under which the function is placed;
<function_linkname> is the link name of the function to be invoked;
<parameters> is the input values to be passed, if any.
Notes:
- Only functions that return a value can be used as parameters.
- Function arguments aren't mandatory. You can also add them later by editing the test case details of that function. Learn more.
- Files: Files are supported only for selected tasks. To access the saved files, type in the format files.<filename>.
- Click Save, to save all changes or edits to the test case.
Note: Clicking on any another button without saving will remove all of the changes made to the test case. Unless the edits or changes are saved, you can't replicate the test case to the builder mode.
Builder mode
- To start writing in builder, click Builder Mode.
- Drag and drop the required tasks from the task panel (on the left) to the editor.
- After adding the task, you need to provide the relevant parameters. Click on the argument placeholder on the right. The set expression pop-up contains an input field and provides the option to select the required elements, variables, files, or functions. The parameters can contain the following:
- Elements: Parameters for the interacted elements can be set in two ways. The first method involves manually hard-coding the locators by enclosing it with double quotes (" ") after inspecting the relevant webpage, web, or mobile applications. For example, to use the locator inside the task Click, enclose it in double quotes: click("#zs-guest-login")
Alternatively, testers can copy the required locators from the element option. Select the element name from the drop-down and choose the required locator. The locator gets auto-populated in the input field with the format: "ui.chrono_44.span".
Additionally, the Refer Elements option allows users to copy, edit, and create new elements. To copy or edit existing elements, select the webpage or application page name, and hover over the copy or edit icons for the required element. To create new elements, click +Add.
- Variables: The variable section includes a list of all global and environment variables, in addition to system variables that are present by default. Select the required variable or type in the format $<variable> inside the input field.
- Functions: Function can only be used as a parameter by using the call function task inside the required task. Call function is a drop-down in the case of builder mode. Select the desired function from the saved list of functions.
- Files: Uploaded files are accessible from the files section. Select the required file from the saved list of files.
- Once the required parameters are applied, click Done. To save these changes or edits to the test case, click Save.
Test cases are now created using the editor or builder modes. To preview their real-time results, configure run and see their executions to review and analyze their functionality and behavior. Once the test cases are created and tested for their real-time behavior, you have the option to add them into a test suite and test plan, allowing you to evaluate their interactions with other functionalities and enabling scheduled testing.