The testing plan is broken up into distinct parts. Under the heading Plan, the basic information will be given on the product and the tests. System Test Description will contain the specific tests for the functional requirements stated for the product. These tests will broken down into what type of tests they are and the results they achieve depending on their specific input. Test for nonfunctional requirments will follow the same format where input will be given and the output will be measured for all of the provided nonfunctional requirements. Under tests for proof of concept, the same format will be utilized as the functional testing but it will not be testing
The testing plan is broken up into distinct parts. Under the heading Plan, the basic information will be given on the product and the tests. System Test Description will contain the specific tests for the functional a requirements stated for the product. These tests will broken down into what type of tests they are and the results they achieve depending on their specific input. Test for nonfunctional requirments will follow the same format where input will be given and the output will be measured for all of the provided nonfunctional requirements. Under tests for proof of concept, the same format will be utilized as the functional testing but it will not be testing
the requirements for the project but for the goals of the proof of concept. Furthermore there will be tests to compare Gifitti to the
the requirements for the project but for the goals of the proof of concept. Furthermore there will be tests to compare Gifitti to the
original product it was based on and unit testing plans to ensure correct output is achieved through proper internal functions.
original product it was based on and unit testing plans to ensure correct output is achieved through proper internal functions.
...
@@ -108,12 +108,14 @@ of the GIF.
...
@@ -108,12 +108,14 @@ of the GIF.
The only tool to be utilized to test this product will be the Microsoft unit test framework found in the C\# Visual Basic Studio.
The only tool to be utilized to test this product will be the Microsoft unit test framework found in the C\# Visual Basic Studio.
\subsection{Testing Schedule}
\subsection{Testing Schedule}
See Gantt Chart at the following url ...
See Gantt Chart \href{https://gitlab.cas.mcmaster.ca/kozeln/Gifitti/tree/master/ProjectSchedule}{ here.}
\section{System Test Description}
\section{System Test Description}
Testing allows the developers to know if their program is free of errors and if there are errors, testing allows the developer to detect them. With the functional and non-functional requirments the developer knows the expected results and can evaluate the results of tests accordingly.
\subsection{Tests for Functional Requirements}
\subsection{Tests for Functional Requirements}
Functional requirments prescribe what services the software should provide. They capture the intendend software effects on the environment and applicability conditions. These tests ensure that the functional requirments of Gifitti are fufilled or the tests will allow the discovery of any requirments not satisfied by Gifitti.
\subsubsection{Open GIF}
\subsubsection{Open GIF}
\paragraph{The User is Able to Open a GIF from a specified location}
\paragraph{The User is Able to Open a GIF from a specified location}
...
@@ -536,6 +538,9 @@ How test will be performed:
...
@@ -536,6 +538,9 @@ How test will be performed:
\subsection{Tests for Nonfunctional Requirements}
\subsection{Tests for Nonfunctional Requirements}
Non-functional requirmentsconstrain how such services
should be provided. They more involved in the quality of the product such as the safety of utilizing the software or how accurate it is. These tests ensure that the non-functional requirments of Gifitti are fufilled or the tests will allow the discovery of any requirments not satisfied by Gifitti.
\subsubsection{Look and Feel Requirements}
\subsubsection{Look and Feel Requirements}
\paragraph{Audio Test}
\paragraph{Audio Test}
...
@@ -653,6 +658,8 @@ not continue the operation and inform the user that disk space needs to be clear
...
@@ -653,6 +658,8 @@ not continue the operation and inform the user that disk space needs to be clear
\section{Tests for Proof of Concept}
\section{Tests for Proof of Concept}
The proof of concept is a demonstration of the feasibility of the goal of the software project. Ensuring that the Proof on Concept is producing the intended results can only be achieved through tests specifically designed to root out any of the errors present in the build of the proof of concept. By successfully testing the proof of concept and achieving the intended goals it is shown that the software product is a possible product.
\subsection{Opening a GIF file for playback}
\subsection{Opening a GIF file for playback}
\paragraph{Open GIF}
\paragraph{Open GIF}
...
@@ -694,6 +701,7 @@ How test will be performed: Click save frames button, select a folder, and verif
...
@@ -694,6 +701,7 @@ How test will be performed: Click save frames button, select a folder, and verif
\end{enumerate}
\end{enumerate}
\section{Comparison to Existing Implementation}
\section{Comparison to Existing Implementation}
\subsection{Graphics/UI}
\subsection{Graphics/UI}
\begin{enumerate}
\begin{enumerate}
\item GIF playback resolution is the same or better than Gif Viewer.
\item GIF playback resolution is the same or better than Gif Viewer.
