Software Test Plan

Prepared by Nicholas Otter and Jordan Leithart

Version beta-0.4

TABLE OF CONTENTS

• Change Log
• Introduction
  • Objectives
  • References
• Test Items
• Environmental Requirements
  • Hardware
  • Software
    • Product Requirements
    • Android Requirements
    • Virtual Device Tests
  • Tools
• Features To Be Tested
• Features Not To Be Tested
  • User Manual
  • Software Requirements Specification
  • Software Design Documents
  • Third Party Libraries
• Approach
  • Unit Testing
  • Integration Testing
  • Regression Testing
  • Acceptance Testing
• Pass / Fail Criteria
  • Pass Criteria
  • Fail Criteria
• Testing Process
  • Test Deliverables
  • Testing Schedule

Change Log

Git History

Date	Person	Change
2013-09-20	Nick Otter	Adding Document Outline
2013-09-21	Nick Otter	Adding Initial Content
2013-09-23	Nick Otter	Adding Change Log, correcting Test Type Table

Introduction

###Objectives ###References

Test Items

Environmental Requirements

###Hardware ###Software ####Product Requirements ####Android Requirements ####Virtual Device Tests ###Tools

Features To Be Tested

Testing Feature	Type of Test
Click Junior Button	Integration Test
Click Menu Button	Integration Test
Role Dice	Integration Test
Board/ballTowardsAway	Unit Test
Board/ballTowardsHome	Unit Test
Board/ballMove	Unit Test
Board/ballPosession	Unit Test
Board/dicePositionAway	Unit Test
Board/dicePositionHome	Unit Test
Board/diceChangeFace	Unit Test

Features Not To Be Tested

• User Manual
• Software Requirements Specification
• Software Design Documents
• Third Party Libraries

Approach

Before a new piece of functionality is written, the developer should write the appropriate test(s) for the new function. This will allow the tests to be considered correct; then the developer can make changes to the appropriate class(es).

###Unit Testing

Unit Testing will be accomplished using Google's Android JUnit library.

###Integration Testing

Integration Testing will be accomplished using Robotium to test the user interaction with the Activities.

####Pressing the Application Icon When a user clicks the application icon (the home button) they should be directed to the Main Activity. If the user is on the Main Activity, the Application Icon should do nothing.

####Menu Buttons Clicking on the Menu icon in the Action Bar should show links to the LevelOneRules Activity, which when clicked on should take the user to the LevelOneRules Activity.

###Regression Testing All changes made to the application code will be followed by compilation and test runs to ensure that features are still functioning properly.

###Acceptance Testing Throughout the semester, prototypes and design changes will be presented to the customer to test the changes being made to the application.

Pass / Fail Criteria

###Pass Criteria

Acceptance testing is carried out by the customer upon application presentation. The application must pass the acceptance criteria of:

• Vitually Simplistic
• Visually Appealing
• Functionality meets the customer's specification
  • Ease of use
  • Implements the rules of KickShot Junior

###Fail Criteria

Any behavior that does not fit the above criteria, or complicates usability in the application will deem the task a failure.

Testing Process

###Test Deliverables For acceptance testing, the final working product will be the accepted deliverable. This includes all the documentation associated with KickShot for Android application.

###Testing Schedule Tests will be ran with Spoon with every change to the code.