2018-12-04 & 1.0 & Andy worked on 5 - how Intergrated \& System testing helped the process \\
2018-12-05 & 1.0 & Usman worked on Functional Requirements \& tracing the requirements to the test \\
Date 2& 1.1&Notes\\
2018-12-05& 1.0&Vaibhav worked on section 2,3 and 9\\
\bottomrule
\end{tabularx}
\end{table}
...
...
@@ -54,15 +54,73 @@ Through the strategy of dynamic testing, the main testing for the requirements w
During the testing, we found the food usually appears within the snake's body which violated one our functional requirements, so to resolve the issue we used boundary conditions to limit the appearance of the food within the gameplay screen. After making the snake and food display on the screen, we found a bug that the snake's body is not aligned with the food most of the time, we changed the code, so the game is divided into rows and columns with the block size equal to the size of the snake and food. Splitting the screen in grids made the food to reappear within a grid, and the snake could easily eat it making our further implementation easy.
\section{Nonfunctional Requirements Evaluation}
The following tests are performed using the Test Plan. Please refer to that document to get the test ID's.
\subsection{Look and Feel}
\begin{enumerate}
\item{\textbf{TID17}\\}
Test Result: For this test, the application was run and it was observed the application launches with an interface. This interface met the requirements of the game. PASSED.
\end{enumerate}
\subsection{Usability}
\begin{enumerate}
\item{\textbf{TID18}\\}
Test Result: Usability of the application was tested by asking people of different ages to play this game. Then, they were asked to fill a survey on Google forms where they selected their age and user-friendliness of the program. After running the test, an average of 4.5 out of 5 was achieved. PASSED
\end{enumerate}
\subsection{Performance}
\begin{enumerate}
\item{\textbf{TID19}\\}
Test Result: Dynamic testing was performed to do this task. For this various buttons were pressed and the delay time was observed. Every time, the application was able to respond fairly quickly. PASSED
\item{\textbf{TID20}\\}
Test Result: In order to perform this testing, different modes of the game were played and the speed difference was observed. Also, it was observed teh the snake speed doesn't change itself and remains constant within a level. For example, there was quite a seed difference between beginner and intermediate. PASSED
\item{\textbf{TID21}\\}
Test Result: A group of people were asked to play this game and check the responsiveness of buttons while playing the game. After performing this Beta Testing, we got an average rating of 4.7 out of 5 for this area which gives this a clear pass. PASSED
\end{enumerate}
\subsection{Operational and Environmental}
\begin{enumerate}
\item{\textbf{TID22}\\}
Test Result: While asking different people to play this game, USB was used as a resource to transfer this. 100\% of the time, the game was able to run on the other device. PASSED
\end{enumerate}
\subsection{Maintainability and Support Requirements}
\begin{enumerate}
\item{\textbf{TID23}\\}
Test Result: When the group of individuals were asked to take a part in our Beta Testing of the game, every user had a device of their own choice. Overall, the group consisted of people with Windows, Mac OD and Linux operating devices. The software was able to run completely fine on all of them. PASSED
\end{enumerate}
\subsection{etc.}
\subsection{Security and Cultural}
\begin{enumerate}
\item{\textbf{TID17}\\}
Test Result: This software does not contain any outside source of information except the snake logo. The snake logo was taken from an open source website allowing us to use it for any non-commercial purpose. Also, the game checked several times to make sure that the game does not contain anything illegal or offensive. PASSED
\end{enumerate}
\section{Comparison to Existing Implementation}
This section will not be appropriate for every project.
This game is inspired from an old game made by Patrick Gillespie in JavaScript. The current implementation is done using python and making some improvements over the existing game. The interface is one of the major improvements of this project. The old interface has everything (levels, high score, playground) clustered onto one page whereas we implemented them in different modules. Also, numerous features were added such that snake going through boundary in beginner and additional barrier in advances mode. Also, a help page was added to the implementation in order to help new players. Overall, this project extends the existing implementation really well and provide the user with a really fun experience.
\section{Unit Testing}
...
...
@@ -95,6 +153,8 @@ Integrated testing can visibly be traced back to the modules created. The main i
\section{Code Coverage Metrics}
The VUA 30 group has managed to produce anywhere between 95 to 100 percent of code coverage through the tests. This number is highly based on the fact that each of the modules has been covered by the testing. Each test and the results have been recorded in this document which highly matches with the expected results from the Test Plan. Please refer to the TID's above and trace to modules in order to follow up with the testing. Finally, this clearly shows that the group has been able to cover the majority of the aspects of this project, once again confirming the high percent coverage rate.
