To confirm the integrity of the MySQL database which the server-side application will rely on to store critical game and player (login) information.

Systematically test that all desired MySQL statements produce desired results. This can then be implemented within the (server-side) java applciaiton.

Write sample database including several players and serveral games. Use thse demonstration tables to check database behaves as expected and produces expected output.

Requires MySQL to be installed on testing platform.

• User can create new player in database (if unique username & valid password entered).
• User can log on from database (if existing username & cooresponding password entered)
• Player's bankroll is always kept current in database (client always sees correct bankroll).
• Game can be recreated from database after server crashes.

• Testing will require correctly set up MySQL database and user priviledges.

1. Start execution of client-side application, but don't have server-side application running. System should: display error that says "blackjack server could not be found".
2. Start execution of client-side application and make sure server-side application is also running (on the same network). System should: automatically show the Login screen.

• 27April03 on home network

1. Click "create new player" in Login screen. Enter valid user name and password (check first user name does not exist in database) in Create new player screen, (e.g. "jon_1234" and "mypassword"). System should: say "player created successfully" & log user into Virtual Casino screen.
2. Clieck "create new player" in Login screen. Enter invalid user/password in Create new player screen. System should: display error & user can try again

• superseeded

1. Enter valid user name and password (already in database) in Login screen, (e.g: "jon_1234" and "mypassword"). System should: log user into Virtual Casino screen.
2. Enter invalid user/password. System should: display appropriate error & user can try again.

• 27April03 on home network

1. Click "automatically assign to table" in Virtual Casino screen. System should: eventually find (or create) a table with vacant boxes. User should then see gameplay screen.

• 27April03 on home network

Test client-server connection:

NOTE: Most of the phases below will require at least two people logged into the same blackjack game. The more people connected to the server & logged into different games the more thorough the testing. After a certain point (say nine players on three different tables) one would assume the system should work for any number number of players and table threads, therefore benchmarking could begin.

1. Enter & submit bet before timer expirers. System should: not allow you to enter ouside of min & max bets for the table. New table bet & bankroll should update.
2. Don't submit bet before timer expirers. System should: automatically submit whatever bet was entered.

• 27April03 on home network

1. System should: deal out initial cards automatically (according to rules). Ideally this should give the seemless impression of one card being deal at at time (but very quickly).

• Not yet testet

1. In subsequence rounds, test each of the following options.
   • hit
   • stay
   • split
   • double
   • insurance

• System should:
  • only present these options when then apply to the hand.
  • do the correct thing according to the rules after an option is chosen.
  • move onto the next player (in a clockwise direction) after user's first hand has gone bust.
• NOTE: testing that the players turns work correctly will be the most involved of all test. This testing module will be made time consuming by the statisitical fact that, it may take quite a few rounds before the user is presented with the option to split or pay insurance.
• QUESTION: Hey Paul - do you think we should break this up into 5 parts - 1 for each user decision (hit etc)?

• Not yet tested

• System should: show dealer taking his turns (one at a time) according to the rules (ie: dealer hits on 16 or less & stays on anything higher).

• Not yet tested

3.1.3.5) Outcome of the game calculated.

3.1.3.6) All cards removed & next round starts.

• Make sure correct payments (into players bankroll) are made on all bets (see rules). The system should then clear the table instantly & begin a new round.

• Not yet tested

3.1.3.7) At any time a player can hit "leave table".

1. Click "leave table" at various stages of the game - at least once during the 6 stages illustrated above (3.1.3.1-3.1.3.5). System should: remove any money you've bet on the current round (unless it's the betting phase and you haven't submitted a bet) and store your bankroll securely. If you then join another game you're bankroll is the same as it was from the last round.

• Not yet tested

Test in-game chat feature:

NOTE: should require at least two people logged into the same game.

3.1.4.1.1) Test chat feature.

1. Type & submit messages into the chat text box (during various phases of the game). System should: display this message to all players almost immediately.

• 23April03 on home network

1. Select a players name on the list and click "send private message". System should: display message to that player only (in the messages window) & clearly show that it's a private message from you.

• 23April03 on home network

1. Play a few rounds of game and check bankroll changes accroding to rules.
2. Log out, then log back in again to check that bankroll persists.

• Not yet tested

1. Test each menu item in sequence for desired result:
   1. File >> Exit - closes application
   2. Help >> Rules - dialog box appears with link to rules
   3. Help >> Help - dialog appears
   4. Help >> About - dialog appears & shows credits.

• Not yet officially tested

1. Use ethreal to test network load due to TCP IP traffic generated on network.

• 27April03 on manning - determined reduced polling to every half second to reduce network load.

3.3.2.5) The server should be benchmarked to determine maximum number of table threads it can handle gracefully.

1. Install and run server application.
2. Start client blackjack application on networked computers, connect to server and join a table.
3. Monitor the server's performance as each new client is added until performance is unbearably slow

• Not yet tested

3.1.2.1.1) The playerID and password must be valid.

1. Try to login as another player using an correct ID, but an incorrect password.

• 27April03 on home network

3.3.1.3) Log-in data security to ensure maximum reliability.

1. Try an method available to hack into blackjack database and instigate a denial of service attack.

• Not yet tested

1. Try running more than one client blackjack application on a single computer. Running more than one client per computer should be disabled to prevent one person from playing all player at a particular player.

• 19April03 on home network

• Not yet tested

1. Pull the network plug out on the server while a game is underway, and check that the gamestate is reconstructed to it's last saved state.

• partly tested on 27April03 on home network

3.6.8) Provide a config file in XML format that stores the current System configuration (on the server).

• 27April03 on home network

Network or Subnet

Server Name

Database Name

Client Test PCs

Include special configuration requirements

Network or Subnet

Server Name

Internet Browser
NOTE: used to view this site.

Email Client software used to communicate with group members
NOTE: used to communicated problems