📄
字号:
<html>
<head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="filetype" content="example">
<title>Example: Test Plan</title>
<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<meta name="Microsoft Border" content="b, default">
</head>
<body><!--msnavigation--><table border="0" cellpadding="0" cellspacing="0" width="100%"><tr><!--msnavigation--><td valign="top">
<font face="Arial" size="5">
<p align="RIGHT"><b>Course Registration System</b></p>
</font><b><font face="Arial" size="5"><p align="RIGHT">Test Plan</p>
</font>
<p align="RIGHT"> </p>
<font face="Arial" size="4">
<p align="RIGHT">Version 1.0</p></font>
<font face="Arial" size="5">
<p align="CENTER">Revision History</p></font></b>
<table border="1" cellspacing="1" cellpadding="7" width="90%" height="167">
<tr>
<th width="24%" valign="TOP" scope="col" height="15"><font size="2"><b>
<p align="CENTER">Date</b></font></th>
<th width="12%" valign="TOP" scope="col" height="15"><font size="2"><b>
<p align="CENTER">Version</b></font></th>
<th width="39%" valign="TOP" scope="col" height="15"><font size="2"><b>
<p align="CENTER">Description</b></font></th>
<th width="24%" valign="TOP" scope="col" height="15"><font size="2"><b>
<p align="CENTER">Author</b></font></th>
</tr>
<tr>
<td width="24%" valign="TOP" height="14"><font size="2">27/March/1999</font></td>
<td width="12%" valign="TOP" height="14"><font size="2">1.0</font></td>
<td width="39%" valign="TOP" height="14"><font size="2">Test Plan for
Release 1 and 2</font></td>
<td width="24%" valign="TOP" height="14"><font size="2">K. Stone</font></td>
</tr>
<tr>
<td width="24%" valign="TOP" height="16">
<pre> </pre>
</td>
<td width="12%" valign="TOP" height="16">
<pre> </pre>
</td>
<td width="39%" valign="TOP" height="16">
<pre> </pre>
</td>
<td width="24%" valign="TOP" height="16">
<pre> </pre>
</td>
</tr>
<tr>
<td width="24%" valign="TOP" height="16">
<pre> </pre>
</td>
<td width="12%" valign="TOP" height="16">
<pre> </pre>
</td>
<td width="39%" valign="TOP" height="16">
<pre> </pre>
</td>
<td width="24%" valign="TOP" height="16">
<pre> </pre>
</td>
</tr>
<tr>
<td width="24%" valign="TOP" height="16">
<pre> </pre>
</td>
<td width="12%" valign="TOP" height="16">
<pre> </pre>
</td>
<td width="39%" valign="TOP" height="16">
<pre> </pre>
</td>
<td width="24%" valign="TOP" height="16">
<pre> </pre>
</td>
</tr>
</table>
<p> </p>
<font face="Arial" size="5"><b>
<p align="CENTER"> </p>
<p align="CENTER">Table of Contents</p></b></font>
<ol>
<li><a href="#_Toc447185686"><font size="2">Objectives</font></a></li>
<li><a href="#_Toc447185687"><font size="2">Scope</font></a></li>
<li><a href="#_Toc447185688"><font size="2">References</font></a></li>
<li><a href="#_Toc447185689"><font size="2">Test Requirements</font></a></li>
<li><a href="#_Toc447185690"><font size="2">Test Strategy</font></a>
<ol>
<li><font size="2"><a href="#_Toc447185691">Testing Types</a></font>
<ol>
<li><font size="2"><a href="#_Toc447185692">Data and Database
Integrity Testing</a></font></li>
<li><font size="2"><a href="#_Toc447185693">System Testing</a></font></li>
<li><font size="2"><a href="#_Toc447185694">Business Cycle Testing</a></font></li>
<li><font size="2"><a href="#_Toc447185695">User Interface Testing</a></font></li>
<li><font size="2"><a href="#_Toc447185696">Performance Testing</a></font></li>
<li><font size="2"><a href="#_Toc447185697">Load Testing</a></font></li>
<li><font size="2"><a href="#_Toc447185698">Stress Testing</a></font></li>
<li><font size="2"><a href="#_Toc447185699">Volume Testing</a></font></li>
<li><font size="2"><a href="#_Toc447185700">Security and Access
Control Testing</a></font></li>
<li><font size="2"><a href="#_Toc447185701">Failover / Recovery
Testing</a></font></li>
<li><font size="2"><a href="#_Toc447185702">Configuration Testing</a></font></li>
<li><font size="2"><a href="#_Toc447185703">Installation Testing</a></font></li>
</ol>
</li>
<li><font size="2"><a href="#_Toc447185704">Tools</a></font></li>
</ol>
</li>
<li><font size="2"><a href="#_Toc447185705">Resources</a></font>
<ol>
<li><font size="2"><a href="#_Toc447185706">Workers</a></font></li>
<li><font size="2"><a href="#_Toc447185707">System</a></font></li>
</ol>
</li>
<li><font size="2"><a href="#_Toc447185708">Project Milestones</a></font></li>
<li><font size="2"><a href="#_Toc447185709">Deliverables</a></font>
<ol>
<li><font size="2"><a href="#_Toc447185710">Test Suite</a></font></li>
<li><font size="2"><a href="#_Toc447185711">Test Logs</a></font></li>
<li><font size="2"><a href="#_Toc447185712">Defect Reports</a></font></li>
</ol>
</li>
<li><font size="2"><a href="#_Toc447185713">Project Tasks</a></font></li>
</ol>
<font face="Arial" size="5"><b>
<p align="CENTER">Test Plan</p></b></font>
<font size="2">
<p> </p>
</font>
<p><b><font face="Arial">1. <a name="_Toc447185686">Objectives</a></font></b></p>
<blockquote>
<font size="2">
<p>This document describes the plan for testing the C-Registration System.
This Test Plan document supports the following objectives:</p>
</font>
</blockquote>
<ul>
<ul>
<font size="2">
<li>Identify existing project information and the software components that
should be tested.</li>
<li>List the recommended test requirements (high level).</li>
<li>Recommend and describe the testing strategies to be employed.</li>
<li>Identify the required resources and provide an estimate of the test
efforts.</li>
<li>List the deliverable elements of the test activities.</li></font>
</ul>
</ul>
<p><b><font face="Arial">2. <a name="_Toc447185687">Scope</a></font></b>
<ol>
<font size="2">
<p>This Test Plan applies to the integration and system tests that will be
conducted on the C-Registration System Releases 1 and 2. Note that a separate
Test Plan [17] exists describing the test strategy for the Architectural
Prototype.</p>
<p>It is assumed that unit testing already provided thorough black box testing
through extensive coverage of source code and testing of all module
interfaces.</p>
<p>This Test Plan applies to testing all requirements of the C-Registration
System as defined in the Vision Document [3], Use Case Specifications [5-12],
and Supplementary Specification [13].</p>
</font>
</ol>
<p><b><font face="Arial">3. <a name="_Toc447185688">References</a></font></b></p>
<blockquote>
<font size="2">
<p>Applicable references are:</p>
</font>
</blockquote>
<ol>
<ol>
<font size="2">
<li>Course Billing Interface Specification, WC93332, 1985, Wylie College
Press.</li>
<li>Course Catalog Database Specification, WC93422, 1985, Wylie College
Press.</li>
<li>Course Registration System Vision Document, WyIT387, V1.0, 1998, Wylie College IT.</li>
<li>Course Registration System Glossary, WyIT406, V2.0, 1999, Wylie College IT.</li>
<li>Course Registration System Use Case Spec - Close Registration, WyIT403, V2.0, 1999, Wylie College
IT.</li>
<li>Course Registration System Use Case Spec - Login, WyIT401, V2.0, 1999, Wylie College IT.</li>
<li>Course Registration System Use Case Spec - Maintain Professor Info, WyIT407, Version 2.0, 1999,
Wylie College IT.</li>
<li>Course Registration System Use Case Spec - Register for Courses, WyIT402, Version 2.0, 1999, Wylie
College IT.</li>
<li>Course Registration System Use Case Spec - Select Courses to Teach, WyIT405, Version 2.0, 1999,
Wylie College IT.</li>
<li>Course Registration System Use Case Spec - Maintain Student Info, WyIT408, Version 2.0, 1999, Wylie
College IT.</li>
<li>Course Registration System Use Case Spec - Submit Grades, WyIT409, Version 2.0, 1999, Wylie College
IT.</li>
<li>Course Registration System Use Case Spec - View Report Card, WyIT410, Version 2.0, 1999, Wylie
College IT.</li>
<li>Course Registration System Supplementary Specification,
WyIT400, V1.0, 1999, Wylie College IT.</li>
<li>Course Registration System Software Development Plan, WyIT418, V2.0, 1999, Wylie College IT.</li>
<li>Course Registration System Software Architecture Document,
WyIT431, V1.0, 1999, Wylie College IT.</li>
<li>Course Registration System Requirements Attributes Guidelines,
WyIT404, V1.0, 1999, Wylie College IT.</li>
<li>Course Registration System Test Plan for the Architectural
Prototype, WyIT432, V1.0, 1999, Wylie College IT.</li></font>
</ol>
</ol>
<p><font size="3">4. <a name="_Toc314978532"></a><a name="_Toc324843638"></a><a name="_Toc324851945"></a><a name="_Toc324915528"></a><a name="_Toc433104441"></a></font><b><font face="Arial" size="3"><a name="_Toc447185689">Test
Requirements</a></font></b><font size="2">
<ul>
<p>The listing below identifies those items (use cases, functional requirements,
non-functional requirements) that have been identified as targets for
testing. This list represents <i>what</i> will be tested. Details on
each test will be determined later as Test Cases are identified and
Test Scripts developed.</p>
<p>(Note: Future release of this Test Plan may use Rational RequisitePro for
linking directly to the requirements in the Vision Document, Use Case
Documents and Supplementary Specification.)</p>
<font face="Arial" size="2"><b>
<p>Data and Database Integrity Testing</p>
</b></font>
<blockquote>
<p>Verify access to Course Catalog Database.</p>
<p>Verify simultaneous record read accesses.</p>
<p>Verify lockout during Course Catalog updates.</p>
<p>Verify correct retrieval of update of database data.</p>
</blockquote>
<font face="Arial" size="2"><b>
<p>System Testing (i.e. functional testing)</p>
</b></font>
<blockquote>
<p>Verify Login Use Case [6]</p>
<p>Verify Close Registration Use Case [5]</p>
<p>Verify Maintain Student Information Use Case [10]</p>
<p>Verify Maintain Professor Information Use Case [7]</p>
<p>Verify Submit Grades Use Case [11]</p>
<p>Verify View Report Card Use Case [12]</p>
<p>Verify Register for Courses Use Case [8]</p>
<p>Verify Select Courses to Teach Use Case [9]</p>
<p>Supplementary Specification, Section 4.1: "All system errors shall
be logged. Fatal system errors shall result in an orderly shutdown of the
system."</p>
<p>Supplementary Specification, Section 4.1: " The system error
messages shall include a text description of the error, the operating system
error code (if applicable), the module detecting the error condition, a data
stamp, and a time stamp. All system errors shall be retained in the Error
Log Database."</p>
<p>Vision Document, Section 12.2: "The system shall interface with the
existing Course Catalog Database System. C-Registration shall support the
data format as defined in [2]."</p>
<p>Vision Document, Section 12.2: "The system shall interface with the
existing Billing System and shall support the data format as defined in
[1]."</p>
<p>Vision Document, Section 12.2: "The server component of the system
shall operate on the College Campus Server and shall run under the UNIX
Operating System."</p>
<p>Supplementary Specification, Section 9.3: "The server component of
the system shall operate on the Wylie College UNIX Server."</p>
<p>Vision Document, Section 12.2: "The client component of the system
shall operate on any personal computer with a 486 Microprocessor or
better."</p>
<p>Supplementary Specification, Section 9.3: "The client component of
the system shall operate on any personal computer with a 486 Microprocessor
or greater."</p>
<p>Supplementary Specification, Section 9.1: "The system shall
integrate with existing legacy system (course catalog database) which
operates on the College DEC VAX MainFrame."</p>
<p>Supplementary Specification, Section 9.2: "The system shall
integrate with the existing Course Billing System which operates on the
College DEC VAX MainFrame."</p>
</blockquote>
<font face="Arial" size="2"><b>
<p>Business Cycle Testing</p>
</b></font>
</ul>
</font><blockquote><font size="2">
<blockquote>
<p>Verify operation following download of a new course catalog.</p>
</blockquote>
<blockquote>
<p>Verify operation across multiple semesters and multiple years.</p>
</blockquote>
</font><blockquote><font size="2">
<p>Verify correct operation when semester spans year rollover.</p></font>
</blockquote>
</blockquote>
<ul>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -