Battleship:
During the game testing, errors immediately happened when the two codes got combined in to one method. At first it was some differentiated variable names, however, it ran deeper into some sections of the code, such as storing the data for the player and AI positions once they were selected. After a day of mulling it over once the programmers met back up again they were able to complete the code to run that section. After that section worked they were then able to implement other parts of the code, such as, displaying the ships and the hit or miss images. After the programmers added these new lines of code, errors began to pop back up again. Some of the problems were selecting the correct images to display, and positioning them correctly. After that the programmers also implemented a way for the game to recognize the winner, and to make the AI choose different points to try to guess the position of the users boats instead of trying positions it already chose before. For the most part the code progressed at a good rate and is mostly error free, once the two codes were combined and the programmers worked together it was completed at a fast rate. The tester, Sade, though it was a fun game and did not have any issues with how the game played. However, she did mention that it would be very helpful to include steps on how to play the game which the programmers added to the website.
Blackjack:
When the group started coding, multiple problems arose. The first problem that came up was that the team couldn’t display cards. The team figured out that graphing the cards would net the same result the team wanted. This allowed them to display the player and dealers hand. The next problem that the group faced was designing the hit button to add cards to the hand when pressed. The team solved this issue by creating a function in the code for hit button. This function added a card to the players hand and also the players graphed hand on screen that is displayed. Another issue that the team had was how to code aces into the game. After a lot of research and looking over message boards the team determined that the best route to take when coding aces was to change there value depending on the dealer or players hand value. If a hands value is over 21 and the hand has an ace in it then the hands value is decreased by ten and if the hand is under 21, then the aces value will remain 11. When the team started play testing the game, the group noticed that people would hit the new hand button instead of waiting for the game to reset. This was an issue because it cause the game to reset twice in a row, often in rapid succession. In order to avoid this the team created a message in the game that would be displayed when the game was over. This message would say “Game will auto reset in 7 seconds”.