Hope you enjoyed the first two issues of our newsletter! We will continue our series of helpful tips by covering the rejection status “Not in Scope”.
While you may be testing the same app during multiple cycles, the scope and focus of the test can change.
- The scope refers to what the general purpose of the cycle is.
- Meanwhile, the focus, zones in on a particular feature or update that may have undergone recent updates and can potentially be unstable as a result.
What are the correct steps to follow?
Check the focus and scope of the test. Check the Tester Spec to see which areas are in scope for testing and what the focus of the test is. If the issue does not match the scope and focus, even if it is valid, it will be rejected.
Check if any areas or flows are not to be tested. This is the same as above but needs to be emphasized. Sometimes the spec will mention a specific aspect that should not be tested.
As an example, the Test Spec may have the entire application in scope but will request that you do not test the payment/subscription section. This means that, while you may report any issues you encounter, these should not be related to that specific section or flow.
We hope you found this issue helpful. We want our newsletter to be valuable to you so please share your feedback or suggest future topics. You can also check the previous newsletter issues here.
In the next issue, we will cover the rejection status “Evidence not provided”, see you next time.