While executing test cases, the most important thing to keep in mind is to follow the instructions written in the “Steps” and “Expected result” sections. This includes following instructions about errors, too!
The fact an error message is triggered after following steps in the test case could mean you’ve stumbled upon a bug, but it could also mean you may have not followed the steps properly or the error is included in the “Expected result” field. Always double-check the instructions!
We’ve mentioned, that earlier error messages can sometimes be a blessing. Let’s say you’re executing a set of instructions inside a long and tiresome test case suite: you’re slowly making progress through the first couple of steps when you’re suddenly welcomed with an error message preventing you from further interacting with that feature of the app you’re testing. This could be gold!
But first, as we’ve highlighted earlier, double-check the instructions! Make sure you’ve followed the steps precisely as they’re written in the test case and the error you’re triggering is in fact related to the actions you were doing (manually disconnecting your device from the internet doesn’t count as an error preventing you from executing the test case instructions).
If you’re confident you’ve followed the instructions right, submit a bug report and include it in the test case document under the “Bug ID” column, as it is a blocker for that set of instructions. Don’t forget to mark the test case as “Blocked” and mention the reason under the “Actual results” column as well!
Make sure to upload an attachment for each and every test case marked as failed + add the bug ID associated with it.
Comments
0 comments
Article is closed for comments.