Pravila,pravila,neka nova pravila,da bi me udavila i SKROZ POSASAVILA
Please Read: New Pop Up Rule 2017-10-16 18:14:48, Kristen Hohenstein
Hello, dear testers! We’ve made an update to the Pop-Up rule to make it easier on both our testers and customers. In a few hours, you’ll see the updated rule in the tester contract you’ll be asked to sign. Do not start applying this rule until after you’ve reviewed and signed the new tester contract. Once the contract is available, you'll be prompted to sign it upon accepting a job from the Chrome extension. The updated rule is as follows:
Updated Pop Up Rule
Pop-up definition: anything that suddenly appears (text and/or window) and you don’t need to hover over it in order to see it.
You should classify each pop-up you see into one of the 3 groups below and follow the instructions based on the relevant group that the pop-up belongs to:
1. Pop-ups which indicate there is a bug
2. Pop-ups which don’t indicate a bug
3. Pop-ups which may indicate a bug, but you aren't sure if this is the case
Here is what you should do in each situation:
1. Pop-up which indicates a Bug - This is a pop-up that includes an ERROR/ WARNING/ CRASH notification. Basically, it indicates that something went wrong or something is about to go wrong.
- Always fail a test by reporting No when you encounter an ERROR/ WARNING/ CRASH notification.
- If the test author instructed you to ignore a specific type of ERROR/ WARNING/ CRASH pop-up, then you should follow the test author’s instructions and ignore only this specific pop-up. That being said, make sure to report all other ERROR/ WARNING/ CRASH pop-ups that weren’t mentioned by the test author.
2. Pop-up which doesn't indicate a bug - this pop-up indicates an expected system/browser/application behavior. for example - a side chat-box, marketing ad, standard browser question such as “do you want to save this password?”, “do you want to run this file?”, etc.
- Ignore these pop-ups. If they don't disappear and interfere with the flow of the test - take the necessary action to close them and move on with your test.
3. Pop-ups which may indicate a bug, but you aren't sure if this is the case -
- If the pop-up doesn’t fall into one of the two other categories (i.e. it’s not an ERROR/ WARNING/ CRASH pop-up, and it’s not an expected behavior by the system/browser/application), and you think that there is a slight chance that this pop-up may indicate a bug - then take the most reasonable action to close it, notify the user that you closed it via the “Suggest Improvement” option (click "Suggest Improvement" and choose "There was an unexpected popup in this step" category) and move on with your test.
- If the test author instructed you to ignore/close a specific type of pop-up, then you should follow the instructions and ignore/close it without mentioning it in the "Suggest Improvement”.
- You are testing and you see a pop-up asking, “Do you want to subscribe to weekly email updates?”. There are no instructions to ignore pop-ups. You should ignore the pop-up and move on with your test. If needed, close it, and move on with your test.
- One of the steps in the instruction includes a screenshot of an error pop-up that might show up and the test author asks you to close this pop-up if you see this pop-up shows up during the test -> If you see this pop-up you should follow the test author’s instructions - close the pop-up (even though it includes an error message), and move on with your test.
You can find examples additional examples on the “Rule 3 Supporting Examples” page of the wiki: Rule 3 Supporting Examples · rainforestapp/tester-chrome-extension Wiki · GitHub
If you have any questions regarding this update, please submit them on this forum post: Rainforest Tester Portal