Software Testing Document

You can use a Software Testing Document to save time when creating test forms, logs and checklists so your Test Department has a standardized approach to testing.
Software Testing : Contents

1. Acceptance Criteria Log – Use this template to capture the acceptance criteria when testing each functional area.
2. Action Item Log – Allocate an action item number, description, status (Low/Medium/High), date reported, resource it was assigned to, its due date, and other additional comments.
3. Change Control Log – Identify the basis for the change; confirm whether it is disapproved or approved. Include the Software Change Request Number (SCR) #, Requirements #, date submitted, and whether it is approved/not approved, on hold, in progress, or cancelled.
4. Change History Log – Describe the date, author and history in this log file.
5. Data Access Control – For each Person or Group, identify the individuals who have access to the test cases and their status, e.g. Development has access to the Test Cases for Web Project.
6. Deviation Control Form – Use this form to record minor adjustments (i.e. deviations) that must be made to the system in order for testing to proceed.
7. Document Control Form – Use this form to identify, track and monitor test scripts.
8. Failed Scripts – Use this script to identify where test scripts have failed and provide details of the error and its severity, e.g. minor error, major error etc.
9. Issue Submission Form – Use this to describe errors/issues that must be addressed for testing to proceed. Usually sent by users or testers to the Line Manager.
10. Log Status – For each log, identify its Log ID, the nature of the risk/issue, and whether it is Open or Closed.
11. Open Issues – Use this to identify all open issues by number, date created; tester, with descriptions of Target Date, Category, Status, Resolution and Date.
12. Project Costs – Use this spreadsheet to determine the cost of running all test-related activities throughout the software development lifecycle.
13. Quality Log – Use this to capture the module under test, method of checking, tester, Planned Date, Date Completed, Results, Action Items and Sign-off Date.
14. Risk Log – Identify the Risk Number, its Date, Type (e.g. Business/Project/Stage) a brief description, Likelihood %, Severity (e.g. Low or Medium) Impact, Action Required, who is was Assigned To and its Status.
15. Roles and Responsibilities Descriptions & Matrix – Identify all the roles on the project, with details of their responsibilities. Include contact names and email addresses.
16. Status Report – Identify the function that is under test, enter its Business value on a scale of 1-5 with 1 the lowest value and 5 the highest (or whichever numbering system you wish to use); details of the problem severity broken out by a factor of 1 to 5.
17. Test Preparation – Use this to identify all activities that must be performed before testing commences, such as reviewing specifications and prioritizing test items.
18. Test Case – Use this template to test a specific part of the system as per the Test Plan.
19. Test Validation Log – Use this log file to track the results of the test cases.
20. Test Script – Enter the Area under test, its Set, whether it has Passed or Failed, with a Description of the Error and its Severity, e.g. L/M/H.
21. Test Script List – Enter the Area under test, its Test Case ID, Bug ID, Bug Fixed Date, Bug Fixed By and Fix verified By details.
22. Task Preparation – Use this checklist to prepare for the Test Plan: Review Software Requirements Specifications, Identify functions/modules for testing, Perform Risk Analysis.
23. Test Case & Validation Log – Use this Test Case template to capture the name of the Test Case; Description; Start Conditions; Pass Criteria; Tester Name; Build Number; Test Data; Steps, Actions and Expected Result.
24. Test Tracking Report – Use this report to track the progress of the software tests each Week, capture which are Planned, were Attempted and numbers that are Successful.
25. Testing Budget – Use this Excel spreadsheet to plan your quarterly and annual testing budgets. Identify, quantify and cost the resources required by your team to complete projects successfully.
26. Unit Test – Use this to describe the item under test, expected results and whether it passed or failed.
27. Version Control Log – Use this to track the Product’s Version No., its Date, and Approvals.
28. Web Usability Report – Use this to analyze the usability of a web project, such as the performance of its Navigation, Graphics, Error Messages, and the quality of its micro-content.

If you want some perspective on how you or your company needs to enhance their Sales/Client Management Capabilities, please email me (Shubhanjan Saha) at shubhanjan.saha@gmail.com