Skip to content
Snippets Groups Projects
Commit 73aae997 authored by Justin's avatar Justin
Browse files

Updated test plan to revision 1 incorporating new requirements

parent 5523f18e
No related branches found
No related tags found
No related merge requests found
No preview for this file type
......@@ -36,7 +36,7 @@
\begin{document}
\title{Test Plan for Pic-Puzzle}
\title{Test Plan for PicPuzzle}
\author{Justin Kapinski, Boyun Deng, Yuchen Liu}
\date{\today}
......@@ -52,6 +52,7 @@
\section{Revision History}
\begin{description}
\item[Revision 1.0] Nov 22, 2015: Fixed more spelling and grammar and updated tests to match new requirements
\item[Revision 0.5] Oct 23, 2015: Revised grammar and spelling
\item[Revision 0.4] Oct 23, 2015: Added test schedule
\item[Revision 0.3] Oct 22, 2015: Added section 'Features Tested in Final'
......@@ -65,22 +66,17 @@
\section{Introduciton}
\subsection{Objectives}
This is the test plan for Pic-Puzzle. The purpose of this document is to
This is the test plan for PicPuzzle. The purpose of this document is to
identify what needs to be done to prepare the tests. Also, the
individuals responsible for each task relating to the tests are
specified. It will also identify what tools will be necessary to perform
the tests. Lastly, it details what each test is and how it will be done.
\subsection{Scope}
This document should outline what needs to be done to test Pic-Puzzle.
This document should outline what needs to be done to test PicPuzzle.
It should describe tests for the basic features that the product must
have.
This is only a Revision 0 document which means the tests are not as
detailed as they will be in the final version. This is because more
information will be available after more of the implementation is
complete.
\subsection{Constraints}
The biggest constraint of this project is time. The project must be
completed by the beginning of December 2015 and this only allows for a
......@@ -89,7 +85,7 @@ few months of development.
\section{Types of Tests}
There are a variety of testing methods that can be used to ensure the
product works as expected. The following describes the methods of
testing that will be utilized to test Pic-Puzzle.
testing that will be utilized to test PicPuzzle.
\subsection{Functional Testing}
Functional testing is a type of black box testing where the test cases
......@@ -169,7 +165,7 @@ be correct.
\end{center}
\subsection{GUI}
Pic-Puzzle is a game and needs to interact with user's mouse. In this
PicPuzzle is a game and needs to interact with user's mouse. In this
case we need to test its GUI features especially the interfacing with
the mouse.
......@@ -182,10 +178,10 @@ the mouse.
\begin{tabular}{ | l | p{3cm} | p{3cm} | p{5cm} |}
\hline
Test Case & Input & Output & Expected Result \\ \hline
\testnumber & The mouse clicks the white square & The color of the square which was originally white & The white square turned to black square. \\ \hline
\testnumber & The mouse clicks the black square & The color of the square which was originally black & The black square turned to white square. \\ \hline
\testnumber & The mouse clicks a correct white square & The color of the square which was originally white & The white square turns to a black square. \\ \hline
\testnumber & The mouse clicks a black square & The color of the square which was originally black & The black square stays black. \\ \hline
\testnumber & The mouse clicks the "close" button & If the program still runs & The program terminates. \\ \hline
\testnumber & The mouse clicks a single square & The number of squares that turned colour & Only one square's colour turned from white to black or from black to white. \\ \hline
\testnumber & The mouse clicks an incorrect white square & The color of the square which was originally white & The square should stay white. \\ \hline
\end{tabular}
\end{table}
\end{center}
......@@ -261,7 +257,7 @@ The product should be easy to add more content to. It should be simple to create
\begin{tabular}{ | l | p{3cm} | p{3cm} | p{5cm} | }
\hline
Test Case & Input & Output & Expected Result \\ \hline
\testnumber &Add more pictures&Game with more pictures and corresponding levels&No errors appear and the process is considerably easy.\\ \hline
\testnumber &Add more pictures&Game with more pictures and corresponding levels&No errors appear and the process is easy.\\ \hline
\end{tabular}
\end{table}
\end{center}
......@@ -270,19 +266,16 @@ The product should be easy to add more content to. It should be simple to create
The game should be working as it is designed to be, following all the rules.
\noindent \textbf{Approach:} \\
\indent To test this, play around with the game and cover as many scenarios as we can, see if the game always does what it should be doing.
\indent To test this, play around with the game and cover as many scenarios as we can, see if the game always does what it should be doing.
\resettestcounter
\begin{center}
\begin{table}[h]
\caption{Content Updating Tests} \label{tab:title}
\caption{Game Logic Tests} \label{tab:title}
\begin{tabular}{ | l | p{3cm} | p{3cm} | p{5cm} | }
\hline
Test Case & Input & Output & Expected Result \\ \hline
\testnumber &Click on start button&Game started&Game started with no errors.\\ \hline
\testnumber &Click on resume button&Game resumed&Game resumed with no errors.\\ \hline
\testnumber &Click on stop button&Game stopped&Game stopped with no errors.\\ \hline
\testnumber &Click on squares&The colour of the square changed&The colour of the square should turn to the opposite colour (white or black).\\ \hline
\testnumber &Click on correct squares&The colour of the square changed&The colour of the square should turn from white to black.\\ \hline
\testnumber &Finish a picture&End of the level&The game should pop up messages to congratulate the user and ask if user want to move to next step.\\ \hline
\testnumber &Finish all the levels&End of the game&The game should pop up messages to congratulate the user and ask if user want to start over.\\ \hline
\end{tabular}
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment