Best Practices

Learn best practices for working with Automation Service results.

Reviewing Automation Results at the Step Level.

Step details provide additional information on how a match was or wasn’t made. We include information about the time and the environment. Test information and actions are also available.

Automation Service failures are due to significant changes in the image that the test step is looking for an evaluating. If an image isn't found, Text Matching is used to find a match, if text matching is applicable to the step. Rainforest will highlight a step that doesn't pass image comparison and text matching. However you can view all steps and see how the element was evaluated.

For passed steps

  1. Click on Investigate Action to see details on how the element was evaluated
  2. Review the information provided and see if the element was image matched or text matched.
  3. See How to Debug Automation Results for additional details.

For failed steps

  1. Click on Investigate Action to view details of a failed test step.
  2. Review the information provided and see how the element was evaluated.
  3. See How to Debug Automation Results for additional details.

Action Failed
An Action Failed error occurs when we can’t confidently match the intended element either visually or with text matching (if enabled). In this case, the test step fails and as a result, the test itself fails as well.

Categorizing Failures

Failure categorization ensures you get the most information about your test suite’s health. It also helps confirm that the correct action is being taken when a test fails. For more information, see How to Categorize Failures.


If you have any questions, reach out to us at [email protected].


Related Articles & Links