🎉 Ends Today! Unlock up to 35% with our Black Friday lifetime discount before its gone! 🎉
The CheckView Step Editor enables users to define detailed test flows using a variety of Step Actions, categorized into general Form Actions and WooCommerce Actions. This guide outlines each action, its purpose, parameters, and pro tips to ensure your tests are efficient and reliable.
Step Name | Purpose | Parameters | Use Case | Pro Tip |
---|---|---|---|---|
Assert Element Is Not Present | Ensures an element is absent from the DOM. | Selector (CSS/XPath) iFrame Method | Often used to validate successful deletion, redirection, or UI changes (e.g., modal dismissed). | Useful after destructive actions like removing an item or closing a component. |
Assert Element Is Not Visible | Confirms that an element is not visible to the user. | Selector (CSS/XPath) iFrame Method | Ideal for verifying that a success message, error notice, or product image has properly loaded. | Use in combination with scroll actions if the element might be off-screen. |
Assert Element Is Present | Verifies that an element exists in the DOM, regardless of user visibility. | Selector (CSS/XPath) iFrame Method | Useful for checking that a dynamic element has been rendered after an action like form submission or AJAX load. | Use when when confirming that hidden input fields or background elements are added correctly. |
Assert Element Is Visible | Confirms that an element is visible on the page to the user. | Selector (CSS/XPath) iFrame Method | Useful for a collapsed accordion, modal overlay, or hidden tab content. | For hidden elements, use Assert Element Is Present instead. |
Assert Element Text Contains | Checks if an element’s text contains a specific value. | Selector (CSS/XPath) Value iFrame Method | Helpful when the target content is part of a longer sentence or includes dynamic labels (e.g., “Estimated delivery: May 14–17”). | Use for headings, notifications, or descriptions where the value may vary slightly but should always include a key phrase. |
Assert Element Text Does Not Contain | Confirms that an element’s text does not contain a specific value. | Selector (CSS/XPath) Value iFrame Method | Commonly used to check that warnings, errors, or unwanted content are absent. | Great for validating clean success states. |
Assert Element Text Does Not Equal | Confirms that an element’s text does not match a specific value. | Selector (CSS/XPath/RegEx) Value iFrame Method | Useful when verifying that an error message was cleared or a field’s value changed. | Confirm proper user state transitions, like switching from “Pending” to “Approved.” |
Assert Element Text Equals | Validates that an element’s text matches a specific value. | Selector (CSS/XPath/RegEx) Value iFrame Method | Often used for status messages, pricing fields, or form responses. | Use RegEx for dynamic values like dynamic shipping rates that may result in a range of dollar rates. |
Assert Email Received in Test Inbox | Verifies that a test email is received in the CheckView test inbox. | None, but requires the use of {{TEST_EMAIL_ADDRESS}} to redirect email confirmations to CheckView. | Essential for workflows involving email confirmations. | Only use with officially supported form plugins as unsupported setups will cause test failures. |
Assert Form Submitted | Validates that form submission data is successfully entered in the form plugin’s database. | None | Works exclusively with officially supported form plugins. | Avoid using this step for unsupported plugins as it will cause test failures. |
Assert Order Placed | Validates that order submission data is successfully entered in the WooCommerce orders database. | None | Works exclusively with WooCommerce. | Avoid using this step for unsupported e-commerce plugins as it will cause test failures. |
Assert Product in Cart | Validates that the selected product has been successfully added to the WooCommerce cart. | None | Works exclusively with WooCommerce. | Avoid using this step for unsupported e-commerce plugins as it will cause test failures. |
Assign | Inputs a value into a text or textarea field. | Selector (CSS/XPath) Value iFrame Method | Essential for filling out any forms with text or textarea fields. | Validate selectors and input values to avoid errors. |
Check | Checks a checkbox or radio button. | Selector (CSS/XPath) iFrame Method | Useful for accepting terms and conditions, opting into communications, or choosing a payment or shipping option. | If this fails, try replacing it with a Click action instead. |
Click | Performs a left-click on an element. | Selector (CSS/XPath) Position X (optional) Position Y (optional) iFrame Method | Common for buttons, links, and other interactive elements. | Utilize the Position X and Position Y (in pixels) to set a custom click position based on the selected element. |
Go to URL | Directs the CheckView bot to visit a specified URL. | URL (required): The target page to visit. | Typically the first step in a test flow but can also navigate to a new page mid-test. | Always use full URLs to avoid errors caused by relative paths. |
Hover | Directs the CheckView bot to hover over a specific element on the page. | Selector (CSS/XPath) iFrame Method | Commonly used for triggering hover-dependent elements like dropdown menus, tooltips, or hover-activated buttons. | Consider adding a short pause before this step if timing issues occur. |
Pause | Instructs the bot to wait for a specified time. | Duration (milliseconds): e.g., 2000 (2 seconds). | Useful for giving dynamic elements time to load before proceeding. | Avoid overusing pauses and combine with assertions for better test optimization. |
Press Key | Simulates keyboard key presses. | Key (e.g., Backspace, Enter) How many times? (optional). | Useful for troubleshooting problematic UI fields. | Combine with the Assign action to handle complex input scenarios like formatted phone number fields. |
Refresh | Reloads the current browser tab. | None. | Useful for resetting the session state, reloading dynamic content, or testing how a page behaves when revisited. | Use sparingly to avoid slowing down test execution. |
Scroll Around the Page | Scrolls the entire page from top to bottom and back up. | None. | Useful for ensuring that scroll-triggered elements (e.g., animations, image loading, infinite scroll content) are fully activated before continuing the test flow. | Ideal to place early in flows where content is loaded progressively or depends on scroll visibility. |
Scroll to Element | Scrolls the browser viewport to bring a specific element into view. | Selector (CSS/XPath) iFrame Method | Useful for triggering lazy-loaded content, revealing hidden sections, or ensuring that an element is in view before interaction (such as clicking or asserting visibility). | Pair with an assertion or interaction step when needed. |
Select | Chooses a specific value in a dropdown field (not a dropdown mega menu). | Selector (CSS/XPath) Value iFrame Method | Used to select a specific option from a dropdown menu, particularly in forms where users choose from predefined values. | Use exact values from the dropdown including capitalization. Further, if the select field value is not equal to its label, the Assert Form Submitted will fail. |
Uncheck | Unchecks a checkbox or radio button. | Selector (CSS/XPath) iFrame Method | This is useful in testing opt-out flows or when verifying how a system reacts when a user disables a previously selected option. | If the standard Uncheck action fails, try using a Click action instead. |