Test Cases

Test Case 1:

Name: Solving

Design Date: December 17^th, 2013

Execution Date: December 28th, 2013. 

Preconditions: The maze has already been created, and all it needs is solving. 

Steps	Action and Data	Expected Output	Pass or Fail	Comments
1	Press Solve Maze	The maze solves itself	Pass	Yes, it works perfectly fine - solving itself, I mean.
2	N/A	The create button should turn colour	Pass	Yes, the create button changes colour.

Postconditions: The maze would have been solved, and the user should have been given another chance to create a second maze. 
What I Did To Change It: There wasn't anything wrong with it, but I customized my own buttons so that it was a gradient of purple and blue. 

Test Case 2: 

Name: Creating

Design Date: December 17^th, 2013

Execution Date: December 28th, 2013

Preconditions: The array that contains all the information about the array should have been initialized. 

Steps	Action and Data	Expected Output	Pass or Fail	Comments
1	Press Create Maze	The maze should generate a bunch of walls and open spaces. As well, along one of the outer edges, there should be an exit and an entrance.	Pass	I think it shows it well, a clear entrance and a clear exit.
2	N/A	The maze just stays like it is, without being solved.	Pass	The pluses represent the pathway for which a maze should be solved, and these are all open spaces.

Postconditions: The maze has been created.

What Did I Fix: Nothing.

Test Case 3: 

Name: Creating and Solving

Design Date: December 17^th, 2013

Execution Date: December 30th, 2013. 

Steps	Action and Data	Expected Output	Pass or Fail	Comments
1	Press Create Maze	The maze creates itself using characters, and the create maze button should become unclickable	Pass	The createMaze button is unclickable.
2	Press solve maze	The maze should go through and solve it.	Pass	It works.

Postcondition: A maze has been created and solved. 

What I Did To Fix it: Nothing.

Test Case 4: 

Name: Exit

Design Date: December 17^th, 2013

Execution Date: December 30th, 2013

Preconditions: The program is being run. 

Steps	Action and Data	Expected Output	Pass or Fail	Comments
1	Do not press anything	The instruction screen should have popped up.	Pass	It opens in Harry Potter Font.
2	Close it	Exit the program	Pass	The program has finished running.

Postconditions: The program ran, and exited properly.

What Did I Fix: Nothing.

Test Case 5: 

Name: Create, Solve, Create, Solve

Design Date: December 17^th, 2013

Execution Date: January 1, 2014. 

Preconditions: The instructions screen has disappeared, and the gameScreen is shown. 

Steps	Action and Data	Expected Output	Pass or Fail	Comments
1	Press Create	The maze should have created itself.	Pass	It opens in Harry Potter Font.
2	Press Solve	The maze should go through and solve it	Pass	The program has finished running.
3	Press Create again	The maze should restart, and create another maze.	Fail	It just turned up blank
4	Press Solve again	The maze should go through and solve that maze	Fail	It solved a maze that did not exist..on the screen, at least.
5	Press Create again	The maze should create itself from scratch.	Fail	The screen displayed half of a maze, with no exit.
6	Press Solve again	The maze should go through the maze and solve it.	Fail	The program solved an invalid maze!

Postcondition: 3 different mazes has been created.

What I Did To Fix It: I did not realize that the addWalls(); method also called the gameBoard(); method (the gameBoard method displays the icons to the screen). Due to this, the gameBoard(); method was called twice, overwriting what was previously displayed.