The Run Summary page contains everything you need to know about the test(s) you ran: how many ran in total, on what platforms, and how many passed and/or failed.

Run ID and Run Name: the identification number associated with that particular run (not to be confused with a test's ID), as well as its name (in the example above, the run ID is #322656 and the run name is [Brant's Test - Petco])

Run state: A run is considered to have passed when all the tests contained within it pass. A run has failed if at least one test in it has failed. A run that was aborted may have been aborted by a user of the account or by Rainforest if there is a serious issue with the run.

Run started: The date and time (UTC) at which the run started.

Test result tabs: You can switch between three different views of tests within the run: All tests, tests that Failed, or tests that Passed. We will remember your selection for next time, so if you usually only want to review Failed tests, you'll see Failed tests for the next run summary you click into. The percentage values expressed in each will tell you what percentage of your tests passed or failed, rounded to display as whole numbers.

Failed platforms: This will be a summary of the platforms on which the test(s) ran and failed.

Failed steps: As above, you can see which step(s) the test(s) failed on, and get a preview of the step if you hover over the number.

Reviewed by: See an avatar of who on your team categorized the test failure. This helps teams with several users understand which failures have already been taken care of, and which ones haven't.

Failure category: If you use the failure categorization feature at test level, you will see the category with which the test was labeled, which user reviewed it, and when. If you hover over the failure category, you will see the comment left by the person on your team who reviewed it and jump into the test.

A note on a test that's been categorized with 'Bug' 

Failure category breakdown: Once you start categorizing your failed test results (e.g. Bug or Needs Refactor), you'll see a handy breakdown for the entire run. Use this to keep an accurate record of what happened during a run.

Failures categorized progress: Our toucan keeps track of all the test failures you've gone through or not. Once you've categorized everything, you'll see it in full color. Fun fact: toucans live in the canopy, meaning the upper layers of rainforest that provide it with coverage!

Categorization progress bar and failure category breakdown

Run Info: Using the arrow on the right side of the screen, you can show or hide the 'Run Info' menu. Run Info contains a summary of that run, including:

  • Cost of the run, as expressed in credits
  • User who started the run
  • Start time indicates when the run was triggered dynamically or triggered by a schedule
  • Duration is how long it took for all the results in the run to come back with a consensus on Passed or Failed
  • Environment is the environment you ran the tests against, set up through the Settings tab
  • Crowd is the group of people who executed it, i.e. Rainforest testers, Automation, or your on-premise testers added via Account & Settings

Rerun Failed Tests: This button allows for the option to rerun all the failed test in the given run once more. When you click on it the re-run will start automatically and inherit the same platform selection as the original run.

Did this answer your question?