Casino Blackjack (Group 53)

Unit Test Plan

Version 1

Revision History

Date | Version | Description | Author
11/05/03 | v1 | Established HTML document | Andrew Noske
26/05/03 | v1 | Added content | Paul Stasuik
27/05/03 | v1 | Modified this HTML document | Paul Stasuik
27/05/03 | v1 | Final review | Paul Stasuik and Andrew Noske

Table of Contents

- 1. Introduction
- 2. Evaluation Mission and Test Motivation
- 3. Target Test Items
- 4. Outline of Planned Tests
- 5. Test Approach
  - 5.1 Initial Test-Idea Catalogs and Other Reference Sources
  - 5.2 Testing Techniques and Types
    - 5.2.1 Data and Database Integrity Testing
    - 5.2.2 Function Testing
- 6. Entry and Exit Criteria
- 7. Deliverables
- 8. Testing Workflow
- 9. Environmental Needs
  - 9.1 Base System Hardware
  - 9.2 Base Software Elements in the Test Environment
  - 9.3 Productivity and Support Tools
  - 9.4 Test Environment Configurations
- 10. Responsibilities, Staffing and Training Needs
- 11. Iteration Milestones
- 12. Risks, Dependencies, Assumptions and Constraints
- 13. Management Process and Procedures

Unit Test Plan

# 1. Introduction

- NOT REQUIRED.

# 2. Evaluation Mission and Test Motivation

- NOT REQUIRED.

# 3. Target Test Items

- The System as described by the project SAD v2 [html link to it].
- The unit testing is based on the SRS v3 [html link to it].

# 4. Outline of Planned Tests

- NOT REQUIRED.

# 5. Test Approach

In order to confirm that the UNIT TESTING is implemented in accordance with the project SAD v3, the SAD v3 features are listed below with appropriate testing solutions.

SRS requirement | Test | Successfully tested
3.1.1 - Create New Virtual Player | The testing involved in this section of the program involved creating a player named Andrew Noske see click the following link to see testpage. | Yes the test was successful see test page for detailed results.
3.1.2 - User logs into virtual casino and gets assigned to a table | The testing for this can be found on testpage. | Yes the test was successful see test page for detailed results.
3.1.3 - User plays blackjack at a table | The testing for this can be found on testpage | Yes the test was successful see test page for detailed results.

## 5.1 Initial Test-Idea Catalogs and Other Reference Sources not required

## 5.2 Testing Techniques and Types

### 5.2.1 Data and Database Integrity Testing

Technique Objective: | If database is not present on system tested a bach file is run which calls a Java app to populate the database with user name and passwords. The database was tested for content and test files containing username and password are contained within database testfile.
Technique: | for a detailed look at the process used to test the database please follow the link database testing.
Oracles: | N/A
Required Tools: | base configuration backup and recovery toolss installation-monitoring tools (hard disk) database SQL utilities and tools data-generation scripts
Success Criteria: | The testing scripts used have all shown that the database is functioning correctly and has been successfully integrated into the overall system effectively.
Special Considerations: | Is that the database is able to record the proper bank balances when a certain player exits the game That the database is able to retrieve the proper bank balance when a certain playerID is entered into the join game GUI interface The database is pre-populated using a batch file and java app when the client initally loads virtual casino program onto the system. Rollback and recovery.

### 5.2.2 Function Testing

The function testing of the target-of-test focuses on use case for section 3.1.1 of the SRSv3. The testing focuses on verifying that the proper actions are taken under difference circumstances. This testing was carried out by actually interacting with the graphical user interfaces and analyzing the results.

Technique Objective: | Three separate sections were tested within the section 3.1.1 through to section 3.1.3 of the SRSv3.
Technique: | Please follow the test link to see how the different sections were unit tested and in which order.
Oracles: | N/A
Required Tools: | The technique used to gather information was by constant (every 1/2 second) built-in monitoring software which enables text output to be recorded for most actions to file. data-generation tools
Success Criteria: | The use-case scenarios used was either that the function passed the given criteria or failed. The technique supports the testing of: all key use-case scenarios all key features
Special Considerations: | The greatest impact of the above testing was that most circumstances were easier to enact by end-user testing then to implement automated testing as the end-user was able to catch more bugs that the system developer was unable to account for as the intricate rules of blackjack posed interesting unforeseen effects.

# 6. Entry and Exit Criteria

- NOT REQUIRED.

# 7. Deliverables

- NOT REQUIRED.

# 8. Testing Workflow

- NOT REQUIRED.

# 9. Environmental Needs

##
9.1 Base System Hardware

The following table sets forth the system resources for the test effort presented in this Test Plan.

Resource | Quantity | Name and Type
Network or Subnet Server Name Database Name | 1 | jcu.edu.au network
localhost | localhost that the program is installed on (localhost unless machine is uniquely named)
mysql | mysql version 3.23.51.NT or later
Client Test PCs Include special configuration requirements | 4 | pentimum4, 2Ghz, with 512RAM using window XP operating system
configuration files are located in the .bat files and clients are assigned unique ID numbers to ensure sale of product | Virtual Casino client architecture
Network or Subnet Server Name | 1 | jcu.edu.au network
localhost | localhost that the program is installed on (localhost unless machine is uniquely named)
Test Development PCs | pentimum4, 2Ghz, with 512RAM using window XP operating system | home computer

## 9.2 Base Software Elements in the Test Environment

The following base software elements are required in the test environment for this Test Plan.

Software Element Name | Version | Type and Other Notes
NT Workstation | 2000 | Operating System
Windows XP | professional with service packs 1 and 2 installed with critical updates | Operating System
Internet Explorer, or Netscape Navigator | v4+ | Internet Browser NOTE: used to view this site.
Blue jay | v1.4 | Java development platform
MySQL | 3.23.51.NT or later | DBMS
Microsoft Outlook | v6 | Email Client software used to communicate with group members NOTE: used to communicated problems
JBuilder | 8 personal | Java development platform
AVG virus software | v1.6 | Virus Detection and Recovery software used to filter emails

## 9.3 Productivity and Support Tools

The following will be employed to support the test process for this Test Plan.

Tool Category or Type | Tool Brand Name | Vendor or In-house | Version
Test Management | Complete system analysis | In house (Jon) | 1.0
Defect Tracking | Complete system analysis | In house (Jon) | 1.0
Project Management | Microsoft project | Microsoft | XP
DBMS tools | SQLYog | Webyog | 1.7.1

## 9.4 Test Environment Configurations

The following Test Environment Configurations need to be provided and supported for this project.

Configuration Name | Description | Implemented in Physical Configuration
Average user configuration | automated | batch file and java application upon installation
Minimal configuration supported | 500MHz, 512MB RAM computer | N/A
Network installation (not client) | automated | done by installation of executables