What are the Scope and Instructions for each test cycle?
Each test cycle has its set of scope and special instructions. Therefore, prior to participating in a test cycle, be sure to read through the high-level product information found in the Product Setup tab and [most importantly] the information found in the Scope & Instructions tab.
Under the Scope & Instructions tab, you will find information such as what activities are In Scope, Out of Scope, Special Instructions, Bug Payout Information, and relevant documentation such as test cases and product guides provided by the customer.
In Scope: Generally, customers will focus on specific areas of their application to be tested (as opposed to "test the entire application"). Therefore, the information provided under 'In Scope' will detail the boundaries that testers should stay within while testing.
Out of Scope: Likewise, customers will generally have specific areas of their application that should not be tested due to the nature of pre-released software (e.g., the email notification system is intentionally turned off to avoid unnecessary emails during testing). Therefore, the information provided under 'Out of Scope' will further detail areas of the application to stay away from and certainly not report bugs against.
Special Instructions: At times, customers will have special instructions for testers. For example, a customer may ask testers to report bugs a certain way in order to conform to their in-house systems and processes.
Please follow these instructions carefully in order to avoid your bugs or test cases being rejected. If you have any questions about the instructions, please utilize the Real Time Chat to get answers from the customer or project manager (however, never post a bug to the chat to request if it is valid or not).