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 some of our best practices on how to 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.
To ensure that testers are focused solely on the task in front of them while they are testing the workflow, our team has worked to eliminate any browser-related modals like "save password" or "browser updates" that could divert a tester's attention away from the task at hand. Additionally, testers have been trained to close these sorts of pop-ups.
Over time, we have realized that there 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 strike a balance, we have come up with some best practices that we have found useful for managing these situations.
Our Best Practices:
1. Notifying testers of any random modals at the beginning of the test.
An effective way of managing how testers should interact with random modals is simply adding a step at the beginning of a test on a site where random modals are known to appear. This step, which can be thought of as an "Agreement" step, would warn the tester at the very beginning of the test that they may encounter surprise modals at some point during the test. Testers can be instructed so that they close and proceed such modals and continue on with the rest of the test. It could be phrased along the lines of:
Action: During this test you may encounter a surprise modal with a message saying (insert message text). If you encounter this modal at any step of the test, please close it and proceed on with the rest of the test.
Question: Do you agree to close this modal if you encounter it during this test?
2. Notifying testers when certain modals should appear during the test
Thought modals are a common element of many websites, not all are "random" in the sense that they can appear anywhere or at any point during a test on a site. Many, because they're triggered by some action performed by a tester, can be anticipated. As they're predictable, it is simple in Rainforest to alert testers to these types of modals and inform them that they should encounter a modal during a specific step.
Action: Navigate to www.rainforestqa.com
Question: Did a modal with a "Welcome to Rainforest!" title appear?
3. Using Screenshots to guide Testers
A powerful tool that can be leveraged to better manage pop-ups in Rainforest is using screenshots help guide testers through out your test. Relating to both of the above, screenshots can be uploaded directly into a step and in the case of pop-ups these screenshots can provide testers with a visual aid to clarify any lingering confusion from describing a modal.
Managing modals in Rainforest comes down to a matter of planning. By anticipating whether a modal might appear or predicting that it will appear at some point, it is possible effectively manage the effects of different types of modals on your Rainforest tests.