| ___________________________________________________________________
 Software Testing (QA) Template Pack
These Software Testing (QA) templates provide you with the logs, forms, checklists, and
templates you need to succeed as a QA Manager.
There are 37 Microsoft Word templates in this pack as shown in this
table.
Microsoft
Word Files - Table of Contents
- Acceptance Form
- Acceptance Test Plan
- Action Item Log
- Change Control Form
- Change Control Log
- Change Control Log - Detailed
- Change Request Form
- Data Access Control Form
- Enhancement Request Form
- Installation Completion Form
- Issue Log
- QA / Program Manager Checklist
- Quality Log
- Release Control Form
- Requirements Testing Report
- Risk Log
- Risk Management Plan Form
- Software Test Plan Template
- System Final Release Sign-off Form
- System Requirements Sign-off Form
- System Test Cycle Sign-off Form
- System Test Environment Sign-off Form
- System Test Plan Sign-off Form
- System Test Sign-off Form
- Test Case Template
- Test Case Validation Log
- Test Plan Review Checklist
- Test Plan Task Preparation
- Test Record
- Test Script Allocation Form
- Test Script
- Team Roles and Responsibilities Form
- Team Training Requirements Form
- Unit Test Plan
- User Acceptance Test (UAT) Report
- Version Control Log
- Web Usability Test Report
Microsoft Excel Files -
Table of Contents
Microsoft Excel - Table of
Contents |
| Worksheet |
Use this template to: |
| 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 |
| Change Control Log |
Identify
the basis for the change; confirm whether it is disapproved or approved. Include the
Software Change Request Number (SCR) #, Requirements (Rqmnt) #, date submitted, and whether it is approved/not
approved, on hold, in progress, or cancelled. |
| Change History Log |
Describe the date,
author and history. |
| Data Access Control |
For
each Person or Group, identify the individuals who have access to the test cases and their
status, e.g. all DEV has access to the Test Cases for Web Project 22B. |
| Log Status |
For each log, identify its Log
ID, the nature of the risk/issue, and whether it is Open or Closed. |
| Failed Scripts |
Identify
the Area where the script failed, and provide details on the Set, Date, with a description
of the error and its Severity, e.g. minor error, major error etc. |
| Open Issues |
Identify all the
open issues by number (#); list when they were created; who raised them, provide a brief
description with details of its Assigned/Target Date/Category, Status (e.g. Open of
Closed), Resolution and its Resolution Date. |
| Quality Log |
When
performing the checks, identify the Ref #, its Module, the Method of Checking, name of the
Tester, its Planned Date, Date Completed, details of the Result, the Action Items (i.e.
tasks) and the Sign-off Date. |
| 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. |
| Roles and Responsibilities |
Identify
all the roles on the project, with details of their responsibilities. Include contact
names and email addresses. |
| 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. The total number of issues (a.k.a
anomalies) is calculated in the final column. |
| 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 |
| 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. |
| Task Preparation |
Use
this checklist to prepare for the Test Plan: Review Software Requirements Specifications,
Identify functions/modules for testing, Perform Risk Analysis. The second checklist is for
the Test Plan Population and helps to: Identify/Prioritize features to be tested, Define
Test Strategy; Identify Test Tools; Identify Resource Requirements etc. |
| Test Case |
This Test Case
template is used to capture the name of the Test Case; its Description; Start Conditions;
Pass Criteria; Tester Name; Build Number; identify the Test Data Used; Steps, Action and Expected Result. |
| Test Tracking Report |
Use
this to track the progress of the software tests each Week, capture which are Planned,
were Attempted and numbers that are Successful. |
| Validation Log |
Use this to capture
the Project’s Completion Date; Test Event; Test Case ID; Test Date; Tester; Test
Results and Status |
| Version Control Log |
Use
this to track the Product’s Version No., its Date, and Approvals. |
| 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 Microcontent |
FAQ: What file formats are the
templates?
All files are in Microsoft Word and are Anti-Virus
free!
FAQ: How soon can I download them?
Immediately after you pay online, you are sent to a page
where you can download the templates online.
FAQ: What is the End User License
Agreement?
You can read
the license agreement here
| How does the order process work? |
1. You click the BUY link.
2. This sends you to Clickbank.com, our
ecommernce partner.
3. You are asked to fill in your details.
4. Your payment is processed instantly.
5. You are sent back to Klariti.com
where you can download the template immediately.
Your credit card
statement will show a payment to CLIKBANK.
[Read
More about How
the order process works]
|
|
Case Study Template
Pack