Added to test report

Doc/SRS/SRS.tex

@@ -146,7 +146,8 @@ image manipulation on a software level to tackle many of the problems at hand.
 
 
 \subsubsection{Individual Product Use Cases}
- The following image is the Use Case representation of Gifitti using UML.
+ The following image is the Use Case representation of Gifitti using UML
+\newpage.
 \begin{figure}[h]
 	\centering
 	\includegraphics[scale=0.4]{UMLUseCase}
@@ -155,6 +156,7 @@ image manipulation on a software level to tackle many of the problems at hand.
 \end{figure}
 \subsection{Functional Requirements}
 
+
 \begin{enumerate}
 \item The user is able to open a GIF from a specified location.\\
 \\Rationale: Allow a user to modify a GIF or pull frames from it.\\

Doc/TestReport/TestReport.tex

@@ -12,12 +12,12 @@
 }
 \usepackage[round]{natbib}
 
-\title{SE 3XA3: Test Report\\Title of Project}
+\title{SE 3XA3: Test Report\\Gifitti}
 
-\author{Team \#, Team Name
-		\\ Student 1 name and macid
-		\\ Student 2 name and macid
-		\\ Student 3 name and macid
+\author{Team \#2, Gifitti
+		\\Pavle Arezina arezinp
+		\\ Riley McGee mcgeer
+		\\ Nicolai Kozel kozeln
 }
 
 \date{\today}
@@ -39,8 +39,8 @@
 \begin{tabularx}{\textwidth}{p{3cm}p{2cm}X}
 \toprule {\bf Date} & {\bf Version} & {\bf Notes}\\
 \midrule
-Date 1 & 1.0 & Notes\\
-Date 2 & 1.1 & Notes\\
+Dec 5 & 1.0 & Functional Testing\\
+Dec 7 & 1.1 & The rest\\
 \bottomrule
 \end{tabularx}
 \end{table}
@@ -103,10 +103,49 @@ Through various test plans being enacted onto this program and other brute force
 This test plan has utilized automated testing for the verification of the manipulation functionality that changes the GIF. That is to say that the
 exported GIF image will match what is created by the user of our product.
 The only tool to be utilized to test this product will be the Microsoft Unit
-Test Framework that is native with Visual Studio. Through this unit testing framework, we will have it set up that it automatically does comparisons of the GIF output to the expected output where it can in a quick manner compare the pixel values to ensure complete accuracy. Throughout utilizing this framework, we have always gotten successful results which allowed us to identify other areas wher the majority of the problems occured.		
+Test Framework that is native with Visual Studio. Through this unit testing framework, we will have it set up that it automatically does comparisons of the GIF output to the expected output where it can in a quick manner compare the pixel values to ensure complete accuracy. Throughout utilizing this framework, we have always gotten successful results which allowed us to identify other areas wher the majority of the problems occured.
+%\newpage		
 \section{Trace to Requirements}
+Refer to Test Plan to see corresponding Tests and SRS to see corresponding Requirements.
+\newpage
 
-		
+\begin{table}
+\centering
+\begin{tabular}{p{0.2\textwidth} p{0.6\textwidth}}
+\toprule
+\textbf{Test} & \textbf{Requirements}\\
+\midrule
+ID1 & FR1\\
+ID2 &  FR1, FR10\\
+ID3 & FR1, FR10\\
+ID4 &  FR1, FR10\\
+ID5 &  FR3, FR8\\
+ID6 & FR2\\
+ID7 &  FR2\\
+ID8 &  FR5, FR6\\
+ID9 & FR4, FR7\\
+ID10 &  FR4, FR7\\
+ID11 & FR11, FR13\\
+ID12 & FR9\\
+ID13 &  FR9\\
+ID14 & FR9\\
+ID15 &  FR9\\
+ID16 &  FR12\\
+ID17 &  FR14\\
+ID18 &  FR14, FR15\\
+ID19 &  NFR1\\
+ID20 &  NFR2\\
+ID21 &  NFR3\\
+ID22 &  NFR7\\
+ID23 &  NFR9\\
+ID24 &  NFR11\\
+
+\bottomrule
+\end{tabular}
+\caption{Trace Between Test Cases and Requirements}
+\label{TblRT}
+\end{table}	
+\clearpage
 \section{Trace to Modules}
 Refer to Test Plan to see corresponding Tests and Module Guide to see corresponding Modules.
 \begin{table}
@@ -123,28 +162,29 @@ ID5 &  M8\\
 ID6 & M8\\
 ID7 &  M8\\
 ID8 &  M8\\
-ID9 & MIL\\
-ID10 &  MIL\\
-ID11 & MIL\\
-ID12 & M6\\
-ID13 &  M6\\
-ID14 & M6\\
-ID15 &  M6\\
-ID16 &  MIL\\
-ID17 &  MIL\\
-ID18 &  MIL\\
-ID19 &  MIL\\
-ID20 &  MIL\\
-ID21 &  MIL\\
-ID22 &  MIL\\
-ID23 &  MIL\\
-ID24 &  MIL\\
+ID9 & M7, M9\\
+ID10 &  M7, M9\\
+ID11 & M7, M9\\
+ID12 & M4, M6\\
+ID13 &  M4, M6\\
+ID14 & M4, M6\\
+ID15 &  M4, M6\\
+ID16 &  M9\\
+ID17 &  M7\\
+ID18 &  M7\\
+ID19 &  M5, M9\\
+ID20 &  M7, M8\\
+ID21 &  M7\\
+ID22 &  M1, M2\\
+ID23 &  M3\\
+ID24 &  M7, M9\\
 
 \bottomrule
 \end{tabular}
-\caption{Trace Between Requirements and Modules}
+\caption{Trace Between Test Cases and Modules}
 \label{TblRT}
 \end{table}		
+\clearpage
 
 \section{Code Coverage Metrics}
 Through an analysis of Trace to Requirements and Trace to Modules sections, the system defined and the system tested almost fully match. Excluding hard to test components of the system, edge coverage of system inputs was tested. \\