\item[Revision 1.0] Dec 2, 2015: Fixed spelling and grammar
\item[Revision 0.3] Nov 23, 2015: Added usability test results
\item[Revision 0.2] Nov 23, 2015: Ran most tests and updated the results
\item[Revision 0.1] Nov 22, 2015: Initial version
...
...
@@ -74,7 +75,7 @@ The tests themselves are outlined in the test plan. For more detail
about each test look up a test by its test number in the test plan.
\subsection{Nonogram Image Loader}
These tests were performed by JUnit and were automated unit tests. Some tests in this test suite test the robustness of the image loader.
These tests were performed by JUnit and were automated unit tests. Some tests in this test suite test the robustness of the image loader module.
\resettestcounter
\begin{center}
\begin{table}[h]
...
...
@@ -92,7 +93,7 @@ These tests were performed by JUnit and were automated unit tests. Some tests in
\FloatBarrier
\subsection{Nonogram Number Generator}
These tests were performed by JUnit and were automated unit tests. Some of the tests in this suite test the robustness of the number generator.
These tests were performed by JUnit and were automated unit tests. Some of the tests in this suite test the robustness of the number generator module.
\resettestcounter
\begin{center}
\begin{table}[h]
...
...
@@ -127,7 +128,7 @@ These tests are to make sure the GUI performs according to the specification. Th
\FloatBarrier
\subsection{Game Loading Time}
This is a performance test to make sure the game starts up in a timely manner. This test is test 5.1.0.
This is a performance test to make sure the game starts up in a timely manner which is a non functional requirement. This test is test 5.1.0.
\resettestcounter
\begin{center}
\begin{table}[h]
...
...
@@ -149,7 +150,7 @@ The average of the trials is much below the time required to be considered a pas
\FloatBarrier
\subsection{GUI Response Time}
This is a performance test to make sure the GUI is responsive to the users actions. This test is test 5.2.0.
This is a performance test to make sure the GUI is responsive to the users actions which is a non functional requirement. This test is test 5.2.0.
\resettestcounter
\begin{center}
\begin{table}[h]
...
...
@@ -171,7 +172,7 @@ The average of the trials is much lower lower than what is considered a pass whi
\FloatBarrier
\subsection{Portability Test}
This test involves manually running the game on multiple operating systems. Success is defined as the game runs with no issues.
This test involves manually running the game on multiple operating systems which is a non functional requirement. Success is defined as the game runs with no issues.
\resettestcounter
\begin{center}
\begin{table}[h]
...
...
@@ -189,7 +190,7 @@ This test involves manually running the game on multiple operating systems. Succ
\FloatBarrier
\subsection{Content Updating Test}
This test makes sure that when new images are added, the game can automaticallty find and use them. This is test 5.4.0.
This test makes sure that when new images are added, the game can automaticallty find and use them. This tests a non functional requirement. This is test 5.4.0.
\resettestcounter
\begin{center}
\begin{table}[h]
...
...
@@ -208,7 +209,7 @@ All of the images were loaded regardless of their format so this test passed.
\FloatBarrier
\subsection{Game Logic Test}
These are manual tests that make sure that the game is behaving correctly by correctly responding to the users input.
These are manual tests that make sure that the game is behaving correctly by correctly responding to the users input. This tests the game logic module.
\resettestcounter
\begin{center}
\begin{table}[h]
...
...
@@ -224,7 +225,7 @@ These are manual tests that make sure that the game is behaving correctly by cor
\end{center}
\FloatBarrier
\subsection{UsabilityTest (Survey Feedback)}
\subsection{UsabilityTest (Survey Feedback)}
Surveys were taken by multiple users to have a understanding about usability of this game. The users were instructed to play the game to completion and then were given the survey. The survey can be found in the appendix of the Test Plan.
\resettestcounter
\begin{center}
...
...
@@ -258,6 +259,14 @@ module. The bug was that the loader was not sensitive enough and could
never detect black or white. This has since been fixed.
\subsection{Future Changes}
According to the usability testing, the game needs more features to make it more fun. Currently the users just cheat by clicking everywhere which solves the puzzle very easily. To make the game more fun a scoring system could be added and every time the user clicks the wrong spot, they lose points. Also another idea is if the user clicks too many incorrect spots, they will be forced to retry the level. This forces the user to solve the puzzle using logic instead of guessing. These changes should be implemented then the usability testing redone to check if these ideas actually help.
According to the usability testing, the game needs more features to make
it more fun. Currently the users just cheat by clicking everywhere which
solves the puzzle very easily. To make the game more fun a scoring
system could be added and every time the user clicks the wrong spot,
they lose points. Also another idea is if the user clicks too many
incorrect spots, they will be forced to retry the level. This forces the
user to solve the puzzle using logic instead of guessing. These changes
should be implemented then the usability testing redone to check if
