Skip to content
Snippets Groups Projects
Commit 26764d7c authored by Pavle Arezina's avatar Pavle Arezina
Browse files

Update on test report

parent 88a89d78
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
Doc/TestPlan/TestPlan.pdf
+ 0
− 0
View file @ 26764d7c
No preview for this file type
Doc/TestPlan/TestPlan.tex
+ 20
− 20
View file @ 26764d7c
......@@ -204,7 +204,7 @@ How test will be performed:
\begin{enumerate}
\item{Save a GIF to a Known Location-id1\\}
\item{Save a GIF to a Known Location-id5\\}
Type: Manual Functional.\\
Initial State: Program loaded; GIF Loaded.\\
......@@ -221,7 +221,7 @@ How test will be performed:
\\
\end{enumerate}
\item{Save GIF to a Non-existent Location- id2\\}
\item{Save GIF to a Non-existent Location- id6\\}
Type: Manual Functional.\\
Initial State: Program loaded; GIF Loaded.\\
......@@ -237,7 +237,7 @@ How test will be performed:
\item{Verify the user is informed that the file path does not work and the system remains running}
\\
\end{enumerate}
\item{Save GIF to Opened Location- id3\\}
\item{Save GIF to Opened Location- id7\\}
Type: Manual Functional.\\
Initial State: Program loaded; GIF Loaded.\\
......@@ -262,7 +262,7 @@ How test will be performed:
\paragraph{The user is able to start and stop GIFs as well as shorten the GIF and change the playback speed.}
\begin{enumerate}
\item{Play Stop GIF-id1\\}
\item{Play Stop GIF-id8\\}
Type: Manual Functional.\\
Initial State: Program loaded; GIF Loaded.\\
......@@ -282,7 +282,7 @@ How test will be performed:
\\
\end{enumerate}
\item{GIF shorten-id2\\}
\item{GIF shorten-id9\\}
Type: Manual Functional.\\
Initial State: Program loaded; GIF Loaded.\\
......@@ -300,7 +300,7 @@ How test will be performed:
\\
\end{enumerate}
\item{Automated GIF Shortening-id3\\}
\item{Automated GIF Shortening-id10\\}
Type: Automated Functional.\\
Initial State: Image reading module driver \\
Input: GIF; Expected output GIF;\\
......@@ -316,7 +316,7 @@ How test will be performed:
\end{enumerate}
\item{GIF speed-id4\\}
\item{GIF speed-id11\\}
Type: Manual Functional.\\
Initial State: Program loaded; GIF Loaded.\\
......@@ -341,7 +341,7 @@ How test will be performed:
\paragraph{The user is able to save a GIF frame by frame to PNG, JPEG, BMP and TIFF formats}
\begin{enumerate}
\item{Save PNG Frames to Known Location-id1\\}
\item{Save PNG Frames to Known Location-id12\\}
Type: Manual Functional.\\
Initial State: Program loaded; GIF Loaded.\\
......@@ -359,13 +359,13 @@ How test will be performed:
\\
\end{enumerate}
\item{Save JPEG frames to known location-id2\\}
\item{Save JPEG frames to known location-id13\\}
This test is identical to id1 with PNG replaced with JPEG
\item{Save BMP frames to known location-id3\\}
\item{Save BMP frames to known location-id14\\}
This test is identical to id1 with PNG replaced with BMP
\item{Save TIFF frames to known location-id4\\}
\item{Save TIFF frames to known location-id15\\}
This test is identical to id1 with PNG replaced with TIFF
\end{enumerate}
%
......@@ -375,7 +375,7 @@ This test is identical to id1 with PNG replaced with TIFF
\paragraph{Verifies and validates the Help context}
\begin{enumerate}
\item{Help Context-id1\\}
\item{Help Context-id16\\}
Type: Manual Functional.\\
Initial State: Program loaded\\
......@@ -398,7 +398,7 @@ How test will be performed:
\paragraph{Verifies a GIF can be exported and resized}
\begin{enumerate}
\item{resizing-id1\\}
\item{resizing-id17\\}
Type: Manual Functional.\\
Initial State: Program loaded\\
......@@ -415,7 +415,7 @@ How test will be performed:
\item{Verify the GIF was exported successfully and resized accordingly.}
\\
\end{enumerate}
\item{resizing-id2\\}
\item{resizing-id18\\}
Type: Manual Functional.\\
Initial State: Program loaded\\
......@@ -446,7 +446,7 @@ Non-functional requirements constrain how the functional requirements and servic
\begin{enumerate}
\item{speed-01\\}
\item{speed-id19\\}
Type: Manual Structural
......@@ -459,7 +459,7 @@ Output: Subsection of frames chosen to be exported.
How test will be performed: Create a timer inside the program to output the time it takes to output the files, to a debug.txt file. The time should be
less than MAX\_EXPORT\_TIME.
\item{speed-02\\}
\item{speed-id20\\}
Type: Manual Structural
......@@ -477,7 +477,7 @@ How test will be performed: Load a GIF into the program. The time to load the GI
\begin{enumerate}
\item{precision-01\\}
\item{precision-id21\\}
Type: Manual Structural
......@@ -495,7 +495,7 @@ How test will be performed: Export the first 5 frames of the GIF. Navigate to th
\begin{enumerate}
\item{safety-01\\}
\item{safety-id22\\}
Type: Manual Structural
......@@ -507,7 +507,7 @@ Output: NA
How test will be performed: Export a subsection of frames from the GIF to a folder. Try to export to the same folder again. The program should ask if you are okay with overwriting the existing files.
\item{safety-02\\}
\item{safety-id23\\}
Type: Manual Structural
......@@ -520,7 +520,7 @@ Output: NA
How test will be performed: Create a small partition of the HDD and fill it so there is no available space. Try to export frames to this location. The program should
not continue the operation and inform the user that disk space needs to be cleared before continuing.
\item{robustness-03\\}
\item{robustness-id24\\}
Type: Manual Structural
......
Doc/TestReport/TestReport.pdf
+ 0
− 0
View file @ 26764d7c
No preview for this file type
Doc/TestReport/TestReport.tex
+ 63
− 4
View file @ 26764d7c
......@@ -73,18 +73,77 @@ A GIF was loaded into the program and a specific size was specified by the user.
\subsection{Performance}
\section{Unit Testing}
Unit testing has been done on system methods that return a value, or modify
known objects in an expected way. A metric for passing is to be used on
all methods with an error tolerance, such as manipulation of a GIF (where
slight variations can exist in the output). A method with no
expected error tolerance has been implemented as discreetly pass XOR fail.
All unit test inputs fall in a known domain where the expected output
can be assumed. The unit tests were utilized to ensure that certain edge cases
were considered and that they did not crash the program.\\
To test the validity of outputted GIF images, the testing system holds
image resources of input frames, input GIFs, as well as the expected GIF
outputted. A known GIF was manipulated and then compared to
the expected GIF in a frame-by-frame matter. To exclude meta-data issues
associated with GIF images, each frame was cast to a known image
format such as a bitmap, then compared pixel-by-pixel. Frames have had
a 100 percent pixel match for the expected GIF to pass. \\
Any written unit test utilizes the C Sharp attributes for
Unit Testing provided by the framework. This ensures the system does not
build the testing package into the consumer version of the software.
\section{Changes Due to Testing}
Through various test plans being enacted onto this program and other brute force testing by persons who had no understanding of code we were able to identify certain areas that were lacking. The general trend is that if a command is successfully inputed, that the expected output, that is the GIF, has been produced accurately for the majority of the time. The main issue the project had to be adjusted to is the different methods and input could be incorrectly given. For example, putting negative values for the frames wanted out of GIF.
Through various test plans being enacted onto this program and other brute force testing by persons who had no understanding of code we were able to identify certain areas that were lacking. The general trend is that if a command is successfully inputed, that the expected output, that is the GIF, has been produced accurately for the majority of the time. The main issue the project had to be adjusted to is the different methods and input could be incorrectly given. For example, putting negative values for the frames wanted out of GIF. Through these testing methadologies, no big corrections were required but extensive testing revealed edge cases that were not previously considered that needed to be corrected. For example, one of the testers caught a work around the file selection to be able to select JPEG images as our input. Of course, futher testing can always be done to catch a possible edge case that has not been considered before.
\section{Automated Testing}
This test plan will utilize automated testing for veri cation that the GIF
manipulation functionality changes the GIF properly. That is to say that the
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.
\section{Trace to Requirements}
\section{Trace to Modules}
\section{Trace to Modules}
Refer to Test Plan to see corresponding Tests and Module Guide to see corresponding Modules.
\begin{table}
\centering
\begin{tabular}{p{0.2\textwidth} p{0.6\textwidth}}
\toprule
\textbf{Test} & \textbf{Modules}\\
\midrule
ID1 & MIL\\
ID2 & MIL\\
ID3 & MIL\\
ID4 & MIL\\
ID5 & MIL\\
ID6 & MIL\\
ID7 & MIL\\
ID8 & MIL\\
ID9 & MIL\\
ID10 & MIL\\
ID11 & MIL\\
ID12 & M6\\
ID13 & MIL\\
ID14 & \ MIL\\
ID15 & MIL\\
ID16 & MIL\\
ID17 & MIL\\
ID18 & MIL\\
ID19 & MIL\\
ID20 & MIL\\
ID21 & MIL\\
ID22 & MIL\\
ID23 & MIL\\
ID24 & MIL\\
\bottomrule
\end{tabular}
\caption{Trace Between Requirements and Modules}
\label{TblRT}
\end{table}
\section{Code Coverage Metrics}
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment