Checklist for Executing Scripts
This is a general guidance checklist to be used when executing scripts so that you do not fail or forget an important step. It helps prevent errors from the side of the software tester.
☐ Update the test data sheet with required values, such as user name, functionality, test code, etc.
☐ Use naming conventions defined as testing standards to define a bug appropriately.
☐ Take screen prints for the script executed using naming conventions, and provide test data that you used for the testing. The screen prints will help other testers and developers to understand how the test was executed, and it will also serve as a proof for you. If possible, try to explain the procedure you followed, choice of data, your understanding, etc.
☐ If your team is maintaining any type of tracking sheet, do not forget to update all the tracking sheets for the bug, its status, time and date found, severity, etc.
☐ If you are using a test reporting tool, do not forget to execute the script in the tool. Many test reporting tools require scripts to be executed to start the life cycle of a bug. For example, some test director needs a script to be executed only till the step where the test script fails.
☐ Update the tracking sheets with current status, i.e., the status in reporting tools, etc., if it is required to be updated after you execute the script in the reporting tool.
☐ Check if you have executed all the scripts properly and updated the test reporting tool.
☐ After you complete your day's work, it is better to do a peer-to-peer review. This step is very important and often helps in finding out missing steps/processes.