Rainforest Tests: Content Matching

Decrease test brittleness and maintenance with Content Matching.

📘

Rainforest vs. Rainforest Classic

Rainforest Automation and RFA are now Rainforest tests.

  • Rainforest Tests - Quickly capture UI element with screenshots
  • Rainforest Tests provide easy and efficient test writing for desktop applications. Test execution may be done via Automation Service, Tester Community or On-Premise Testers.

Plain English tests are now Rainforest Classic tests.

  • Rainforest Classic tests - Detail your test case line by line
  • Rainforest Classic tests allow you to write instructions via a free-form English testing writing interface. Tests may be run on desktop applications, mobile browsers, and mobile applications. Test execution is done via the Tester Community or On-Premise Testers.

Overivew

Content Matching provides a secondary layer for comparing elements by specifically evaluating text content in addition to a strict visual comparison. Using Content Matching allows more control over how strictly elements are evaluated. Proper use will ensure that appropriate evaluations are being done, reducing false failures and reduce test maintenance efforts. Content Matching is very helpful when your tests are being run using Automation Services.

This means in scenarios where a test might fail because of superficial changes such as a new font or font size, could pass if its text content remained the same.

When to use Content Matching?

Use Content Matching when the text content of the image is important, but other items such as shape or size are not.

Example:
The button on the left was captured from the previous UI, the button on the right is an updated version. They have different colors and shapes but the context is the same.

If Content Matching is enabled, tests will pass as Buy Now will be detected even though the visual styling is no longer an exact match.

This is useful when the QA strategy is focused on testing implicit functionality over strict appearance. The test won't fail due to small non-critical changes.

In test cases where Content Matching is not enabled, the updated button would result in a test failure as there isn't an exact match to the initial button.

Not using Content Matching is a perfectly acceptable practice, and is encouraged if the team values very rigid tests or if the update is UX based and the purpose is to confirm that all elements have been properly updated.

Can Content Matching be turned on and off?

Content Matching may be turned on and off at the individual element level. This can be done for buttons, headers, various amounts of text.

Rainforest will automatically determine if Content Matching is feasible for the selected element. However, if it is feasible for an element, you may turn it off if you so chose. Additionally, it may be turned back on for the specific element at will if needed.

In the following example, when the "Try for free" was selected, Rainforest determined that Content Matching could be used. However, it can set it so it does not use Content Matching. If you change your mind, it can be switched on.

No text to evaluate

No valid text content could be found
If there is not enough text to evaluate, Content Matching will not be available. This will happen with graphics, logos etc., and other elements that don't have discernible text. In this instance, Content Matching will not be used and there is not an option to engage it. Our detection logic will continue to improve and cover a wider range of cases. If you believe however that there is an issue please let us know at [email protected].

Too much text to evaluate

The text content found was too detailed.
There is too much information to evaluate. In order to preserve accuracy, Content Matching works best with smaller chunks of text. In this instance, Content Matching will not be used and there is not an option to engage it.

Instead of capturing a large piece of the screen, try several smaller if that still satisfies your test case. If you believe however that there is an issue please let us know at [email protected].

🚧

Multiple lines of center-aligned text

Content Matching will not work if multiple lines (two or more) of center-aligned text are being evaluated. It is suggested that the image capture be reduced to a single line at a time for evaluation.

NOTE: Even though Content Matching looks like it is engaged, Content Matching will not actually be used.

If you have any questions, please feel free to reach out to us at [email protected] or through Intercom!

Updated 11 days ago


Rainforest Tests: Content Matching


Decrease test brittleness and maintenance with Content Matching.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.