In addition to executing tests, Rainforest testers also provide valuable feedback to you to help improve the test itself and also provide feedback to the feature being tested.  The terms comments and feedback are used interchangeably.

How to find tester feedback

The Tester Comment Icon (blue speech bubble) and is shown on the Test, Run Summary and Test Results pages. It is shown for tests where a tester has left comment and feedback for your review.  

To see the actual feedback, select the test so you are advanced to the test page.  

Once in the Test page, click the icon at the top of the screen to view tester comments from the latest run or select the blue tester comment at the test specific test steps. These comments will show up to the right of the editor aligned with each corresponding step.

Selecting Show Tester Comments at top of Test page

Selecting Show Tester Comments at individual test step 

Note that Rainforest will only show tester feedback from the latest run alongside the test steps. To view feedback from prior runs, click on the ‘view comments history’ link.

Types of tester feedback

Testers will provide feedback for two specific reasons:

  • Bug Reports (reasoning for failed test)
  • Tester Feedback (suggestions for passed tests)

Bug reports

When a step can't be passed, testers will select No and fail the step. The tester will share a bug report to help you identify what went wrong with the application.

The Bug Report includes a constructive, helpful comment that explains why they had to fail the step. Please note that lengthy comments are not mandatory, and some testers may leave more detailed feedback than others.  

Tester Feedback (aka Suggest Improvement)

Yo'll also see Tester Comments on passed results.  This notes helpful feedback from the testers.

Testers may leave a tip about how your instruction could be phrased better, or something else they noticed while testing. We encourage testers to provide this type of feedback in addition to just answering the step with “YES” when appropriate.

Tester feedback usually concentrate on the following:

  • This step can be broken into multiple steps
    If step is asking them to do too many things in one step which can lead to confusion.  The step can be improved by splitting it into multiple steps
  • These instructions are hard to understand
    If the tests were written in specific jargon they don’t quite understand, or phrasing that could be clearer
  • The action you want me to do is not fully described
    Instructions omit certain actions that are too far of a leap for testers to responsibly infer, or perhaps a step was not fully written 
  • There was an unexpected pop-up in this step
    If testers experience a pop-up that wasn't included in the instructions
  • I see an additional problem that is not asked as part of the question
    Tester notices something else about your app, e.g. a typo in a part not mentioned in instructions. and they wish to bring it to your attention

While we recommend testers use this in certain situations, it is not mandatory. Regardless of if the tester chooses to leave a suggestion, they must follow your instruction to the best of their ability and answer Yes or No accordingly.

Should testers provide feedback, their report must includes a polite, helpful comment(s) explaining how the situation could be improved. Unless the tester’s comment was rude or unhelpful, you should never give the tester a poor rating for providing this type of feedback.

If you have any questions about testers or need to report a bad comment, please let our team know in as much detail as you can at

Did this answer your question?