Weekly QA Visibility Report

Learn how to improve the performance of your test suites.

The “Weekly QA Visibility” report sheds light on how critical metrics in your test suite changed over the past several weeks. It’s intended to be a conversation starter for your team. Among other things, it can help answer questions such as:

  • Is everything okay?
  • Was something supposed to happen—and didn’t?
  • Does your QA process need tweaking to achieve the metrics you want to see?

The report covers test creation and maintenance history, test execution, and failure categorization.

A test creation and maintenance metrics example.A test creation and maintenance metrics example.

A test creation and maintenance metrics example.

A failure categorization metrics example.A failure categorization metrics example.

A failure categorization metrics example.

Report Highlights Examples

  1. The number of tests created didn’t go up very much in the past few weeks, even though you released new core features last week.
  2. The number of tests that ran last week went down considerably, even though you had several new releases.
  3. No bugs were marked as “caught,” even though the team discussed a recent P1 that Rainforest caught.

In addition to the visual bar charts, there’s also a table that shows you how these data points changed during the past two weeks.

An example of numerical changes in test suite data points.An example of numerical changes in test suite data points.

An example of numerical changes in test suite data points.

Receiving the Report via Email

You can receive this report automatically by updating your email preferences. For more information, see Profile Settings.


If you have any questions, reach out to us at [email protected] or via the chat bubble below.

Updated about a month ago


Related Articles & Links

Profile Settings

Weekly QA Visibility Report


Learn how to improve the performance of your test suites.

Suggested Edits are limited on API Reference Pages

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