Updates to how our testers should handle pop-ups on your application

A common encounter while navigating a site is a random pop-up or modal that prompts them to take a certain course of action. This article will outline how our testers manage these random pop-ups while testing with Rainforest.

Why do random pop-ups and modals have to be managed?

The answer is simple: our testers are trained to fail a test by answering 'No' to a test step whenever they encounter a pop-up or modal while going through a workflow that is not mentioned in the test instructions.

Over time, we have come to realize many sites that we QA often have pop-up modals that customers intentionally build into their site but that appear in random places. Due to how our testers are trained, they will fail tests if they encounter these purposeful pop-ups. To balance both sides of scale, we have come up with tester rules that we have found useful for managing these situations.

Pop-ups are divided to 3 groups:

(1) pop-ups that indicate a bug
(2) pop-ups that don’t indicate a bug
(3) pop-ups where it is not obvious whether they indicate a bug or not.

Testers will need to fail on pop-ups from group #1, to pass on pop-ups from group #2, and to add a step comment and pass on pop-ups from group #3. You can find more specific details about these rules here.

Clients can choose how to handle pop-ups from group #3: either fail automatically or leave as a comment. This can be toggled in the global settings (by default it’s unchecked i.e. left as a comment without failing the test).

Did this answer your question?