Scribd
Upload
236 views3 pages

Testing Template - Plan and Cases Combined

This document outlines a test plan for a project. It includes sections for tracking changes, purpose, related documents, test team members, abbreviations used in test cases, items not covered by testing, how bugs will be tracked, and quality control procedures. The test cases themselves are not included, but the document provides instructions for how they should be formatted and evaluated.

Uploaded by

api-19980631
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
236 views3 pages

Testing Template - Plan and Cases Combined

This document outlines a test plan for a project. It includes sections for tracking changes, purpose, related documents, test team members, abbreviations used in test cases, items not covered by testing, how bugs will be tracked, and quality control procedures. The test cases themselves are not included, but the document provides instructions for how they should be formatted and evaluated.

Uploaded by

api-19980631
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 3

Project Name Test Cases

Project Name
Test Plan

Table of Contents

History of Changes – VERY important to track history of changes to document, who made
the changes, and why.....................................................................................................................1
Version ...........................................................................................................................................1
Date..................................................................................................................................................1
Change............................................................................................................................................1
First Draft.......................................................................................................................................1
Purpose............................................................................................................................................2
Related Documents......................................................................................................................2
Test Team.....................................................................................................................................2
Test Case Abbreviations..............................................................................................................2
Items Not Covered by These Test Cases ...................................................................................2
Bug Tracking...............................................................................................................................2
Quality Control............................................................................................................................2
ROLE (Security Role)....................................................................................................................3

History of Changes – VERY important to track history of changes to document, who made
the changes, and why.

Version Date Change


First Draft

12/3/09 1
Project Name Test Cases

Purpose

The purpose of these test cases is to verify changes to

Related Documents

Requirements Document and location (path)

Test Team

List Test Team members and phone numbers

Test Case Abbreviations

Req Requirement that the test cases are validating (number / identifier)
Case Test Case Number / Identifier
Action Action to perform
Expected Result Result expected when action is complete
P/F Pass / Fail indicator. Checkmark = Pass. “F” = Fail
Notes Additional notes, error messages, or other information about the test.

Items Not Covered by These Test Cases

List any functions or processes not being tested and why.

Bug Tracking

The “Insert Name Here” Database will be used to track defects found while performing the test
cases. All defects will be logged as they are discovered. Defects will be assigned to Person A to
fix, or to Person B to investigate.

Quality Control

The completed test cases will be reviewed to ensure that all cases were run; that all were
completed successfully; and that any deviations from the test cases were noted accordingly.
Each step should be marked as Passed or Failed. Failed cases should be marked with the date
and time of the failure, and the associated test track number. When the failed cases is fixed, the
date and time of the retest should be noted.

12/3/09 2
Project Name Test Cases

ROLE (Security Role)


Function (Section of Software being Tested)
Case Action Expected Result P/F Notes
Number

12/3/09 3

You might also like