What does this page cover

Best practices

1. In test scenarios involving web services or applications with dynamic content, always use the Wait task after major steps such as page navigations or data-fetching actions to ensure that elements or components have fully loaded before moving forward. Rather than relying on fixed delays, configure the wait condition to check if a specific element is intractable. This approach improves test stability and avoids flakiness caused by premature interactions with partially loaded elements.
   
   
2. Scroll To can be used to bring elements into the visible viewport before interacting with them. Many UI elements won’t respond correctly if they’re off-screen or hidden behind sticky headers. Scrolling ensures reliable and consistent behavior in your test flows.
   
   
3. Avoid using Open URL repeatedly within the same test flow. This reloads the page and resets the context, which can break locators or slow down your test. Instead, use navigation tasks like Switch To for switching between sessions, tabs, or iframes, and use Browser Navigation (e.g., Back, Forward) to move within the same session when appropriate.
   
   
4. When automating form interactions, prefer using the Set Value task instead of using the Click task to focus input fields. It allows you to directly populate values without UI-driven clicks or typing, making your tests faster and less error-prone. Use Click only when triggering actions (e.g., Submit) or interacting with controls like checkboxes or dropdowns.
   
   
5. When you need to simulate real keyboard input, such astyping, using shortcuts, or navigating with the tab key, use tasks like Send Keys. Unlike Click, it mimics actual user behavior, making your tests more realistic for scenarios that rely on keyboard interaction. 
   

1. When test cases across modules perform similar flows like login or form fill, define the logic inside web tasks and organize it through functions, which are then reused across test cases within modules. 
   
   
2. For consistent session handling in your test cases, use cookie management tasks such as getcookies and setCookies. Capture and reuse session cookies to maintain authentication or user state across test cases. These tasks can be combined with built-in functions like IS_PREVIEW_RUN to fetch and set cookie values dynamically. For example, during a live preview, you might use locally stored cookies, while in a test plan, you can fetch and reuse cookies in runtime across test cases. This approach ensures seamless session persistence without hard coding, and promotes script modularity and environment adaptability.   
   

1. After any user interaction, such as logging in, submitting a form, or navigating to a new page, it’s essential to verify that the UI responds as expected. For example, after a form is submitted, the application is expected to display the dashboard view. To confirm this, write verification scripts using assertion tasks that check for the presence of key dashboard elements. Whether you're checking text, visibility, selection states, or file downloads, assertions ensure your tests verify actual application behavior, not just execution.
   
   
2. Avoid using raw locators like full XPath strings in your test scripts. Instead, use logical identifiers (e.g., field labels or names). Let QEngine handle locator resolution to improve reliability and reduce maintenance. Learn more about element locator strategies
   
   
3. Use the Finally block for tasks that should always run, such as logging out, resetting state, or clearing test data, regardless of test success or failure. This ensures clean test environments for future runs.
   
   
4. In scenarios where certain steps might occasionally fail without impacting the overall test workflow, encapsulate them using a Continue On Error task. For example, if you're testing a form submission and the presence of an optional field isn't critical, you can validate it using this task. This approach helps handle optional UI elements or environment-dependent behaviors without triggering false test failures. 
   

Related links

1. ​Web tasks
2. Understanding cookie support in Zoho QEngine