Resolve a blocker Learn how to resolve a blocker using Blocker Remediation, so you can execute the test run successfully. What is a blocker? In test steps that use the touch action, the user interface (UI) of an element often changes across multiple devices. If the difference is significant, the AI will raise a blocker and is unable to select the element. This situation can disrupt revisits on different devices due to difficulties in managing element appearance across various screen ratios, such as 18:9, 17:9, and 16:9. However, you can easily resolve these issues in Test Management without scripting by using Blocker Remediation. Resolve a blocker When a blocker is encountered, the Test Run Results page will display the Needs Actions status: Select the Needs Actions status to go to the Session Explorer page. In the Session Timeline, the step with the blocker is marked with a red icon. Select this icon, then choose Resolve Blocker. The Blocker Remediation popup appears: The following tools will help you remediate: Navigation buttons to switch between test steps. The original screenshot of the baseline session is shown alongside the screenshot of the revisit session. The selected element is highlighted in the Baseline screenshot. Hover the mouse over the Revisit screenshot to highlight the element closest to it. To remediate a test step: Navigate to the desired test step using the navigation buttons. You can only navigate to test steps that use the touch action Select an element from the Revisit screenshot. When finished, select Submit. You can only resolve blocker for one test step in one revisit session. If a test run has many test steps that require Blocker Remediation, rerun the test run again, resolve the next blocker, and repeat until there is no blocker left. Once you submit, you cannot resolve the blocker for the current session again. Proceed with caution. After submitting, the submitted test step will be set as the new baseline when running the same test case on any device with the same model and OS version. To verify, rerun the test run again on any device with the same model and OS version. Notes Blocker Remediation does not work in the following cases: The element does not involve a touch action, such as swiping or scrolling. The element’s position and appearance is not static, such as: Floating element. Element that can hide or display based on user behavior (playback button in videos player). Element with animations. The element cannot be identified via Appium Inspector, such as label or xPath, and requires touching on an exact coordinate on the screen. For example, an object in a mobile game. The element is outside the current view and requires additional actions to be visible, such as scrolling vertically more than 5 pages, scrolling horizontally, or swiping left/right. The AI can automatically find the element by scrolling vertically within a 5-page range. The element is not selectable due to a bug. An in-app pop-up (that did not appear in the baseline session) blocks the element from being selected. System pop-ups, such as software update notices, are automatically dismissed by the AI.