diff --git a/Doc/TestPlan/TestPlan.pdf b/Doc/TestPlan/TestPlan.pdf
index 9a6ed25616971664405d6858f7bd20587d7b9f57..45f6ccd02cd369431b0d265461044c43c73b12fc 100644
Binary files a/Doc/TestPlan/TestPlan.pdf and b/Doc/TestPlan/TestPlan.pdf differ
diff --git a/Doc/TestPlan/TestPlan.tex b/Doc/TestPlan/TestPlan.tex
index 129109ba77eadfdbb97a145d01833e3feac5e516..f0296c1f2fb532cbc2f9dc80c43eb38ecb20f85f 100644
--- a/Doc/TestPlan/TestPlan.tex
+++ b/Doc/TestPlan/TestPlan.tex
@@ -111,326 +111,326 @@ GanttChart.pdf}\\
\begin{itemize}
% \begin{enumerate}
- \item FS-NG-1: When user chooses new game, a new page with the options for selecting a new game should open
+ \item \textbf{FS-NG-1: }When user chooses new game, a new page with the options for selecting a new game should open
- Type: Functional, Dynamic, Manual
+ \textbf{Type: }Functional, Dynamic, Manual
- Initial State: Menu page
+ \textbf{Initial State: }Menu page
- Input: Button click
+ \textbf{Input: }Button click
- Output: New game page
+ \textbf{Output: }New game page
- How test will be performed: Run the program and check if appropriate page opens.
+ \textbf{How test will be performed: }Run the program and check if appropriate page opens.
\end{itemize}
\end{reqbox}
\begin{reqbox}
\begin{itemize}
- \item FS-NG-2: Single Player Mode chosen
+ \item \textbf{FS-NG-2: }Single Player Mode chosen
- Type: Functional, Dynamic, Manual
+ \textbf{Type: }Functional, Dynamic, Manual
- Initial State: New game page
+ \textbf{Initial State: }New game page
- Input: Button click
+ \textbf{Input: }Button click
- Output: New single player mode game is started
+ \textbf{Output: }New single player mode game is started
- How test will be performed: Run the program and check if appropriate game mode starts.
+ \textbf{How test will be performed: }Run the program and check if appropriate game mode starts.
\end{itemize}
\end{reqbox}
\begin{reqbox}
\begin{itemize}
- \item FS-NG-3: Advanced Single Player Mode chosen
+ \item \textbf{FS-NG-3: }Advanced Single Player Mode chosen
- Type: Functional, Dynamic, Manual
+ \textbf{Type: }Functional, Dynamic, Manual
- Initial State: New game page
+ \textbf{Initial State: }New game page
- Input: Button click
+ \textbf{Input: }Button click
- Output: New advanced single player mode game is started
+ \textbf{Output: }New advanced single player mode game is started
- How test will be performed: Run the program and check if appropriate game mode starts.
+ \textbf{How test will be performed: }Run the program and check if appropriate game mode starts.
\end{itemize}
\end{reqbox}
\begin{reqbox}
\begin{itemize}
- \item FS-NG-4: Multiplayer Mode chosen
+ \item \textbf{FS-NG-4: }Multiplayer Mode chosen
- Type: Functional, Dynamic, Manual
+ \textbf{Type: }Functional, Dynamic, Manual
- Initial State: New game page
+ \textbf{Initial State: }New game page
- Input: Button click
+ \textbf{Input: }Button click
- Output: New multiplayer mode game is started
+ \textbf{Output: }New multiplayer mode game is started
- How test will be performed: Run the program and check if appropriate game mode starts.
+ \textbf{How test will be performed: }Run the program and check if appropriate game mode starts.
\end{itemize}
\end{reqbox}
\begin{reqbox}
\begin{itemize}
- \item FS-NG-5: Back button to go back to the menu page
+ \item \textbf{FS-NG-5: }Back button to go back to the menu page
- Type: Functional, Dynamic, Manual
+ \textbf{Type: }Functional, Dynamic, Manual
- Initial State: New game page
+ \textbf{Initial State: }New game page
- Input: Button click
+ \textbf{Input: }Button click
- Output: Menu page
+ \textbf{Output: }Menu page
- How test will be performed: Run the program and check if appropriate page opens.
+ \textbf{How test will be performed: }Run the program and check if appropriate page opens.
\end{itemize}
\end{reqbox}
\paragraph{3.1.1.2 Load Game}
\begin{reqbox}
\begin{itemize}
- \item FS-LG-1: Load a saved game instead of starting a new one
+ \item \textbf{FS-LG-1:} Load a saved game instead of starting a new one
- Type: Functional, Dynamic, Automated
+ \textbf{Type:} Functional, Dynamic, Automated
- Initial State: Menu page
+ \textbf{Initial State: }Menu page
- Input: Load previously saved game state
+ \textbf{Input: }Load previously saved game state
- Output: The scores aren’t reset to zero
+ \textbf{Output: }The scores aren’t reset to zero
- How test will be performed: Check that the scores do not start at zero through automated testing. This testing approach may give us errors if the user saved a game state with a zero score. However, this can be overcome by implementing it so that a saved game state with a score of zero will be treated as a new game.
+ \textbf{How test will be performed: }Check that the scores do not start at zero through automated testing. This testing approach may give us errors if the user saved a game state with a zero score. However, this can be overcome by implementing it so that a saved game state with a score of zero will be treated as a new game.
\end{itemize}
\end{reqbox}
\begin{reqbox}
\begin{itemize}
- \item FS-LG-2: Game loaded is same as the game state that was saved the last time
+ \item \textbf{FS-LG-2: }Game loaded is same as the game state that was saved the last time
- Type: Functional, Dynamic, Manual
+ \textbf{Type: }Functional, Dynamic, Manual
- Initial State: Menu page
+ \textbf{Initial State:} Menu page
- Input: Button click
+ \textbf{Input:} Button click
- Output: The scores, game mode, and the speed should be the exact same as ones in the last saved game.
+ \textbf{Output: }The scores, game mode, and the speed should be the exact same as ones in the last saved game.
- How test will be performed: Run the program and check if the data from the saved game state matches the data for the game that is loaded.
+ \textbf{How test will be performed: }Run the program and check if the data from the saved game state matches the data for the game that is loaded.
\end{itemize}
\end{reqbox}
\paragraph{3.1.1.3 Change Speed}
\begin{reqbox}
\begin{itemize}
- \item FS-CS-1: Open speed change page with fast, normal, and slow options
+ \item \textbf{FS-CS-1: }Open speed change page with fast, normal, and slow options
- Type: Functional, Dynamic, Manual
+ \textbf{Type: }Functional, Dynamic, Manual
- Initial State: Menu page
+ \textbf{Initial State:} Menu page
- Input: Button click
+ \textbf{Input: }Button click
- Output: Speed change page
+ \textbf{Output: }Speed change page
- How test will be performed: Run the program and check if appropriate page opens.
+ \textbf{How test will be performed: }Run the program and check if appropriate page opens.
\end{itemize}
\end{reqbox}
\begin{reqbox}
\begin{itemize}
- \item FS-CS-2: Once option is chosen, go back to menu page so user can start a new game
+ \item \textbf{FS-CS-2: }Once option is chosen, go back to menu page so user can start a new game
- Type: Functional, Dynamic, Manual
+ \textbf{Type: }Functional, Dynamic, Manual
- Initial State: Speed change page
+ \textbf{Initial State: }Speed change page
- Input: Button click (one of the three speeds)
+ \textbf{Input: }Button click (one of the three speeds)
- Output: Menu page
+ \textbf{Output: }Menu page
- How test will be performed: Choose a speed, and check if appropriate page opens.
+ \textbf{How test will be performed: }Choose a speed, and check if appropriate page opens.
\end{itemize}
\end{reqbox}
\begin{reqbox}
\begin{itemize}
- \item FS-CS-3: Check that single player mode has the updated speed
+ \item \textbf{FS-CS-3: }Check that single player mode has the updated speed
- Type: Functional, Dynamic, Manual
+ \textbf{Type: }Functional, Dynamic, Manual
- Initial State: Menu page
+ \textbf{Initial State: }Menu page
- Input: Button clicks
+ \textbf{Input: }Button clicks
- Output: Single player mode game starts with the ball having the appropriate speed.
+ \textbf{Output: }Single player mode game starts with the ball having the appropriate speed.
- How test will be performed: Run the program, start a single player mode game and verify the speed.
+ \textbf{How test will be performed: }Run the program, start a single player mode game and verify the speed.
\end{itemize}
\end{reqbox}
\begin{reqbox}
\begin{itemize}
- \item FS-CS-4: Check that advanced single player mode has the updated speed
+ \item \textbf{FS-CS-4: }Check that advanced single player mode has the updated speed
- Type: Functional, Dynamic, Manual
+ \textbf{Type: }Functional, Dynamic, Manual
- Initial State: Menu page
+ \textbf{Initial State: }Menu page
- Input: Button clicks
+ \textbf{Input: }Button clicks
- Output: Advanced single player mode game starts with the ball having the appropriate speed.
+ \textbf{Output: }Advanced single player mode game starts with the ball having the appropriate speed.
- How test will be performed: Run the program, start an advanced single player mode game and verify the speed.
+ \textbf{How test will be performed: }Run the program, start an advanced single player mode game and verify the speed.
\end{itemize}
\end{reqbox}
\begin{reqbox}
\begin{itemize}
- \item FS-CS-5: Check that multiplayer mode has the updated speed
+ \item \textbf{FS-CS-5: }Check that multiplayer mode has the updated speed
- Type: Functional, Dynamic, Manual
+ \textbf{Type: }Functional, Dynamic, Manual
- Initial State: Menu page
+ \textbf{Initial State: }Menu page
- Input: Button clicks
+ \textbf{Input: }Button clicks
- Output: Multiplayer mode game starts with the ball having the appropriate speed.
+ \textbf{Output: }Multiplayer mode game starts with the ball having the appropriate speed.
- How test will be performed: Run the program, start a multiplayer mode game and verify the speed.
+ \textbf{How test will be performed: }Run the program, start a multiplayer mode game and verify the speed.
\end{itemize}
\end{reqbox}
\paragraph{3.1.1.4 Highscores}
\begin{reqbox}
\begin{itemize}
- \item FS-HS-1: Open highscores page when option is chosen from the menu page
+ \item \textbf{FS-HS-1: }Open highscores page when option is chosen from the menu page
- Type: Functional, Dynamic, Manual
+ \textbf{Type: }Functional, Dynamic, Manual
- Initial State: Menu page
+ \textbf{Initial State:} Menu page
- Input: Button click
+ \textbf{Input: }Button click
- Output: Highscores page
+ \textbf{Output: }Highscores page
- How test will be performed: Run the program, and check if appropriate page opens.
+ \textbf{How test will be performed: }Run the program, and check if appropriate page opens.
\end{itemize}
\end{reqbox}
\begin{reqbox}
\begin{itemize}
- \item FS-HS-2: Add a new highscore and check if it is added at the right place in the highscores list
+ \item \textbf{FS-HS-2: }Add a new highscore and check if it is added at the right place in the highscores list
- Type: Functional, Dynamic, Manual
+ \textbf{Type: }Functional, Dynamic, Manual
- Initial State: Menu page
+ \textbf{Initial State: }Menu page
- Input: Button clicks
+ \textbf{Input: }Button clicks
- Output: Highscores page
+ \textbf{Output: }Highscores page
- How test will be performed: Run the program, play a single player mode game, and make a highscore. Go back to the menu page, open the highscores list and check if the new highscore was added or not. Also, make sure that the highscore was added at the correct rank.
+ \textbf{How test will be performed:} Run the program, play a single player mode game, and make a highscore. Go back to the menu page, open the highscores list and check if the new highscore was added or not. Also, make sure that the highscore was added at the correct rank.
\end{itemize}
\end{reqbox}
\paragraph{3.1.1.5 Tutorial}
\begin{reqbox}
\begin{itemize}
- \item FS-TU-1: Open tutorial page when option is chosen from the menu page
+ \item\textbf{ FS-TU-1:} Open tutorial page when option is chosen from the menu page
- Type: Functional, Dynamic, Manual
+ \textbf{Type: }Functional, Dynamic, Manual
- Initial State: Menu page
+ \textbf{Initial State: }Menu page
- Input: Button click
+ \textbf{Input: }Button click
- Output: Tutorial page
+ \textbf{Output: }Tutorial page
- How test will be performed: Run the program, and check if the tutorial page opens.
+ \textbf{How test will be performed: }Run the program, and check if the tutorial page opens.
\end{itemize}
\end{reqbox}
\begin{reqbox}
\begin{itemize}
- \item FS-TU-2: Back button to go back to the menu page
+ \item \textbf{FS-TU-2: }Back button to go back to the menu page
- Type: Functional, Dynamic, Manual
+ \textbf{Type: }Functional, Dynamic, Manual
- Initial State: Tutorial page
+ \textbf{Initial State: }Tutorial page
- Input: Button click
+ \textbf{Input: }Button click
- Output: Menu page
+ \textbf{Output: }Menu page
- How test will be performed: Run the program and check if appropriate page opens.
+ \textbf{How test will be performed: }Run the program and check if appropriate page opens.
\end{itemize}
\end{reqbox}
\subsubsection{Game State}
\begin{reqbox}
\begin{itemize}
- \item FS-GS-1: Paddle movement
+ \item \textbf{FS-GS-1: }Paddle movement
- Type: Functional, Dynamic, Manual
+ \textbf{Type: }Functional, Dynamic, Manual
- Initial State: Game
+ \textbf{Initial State: }Game
- Input: Left key pressed
+ \textbf{Input: }Left key pressed
- Output: User’s paddle is moved left
+ \textbf{Output: }User’s paddle is moved left
- How test will be performed: Run the program, open a game and press left key. Check that the paddle moved left on the console.
+ \textbf{How test will be performed: }Run the program, open a game and press left key. Check that the paddle moved left on the console.
\end{itemize}
\end{reqbox}
\begin{reqbox}
\begin{itemize}
- \item FS-GS-2: Paddle movement
+ \item \textbf{FS-GS-2: }Paddle movement
- Type: Functional, Dynamic, Manual
+ \textbf{Type: }: Functional, Dynamic, Manual
- Initial State: Game
+ \textbf{Initial State: } Game
- Input: Right key pressed
+ \textbf{Input: } Right key pressed
- Output: User’s paddle is moved right
+ \textbf{Output: }User’s paddle is moved right
- How test will be performed: Run the program, open a game and press right key. Check that the paddle moved right on the console.
+ \textbf{How test will be performed: }Run the program, open a game and press right key. Check that the paddle moved right on the console.
\end{itemize}
\end{reqbox}
\begin{reqbox}
\begin{itemize}
- \item FS-GS-3: Increment scores
+ \item \textbf{FS-GS-3: }Increment scores
- Type: Functional, Dynamic, Manual
+ \textbf{Type: }: Functional, Dynamic, Manual
- Initial State: Game
+ \textbf{Initial State: } Game
- Input: One of the users misses a turn
+ \textbf{Input: } One of the users misses a turn
- Output: The other user’s score should increase by 1
+ \textbf{Output: }The other user’s score should increase by 1
- How test will be performed: Run the program, open a multiplayer game and miss one of the player’s turn. Check that the other player’s score increased by 1.
+ \textbf{How test will be performed: }Run the program, open a multiplayer game and miss one of the player’s turn. Check that the other player’s score increased by 1.
\end{itemize}
\end{reqbox}
\begin{reqbox}
\begin{itemize}
- \item FS-GS-4: Decrease lives (in single player mode)
+ \item \textbf{FS-GS-4: }Decrease lives (in single player mode)
- Type: Functional, Dynamic, Manual
+ \textbf{Type: }: Functional, Dynamic, Manual
- Initial State: One of the single player modes game
+ \textbf{Initial State: } One of the single player modes game
- Input: Miss the ball (when thrown by the computer)
+ \textbf{Input: } Miss the ball (when thrown by the computer)
- Output: User’s life should decrease by 1
+ \textbf{Output: }User’s life should decrease by 1
- How test will be performed: Run the program, open one of the single player modes game and miss one turn. Check that the player’s lives decreased by 1.
+ \textbf{How test will be performed: }Run the program, open one of the single player modes game and miss one turn. Check that the player’s lives decreased by 1.
\end{itemize}
\end{reqbox}
@@ -438,69 +438,69 @@ GanttChart.pdf}\\
\subsubsection{Usability}
\begin{reqbox}
\begin{itemize}
- \item FN-1: This testing is done to ensure that the re-designing of the game has made the game better than it was originally.
+ \item \textbf{FN-1: }This testing is done to ensure that the re-designing of the game has made the game better than it was originally.
- Type: Structural, static, manual
+ \textbf{Type: }: Structural, static, manual
- Initial State: Users group have already downloaded and played the original version of the pong game. After playing the game they have also filled in the survey that they were asked to fill in, so that we could have something to compare our game’s ability against. The usability and entertainment factors are the areas we are most focused on for the game.
+ \textbf{Initial State: } Users group have already downloaded and played the original version of the pong game. After playing the game they have also filled in the survey that they were asked to fill in, so that we could have something to compare our game’s ability against. The usability and entertainment factors are the areas we are most focused on for the game.
- Input: the same group of user are given our re-designed game and asked to fill in the same survey.
+ \textbf{Input: } the same group of user are given our re-designed game and asked to fill in the same survey.
- Output/ result: The user response for each major category of the survey is tallied, for both the surveys. Based of that tally, the original game and the redesigned version are given a rating for the usability and entertainment factor of the game.
+ \textbf{Output/ result: }The user response for each major category of the survey is tallied, for both the surveys. Based of that tally, the original game and the redesigned version are given a rating for the usability and entertainment factor of the game.
- How test will be performed: The same group of the user who participated in playing the initial version of the game are made to play the new updated version of the game. They are then given the same survey questions to fill in, as they had filled in after the original game. The result for both versions are tallied. If the updated version receives more favourable responses from the user for the game, then it can be said that this re-design of the game is successful.
+ \textbf{How test will be performed: }The same group of the user who participated in playing the initial version of the game are made to play the new updated version of the game. They are then given the same survey questions to fill in, as they had filled in after the original game. The result for both versions are tallied. If the updated version receives more favourable responses from the user for the game, then it can be said that this re-design of the game is successful.
\end{itemize}
\end{reqbox}
\subsubsection{Operating System Support}
\begin{reqbox}
\begin{itemize}
- \item FN-2: This test is done to confirm that the game runs in all major operating systems such as Windows, Mac OX, Linux etc.
+ \item \textbf{FN-2: }This test is done to confirm that the game runs in all major operating systems such as Windows, Mac OX, Linux etc.
- Type: Functional (dynamic, manual)
+ \textbf{Type: }: Functional (dynamic, manual)
- Tester: Development team
+ \textbf{Tester: }Development team
- Pass: The game can be compiled and run in each of the platform and change the game to make sure that it runs in each operating system.
+ \textbf{Pass: }The game can be compiled and run in each of the platform and change the game to make sure that it runs in each operating system.
\end{itemize}
\end{reqbox}
\subsubsection{Spelling and Grammar}
\begin{reqbox}
\begin{itemize}
- \item FN-3: Making sure that the game does not have any grammar or spelling errors.
+ \item \textbf{FN-3: }Making sure that the game does not have any grammar or spelling errors.
- Type: Functional (dynamic, manual)
+ \textbf{Type: }Functional (dynamic, manual)
- Tester: Development team
+ \textbf{Tester: }Development team
- Pass: The development team checks to see if the game has any grammar or spelling errors in it and all the errors are corrected.
+ \textbf{Pass: }The development team checks to see if the game has any grammar or spelling errors in it and all the errors are corrected.
\end{itemize}
\end{reqbox}
\subsubsection{Hardware Requirement}
\begin{reqbox}
\begin{itemize}
- \item FN-4: Making sure that the speed of game doesn’t change in different machines.
+ \item \textbf{FN-4: }Making sure that the speed of game doesn’t change in different machines.
- Type: Functional (dynamic, manual)
+ \textbf{Type: }: Functional (dynamic, manual)
- Tester: Development team
+ \textbf{Tester: }Development team
- Pass: The development team runs it in their respective computers at the same time to see that the game runs at the same speed in all the computers.
+ \textbf{Pass: }The development team runs it in their respective computers at the same time to see that the game runs at the same speed in all the computers.
\end{itemize}
\end{reqbox}
\subsubsection{Entertainment}
\begin{reqbox}
\begin{itemize}
- \item FN-5: This testing is done to determine if the game is entertaining enough for the user.
+ \item \textbf{FN-5: }This testing is done to determine if the game is entertaining enough for the user.
- Type: Functional (dynamic, manual)
+ \textbf{Type: }: Functional (dynamic, manual)
- Tester: Testing group
+ \textbf{Tester: }Testing group
- Pass: First the testing group is made to play the game and complete the survey relating to it. Then the survey response is tallied and if the average vote says that they deem it entertaining then we pass this test.
+ \textbf{Pass: }First the testing group is made to play the game and complete the survey relating to it. Then the survey response is tallied and if the average vote says that they deem it entertaining then we pass this test.
\end{itemize}
\end{reqbox}
@@ -509,13 +509,13 @@ GanttChart.pdf}\\
\begin{reqbox}
\begin{itemize}
- \item FN-6: This testing is done to determine if the game is challenging enough for the user.
+ \item \textbf{FN-6: }This testing is done to determine if the game is challenging enough for the user.
- Type: Functional (dynamic, manual)
+ \textbf{Type: }: Functional (dynamic, manual)
- Tester: Testing group
+ \textbf{Tester: }Testing group
- Pass: First the testing group is made to play the game and complete the survey relating to it. Then the survey response is tallied and if the average vote says that they rate it medium for challenging then we pass this test. A medium means that the game isn’t too hard but isn’t so easy that it gets boring.
+ \textbf{Pass: }First the testing group is made to play the game and complete the survey relating to it. Then the survey response is tallied and if the average vote says that they rate it medium for challenging then we pass this test. A medium means that the game isn’t too hard but isn’t so easy that it gets boring.
\end{itemize}
\end{reqbox}
@@ -523,13 +523,13 @@ GanttChart.pdf}\\
\subsubsection{Contols}
\begin{reqbox}
\begin{itemize}
- \item FN-7: This testing is done to determine if the game controls are intuitive.
+ \item \textbf{FN-7: }This testing is done to determine if the game controls are intuitive.
- Type: Functional (dynamic, manual)
+ \textbf{Type: }Functional (dynamic, manual)
- Tester: Testing group
+ \textbf{Tester: }Testing group
- Pass: First the testing group is made to play the game and complete the survey relating to it. Then the survey response is tallied and if the average vote is high then we pass the test.
+ \textbf{Pass: }First the testing group is made to play the game and complete the survey relating to it. Then the survey response is tallied and if the average vote is high then we pass the test.
\end{itemize}
\end{reqbox}
@@ -541,82 +541,82 @@ GanttChart.pdf}\\
\begin{reqbox}
\begin{itemize}
- \item PC-1: Checking to see that the games starts with scores set at 0
+ \item \textbf{PC-1: }Checking to see that the games starts with scores set at 0
- Type: Functional, Dynamic, Automated
+ \textbf{Type: }: Functional, Dynamic, Automated
- Initial State: New game page
+ \textbf{Initial State: } New game page
- Input: make a new game state
+ \textbf{Input: } make a new game state
- Output: the score at the beginning of the game
+ \textbf{Output: }the score at the beginning of the game
- How test will be performed: A new game state is created and the score at the beginning of the game is returned and the results are evaluated to see that it matches the expected result. If the results match, then the test unit returns true.
+ \textbf{How test will be performed: }A new game state is created and the score at the beginning of the game is returned and the results are evaluated to see that it matches the expected result. If the results match, then the test unit returns true.
\end{itemize}
\end{reqbox}
\begin{reqbox}
\begin{itemize}
- \item PC-2: Checking to see that the load game mode starts correctly
+ \item \textbf{PC-2: }Checking to see that the load game mode starts correctly
- Type: Functional, Dynamic, Automated
+ \textbf{Type: }: Functional, Dynamic, Automated
- Initial State: Load game page
+ \textbf{Initial State: } Load game page
- Input: make a load game state
+ \textbf{Input: } make a load game state
- Output: the score at beginning of the loaded game and end of the old game
+ \textbf{Output: }the score at beginning of the loaded game and end of the old game
- How test will be performed: A load game state is created and the score at the beginning of the game is returned and result is compared with the score returned at the end of the save game. If the results match, then the test unit returns true.
+ \textbf{How test will be performed: }A load game state is created and the score at the beginning of the game is returned and result is compared with the score returned at the end of the save game. If the results match, then the test unit returns true.
\end{itemize}
\end{reqbox}
\begin{reqbox}
\begin{itemize}
- \item PC-3: Checking to see that the high score function is implemented correctly
+ \item \textbf{PC-3: }Checking to see that the high score function is implemented correctly
- Type: Functional, Dynamic, Automated
+ \textbf{Type: }: Functional, Dynamic, Automated
- Initial State: New game page
+ \textbf{Initial State: } New game page
- Input: make a new game state
+ \textbf{Input: } make a new game state
- Output: the score at the end of the game
+ \textbf{Output: }the score at the end of the game
- How test will be performed: A new game state is created and the score at the end of the game is returned and the over all high scores stored is checked to see if the new high score is added to the list or not. It returns true if the new high score is added only if player beat the old saved records.
+ \textbf{How test will be performed: }A new game state is created and the score at the end of the game is returned and the over all high scores stored is checked to see if the new high score is added to the list or not. It returns true if the new high score is added only if player beat the old saved records.
\end{itemize}
\end{reqbox}
\subsection{Paddle and Ball Movement}
\begin{reqbox}
\begin{itemize}
- \item PC-4: Checking to see that the direction of the ball changes
+ \item \textbf{PC-4: }Checking to see that the direction of the ball changes
- Type: Functional, Dynamic, Automated
+ \textbf{Type: }: Functional, Dynamic, Automated
- Initial State: New game page
+ \textbf{Initial State: } New game page
- Input: initial speed and potion of the ball
+ \textbf{Input: } initial speed and potion of the ball
- Output: the x and y coordinates and speed of the ball
+ \textbf{Output: }the x and y coordinates and speed of the ball
- How test will be performed: A new game state is created and the position of the ball at the beginning of the game is returned and then position and speed of the ball at various stages are returned. If the ball changes direction, then the coordinates should go to negative. If this is happening, then the test function returns true. Otherwise, it returns false.
+ \textbf{How test will be performed: }A new game state is created and the position of the ball at the beginning of the game is returned and then position and speed of the ball at various stages are returned. If the ball changes direction, then the coordinates should go to negative. If this is happening, then the test function returns true. Otherwise, it returns false.
\end{itemize}
\end{reqbox}
\begin{reqbox}
\begin{itemize}
- \item PC-5: Checking to see if the paddle changes direction correctly
+ \item \textbf{PC-5: }Checking to see if the paddle changes direction correctly
- Type: Functional, Dynamic, Automated
+ \textbf{Type: }: Functional, Dynamic, Automated
- Initial State: New game page
+ \textbf{Initial State: } New game page
- Input: the initial position of the paddle
+ \textbf{Input: } the initial position of the paddle
- Output: the coordinates of the paddle at various stages of the game.
+ \textbf{Output: }the coordinates of the paddle at various stages of the game.
- How test will be performed: A new game state is created and the initial position of the paddle is returned in the test unit. When the paddle changes direction, the new coordinates of the paddle is returned. If the coordinates change, then the test function would return true.
+ \textbf{How test will be performed: }A new game state is created and the initial position of the paddle is returned in the test unit. When the paddle changes direction, the new coordinates of the paddle is returned. If the coordinates change, then the test function would return true.
\end{itemize}
\end{reqbox}