Step 2. Identify the root cause
Before creating an issue in Jira based on a failure, it’s important to identify the root cause. Mabl reports failures and provides rich diagnostic data including context that uncovers the root cause as quickly as possible. This includes artifacts such as screenshots, HAR files, the DOM, and even step traces.
1. Examine the failed step.
2. Check for any changes using diagnostic information, like screenshots or the DOM snapshot.
3. Verify the cause. In this case, the element doesn’t appear in the DOM.