Note: The website, Zylker Watches, is a test demonstration store. If visiting the link, no orders will be fulfilled from this store.

• Faster test case creation: Testers can create automated tests quickly and easily without needing to write code manually. This saves time and effort and enables testers to focus on other aspects of testing.

• Accuracy: It ensures the test is executed the same way every time, leading to more accurate and reliable results.

• Reusability: Recorded test cases can be reused multiple times, reducing the need to create new tests for similar functionality.

• Scalability: Testers can create automated tests that can be executed across multiple platforms and configurations, making it easier to test large or complex systems.

• Clarity: It can make it easier for others to understand what is being tested, as they can see the exact steps and inputs used in the test case.

• Consistency: It ensures the same steps are followed each time the test is executed, maintaining consistency across different test runs and environments.

• Maintenance: This can help simplify maintenance and updates to automated tests, as changes to the system under test can be easily captured and incorporated into the test script. It also records the interacted elements, which are then saved along with its page name.

 Installation setup for Zoho QEngine recorder 

1. To start recording test cases, you need to install the Zoho QEngine extension for your browser. Click Record to find the extension file to be installed. For Chrome, the pop-up below will be shown when you try to record a test case.
   
   
   

Note: The extension is currently supported for Chrome and Firefox. Make sure you are logged into either of the two to use the recorder.

2. Click Install Extension. This navigates you to the Chrome Web Store where you can read more about its features, user reviews, and ratings. To install the extension, click Add to Chrome in the top-right corner of the page.
   
   
   

3. A pop-up window will appear to confirm you want to install the extension. Click Add extension to confirm. The extension will start to download and install automatically. Depending on the size of the extension, this may take a few seconds or a few minutes.
   
   

4. Once the installation is complete, you'll see a confirmation message at the top-right of the browser window. The extension's icon will also appear on the toolbar to the right of the address bar. 
   
   
   
   

Recording a test case 

1. Click Record. Enter the URL of the application to be tested in the format https://www.example.com. Then, click Start.
   
   

Note: The recorder will only check the authenticity of the URL. The URL given can have anchor links to the page, query params, and more.

2. The recorder opens a new browser window with the requested URL ready to capture the actions. While recording, you'll notice each interaction with the page will be recorded as steps.
   
   

3. The focus element pop-up shows the locator tags of every element you interact with. The settings icon lets you perform a few selected browser actions with these elements.
   
   
   

4. If you want to pause in between the recording, click on the floating pause/stop button. For example, if you wish to re-record a test case without losing the previously recorded steps, you can pause the recording and then resume it once you reach the page to be recorded.
   
   
   

5. Once you are done, you can stop the recording.
   
   You'll be taken back to the test case editor. Elements are recorded along with their webpage name. All the elements you interacted with during the recording are listed for selection. Previously saved elements will be listed as "Existing Locators" and the newly saved elements, irrespective of their webpage name, will be listed as "New Locators."
   

6. Choose the required elements, name them appropriately, and select which type of locator you would want for that element. To learn more about them, see the page, elements.
   
   

Note: If the test case already has test scripts, you can either opt to continue on the existing one or start fresh. If you click Yes, the next line of script will start from where you last stopped.

 

 

However, if you click No, I want a clean session, the previous script will be removed. If you want the replaced script, it can be viewed or restored from the previous version(s).

7. Once you finish recording on the desired platform, the test case will be saved by default.

Web testing best practices

• Variables can be used to avoid repeatedly entering values that are found in input fields of a form or login, such as name, username, password, and the like.

• Avoid hard coding locators inside test cases. Instead, save them during interactions with the page for maintenance and better debugging.

• Creating functions can replace a test script with repetitive actions performed within a web application or website.

• It is recommended to optimize tasks for writing effective test cases. This means there are multiple ways to achieve the same functionality with different tasks. For instance, the "wait" function has two syntax options. The first one waits for a specific duration, irrespective of the element being present or not in the Document Object Model. In contrast, the other "wait" option waits with respect to the element being found in the DOM. By opting for the latter option, the execution time can be reduced.

• The test case should be associated with the right module. For example, a user accidentally associated a test case meant to test the payment gateway with a module designed to test the search functionality of a webstore. Once the testing was complete, the payment gateway module still had issues.