Test Plan General Checklist
For whatever test application you intend to test you and your team need a ‘north’, somewhere to go and what a better way to check if you are on the track of your work with a checklist.
I believe is important to have a checklist, nothing too complicated and too elaborate, keep things simple so you can focus on the actual tests and investigations.
Once you start putting in place those checklists and use it often it will then become a habit and a habit of doing the right things will only make your job more efficient and demonstrate that you are a dedicated and well-organised tester.
It will also help you keep on top of things when things go wrong, accept the fact that they will and be prepared for pushed back and postponed releases due to the course of any test project you are involved with.
Here’s a checklist I use. Adjust it accordingly, with your name convention and add or take a line off accordingly with your project. You can also download a spreadsheet template of this list and begin to use it straight away. I only ask to like the page and make any comments below.
1. Review requirements/user story/documentation/CR’s (change requests).
2. Add requirements to the main test plan.
3. Provide test estimation.
4. Complete test approach document.
5. Create, in a structured folder, dated accordingly with the releases for SIT, UAT, pre-Prod and Live in your software testing management of your choice.
6. Write test cases in your software testing management.
7. Review release folders with the test cases ready to run.
8. When the code is deployed and application is ready for tests, run your test cases/scripts.
9. Raise bugs/issues in the bug/issue tracker tool of your choice. Make sure it has a clear summary, clear description, steps to reproduce, gather pieces of evidence such as data, location, screenshots and/or videos. Assign it to the gatekeeper of bugs for triage or directly to the developer.
10. Produce test scenarios report indicate a pass and fail. Bug/issue reports as well, linking with the test scenarios/cases.
11. Once a bug is fixed, then retest defects.
12. Capture screenshots and save as evidence of changes and so you have something to compare before and after.
13. Carry out a regression test once a change in the code and also fixes are made to discover any other bug that fixes could cause elsewhere.
14. Once is deployed to pre-prod/pre-launch carry out a smoke test, with data whenever possible if allowed by the team.
15. Once it goes live, carry out either a smoke test or a sanity check for it basic functionalities and known risk critical places where is likely to break.
16. Save an outstanding bugs/issues report for the next release, sprint or bug fix.
17. Prepare a test completion report and sent out a copy to all the stakeholders involved in the project.
That’s it. I hope you enjoy use it and with this simple checklist, you will benefit from using it.
Please let me know your thoughts dropping a comment below or on the facebook page. Will update with your comments, ideas and critics.
Thank you.
