Overview 

• Editor
  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
  The builder mode is the easiest one to follow, as it is 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.

Understanding Editor mode  

• Creating test steps becomes effortless with auto-completion suggestions for tasks, functions, and, with the right syntax, even for elements and variables. These suggestions enhance the testing process by providing quick and accurate input options.
                   
  
  
• Type the keyword, 'ui.' to see suggestions for the saved elements. This saves you time from manually inspecting webpages to identify locators for elements every time.
  
  

• Type '$' to see the saved variable list along with the built-in system variables.
  
  

Note: Elements and variables created for a particular project can only be used for test cases inside that project.

Understanding Builder mode  

The builder mode simplifies the test case creation process. Using the same task panel, you can either drag and drop the desired tasks or double-click them to the test editor.

• The panel to the right of the test editor lists the arguments for the selected task and supplies the required values to them.
  
  

• The slider pop up helps fill in the arguments for the tasks. It provides access to the pre-saved Elements, Variables, Functions, and Files. You can either type in the arguments inside the set expression input field using the right syntax or choose the required arguments from the four entities. 

Note:

• You can reorder tasks to change the execution order. Drag and drop the required task to the required position in the editor.
  

1. The selected task is inserted into the test editor, based on the current position of the cursor before the drag and drop or double-click actions.
   

Set Expression inside Builder Mode   

1. Drag and drop the task Open URL to the test editor. There are two parameters that have to be filled: URL and Window Type. As you click on the space allocated for the URL, the set expression input field gets accessed.

2. From the four entities, click Variables. Choose the required variable for the task from the Global Variable section. Click Done.

3. Next, click the Window Type and specify them using the drop-down menu: Same Window, New Tab, and New Window.

 Edit, Delete, and Comment 

• To remove the task from the test case use the trash icon.
      

• To remove multiple test steps, hover over the test step you want to delete, then select the checkboxes for all the test steps you wish to remove. Click Delete.
  
  

• Similarly, to comment test steps, check the box you wish to comment on and click Comment. Do the same to uncomment on the test steps as well.

Common actions inside Editor and Builder modes

• Version ( ) tracks and manages changes made to test cases or functions over time, ensuring version control and easy restore, if needed.

• Using the Edit option ( ), you can easily edit the test case details, such as test case name, link name, associated module, and the description.

Note: If the test case was marked as a function, it can't be converted back to a test case. The same applies when a test case is created.

• Manual View () is used to create test cases that allows users to create, organize, and execute test cases manually, based on predefined steps and expected outcomes.

• Suites () allows you to group test cases together, based on a specific testing objective or scenario.

• Record () captures the user interactions (element locators) and actions to automate the test case creation.

• A single test case is created for testing requirements of different platforms. Use the platform switch drop-down () to choose between the platforms: web, Android, iOS, and API.

• Use the refer elements () option to copy or refer the existing elements. To save new locators as elements, click +Add. Learn more.

• The test case status indicates whether they are in draft or in ready state. For the test cases to be executed under a test plan, they need to be in the ready state. Use the drop-down () to mark a test case or a function ready. Learn more.

• Run initiates live test preview for the test cases or functions to analyze and debug, if required. Customize your preferred configuration using the drop-down () to execute the test cases or functions.

Note: For test cases as functions, the actions are limited. They have access to Versions, Edit, Recorder, Refer Elements, and Switch Platform options, as well as run customization.

1. Web testing using Builder or Editor mode