\documentstyle[11pt,fullpage]{article}
\begin{document}
\title{Testing Specification Document
\author{Group Name: \\
Group members
\date{\today}
}}
\maketitle

%
%  This section provides a high level overview of the system.
%  Discuss the scope of the testing. (Recall the guidelines for
%  for testing that you gave in the preliminary-design document.
%  It should summarize the specific functional, performance, and internal
%  design characteristics that are to be tested.
%  The testing effort is bounded, criteria for completion of each test phase
%  should be described, and schedule constraints are documented.
% 
\section{Scope of Testing}
%
% Describes the overall strategy for integration. Testing is divided
% into phases and builds that address specific functional and behavioral 
% characteristics of the software. 
%
\section{Test Plan}
%
% You will need to test at the high-level module (class) level, 
% and then test as you put together the different pieces
% of the system. For example, you will want to test your base classes first,
% before proceeding to those classes that inherit from a general class.
% For those classes that have aggregate classes, you should test the
% main class before testing the aggregate classes. Clearly, the testing refers
% to the methods that make up each of the classes.
%
%
% Given that you have developed classes to address the major tasks of
% your system, the following sample breakdown indicates what is considered
% to be ``high-level'' :
%
%	1. User interaction or top level user interface: 
%	(command selection, drawing creation, display 
%	representation, error processing and representation)
%
%	2. Data manipulation and analysis: (symbol creation, 
%	 computation of positions of graphical entities, 
%	 manipulation of input data -- transformation of data from
%	 parsing activities, and generation of new data based on
%	 input data.
%	
%	3. Display processing and generation:
%	(placement of graphical components onto drawing canvas, 
% 	generation of new GUI elements)
%
%	4. Database management (access, update, integrity, performance) 
%
\subsection{Test phases and builds}
%
% A schedule for conducting the tests and the integration is discussed
% in the following subsection. Start and end dates for each phase are 
% established and dates when specific classes will be available are 
% established. 
%
\subsection{Schedule}
%
% A brief description of overhead software (stubs and drivers) concentrates 
% on characteristics that might require special effort.
%
% Criteria for testing and corresponding tests:
%
% 	1. Interface integrity: internal and external interfaces are
%	tested as each class (or group of classes) is incorporated into the
%	structure. (For each class, incorporate one method at a time.)
%
%	2. Functional validity: tests designed to uncover functional errors
%	are conducted.
%
%	3. Information content: tests designed to uncover errors associated 
%	with local or global data structures are conducted.
%
%	
% 
%
\subsection{Overhead software}
%
% Test environment and resources are described. Unusual hardware 
% configurations, exotic simulators, special test tools might
% be discussed in this section. 
%
\subsection{Environment and Resources}
%
% From the information described in the Test plan, give the 
% actual procedure for carrying out the plans.
%
\section{Test Procedure}
%
% For each top level module:
%
%	0. Describe the top level module (in terms of classes and
%	   their methods) 
%
%	1. List the low-level modules that are invoked by the
% 	top level module  (in terms of classes and their methods)
%
%	2. Discuss integration provisions and outline integration tests
% 
%
\subsection{Order of integration}
\paragraph{Purpose}
% As you specify the order of integration, 
% describe (briefly) the classes and their methods that are to be tested.
%
\paragraph{Classes and methods to be tested}
%
% The following subsubsection should be repeated for each class or
% group of classes that are invoked by the top-level classes.
%
\subsubsection{Unit tests for Class X} 
\begin{description}
%
% Describe the tests for each method in the class. (Itemize for each method.)
%
\item[{\bf Description of tests for methods of class X:}] \hfill \\
\begin{itemize}
\item Method X:
\item Method Y:
\item Method Z:
\end{itemize}
%
% Use of stubs or other software to facilitate the test
%
\item[{\bf Overhead software description:}] \hfill \\
%
% What data did you use to conduct the tests?
%
\item[{\bf Test case data:}] \hfill \\
%
% Briefly, what type of results do you expect?
%
\item[{Expected Results:}] \hfill \
\end{description}
%
% DO NOT FILL OUT THE FOLLOWING SECTION FOR THE TESTING SPEC DELIVERABLE!!
% The testing results will be turned when the practice demo is given.
%
% For each top level class, describe the testing results.
% 
%\subsubsection{Actual Test Results}
\section{References}
\section{Appendices}
\end{document}