Rule 3 Supporting Examples – Rainforest Support

Examples for Group 1: Pop-ups which indicate there is a bug

Report pop-ups like these, unless the customer specifically instructs you not to. Here are some examples of these types of pop-ups:

500 errors

An error message that appears for few seconds and then disappears

404 errors

Crashed browser

Microsoft Excel external error

“Uh oh. Something went wrong on our end. It’s not you, it’s us. Sorry about that”

Examples for Group 2: Pop-ups which don’t indicate a bug

Do not report pop-ups like these. Here are some examples of these types of pop-ups:

Side chat box

Connecting

Prompt to save password

Prompt to save credit card or similar info

Warning popups that don’t indicate a bug:

Screenshot_2020-05-25_at_9.53.25_AM.png

Forms that say valid info is required

Note: Sometimes forms show you a warning like this before you enter required information, like the one above. This is not a bug, and should not be reported. However, if you have entered the valid information required, and you still receive this message, you should report it as a bug with “No” and explain the issue.

Hostname conflicts:

A pop up asking you to subscribe to email updates, discounts, limited time offers, etc

Captcha message

Do you want to allow notifications from [this app]? (usually on mobile real devices)

Examples for Group 3: Pop-ups which may indicate a bug, but you aren't sure if this is the case

You should not report pop-ups like these. Alert the customer using “Suggest Improvements” category “There was an unexpected popup in this step”, or ignore completely if instructed to do so by the customer.

Note: While we recommend the use of Suggest Improvement in some cases like the following, it is not required. If you choose not to use SI, follow the instruction to the best of your ability and answer Yes or No accordingly.