Test Plan: Game "Example"
Test Plan: Game "Example"
Game “Example”
Introduction
1.1 Objectives
Test Case Tamer is a web-based Test Management tool used to create and store tests as well as the
results of running those tests. The test team is responsible for testing the product and ensuring it
meets their needs. The test team is both the customer and the tester in this project.
Phase 1 of the project will deliver TCT (Test Case Tamer) with functionality to create and store
manual tests. This will allow the test team to start transferring tests over to the new system. Must
have functionality is considered more important than the delivery date in this project.
2 Scope
The initial phase will include all ‘must have’ requirements. These and any other requirements that
get included must all be tested. At the end of Phase 1, a tester must be able to:
1. Create a manual test with as many steps as necessary
2. Save it
3. Retrieve it and have the ability to view it when running the test
4. Enter results and appropriate comments
5. View results
As the team works with the product they will define the needs for the second phase.
Load testing will not be considered part of this project since the user base is known and not an
issue.
Rewriting, moving or porting existing test cases from the existing Word documents is not
considered part of this project.
3 Assumptions / Risks
3.1 Assumptions
This section lists assumptions that are made specific to this project.
1. Delivery of the product is in format that the test team can check it into CVS.
3.2 Risks
The following risks have been identified and the appropriate action identified to mitigate their
impact on the project. The impact (or severity) of the risk is based on how the project would be
affected if the risk was triggered. The trigger is what milestone or event would cause the risk to
become an issue to be dealt with.
4 Test Approach
The project is using an agile approach, with weekly iterations. At the end of each week the
requirements identified for that iteration will be delivered to the team and will be tested.
Exploratory testing will play a large part of the testing as the team has never used this type of tool
and will be learning as they go. Tests for planned functionality will be created and added to TCT as
we get iterations of the product.
6 Milestones / Deliverables
6.1 Test Schedule
The initial test schedule follows……….
Test Planning
System testing
Regression testing
UAT
Performance testing
Release to Production
6.2 Deliverables
Deliverable For Date / Milestone
1 General
4 Log in view
5 Register-Log in Interactions
Object: Log in via Facebook, create an account view, log in view, Register-Log in Interactions in game
“Example”
1 General
1.1 Open game
Pre steps:
1. Kill the process of game on Iphone
2. Launch game
1.3 Show-Hide
1.3.1 Steps: The game was hidden
1. Click on Exit Button of the iphone
2. Check that the game was hidden
3.2 Email field positive tests String view at <more than 2 symbols (0-9,a-z,A-
Z,’_’,’-‘,’.’)>@<more than 1 symbol (0-9,a-z,A-
Z,’_’,’-‘,’.’)>.<less than 4 symbol (a-z,A-Z)>
4.2 Email positive tests String viewat <more than 2 symbols (0-9,a-z,A-
Z,’_’,’-‘,’.’)>@<more than 1 symbol (0-9,a-z,A-
Z,’_’,’-‘,’.’)>.<more than 1 symbol (a-z,A-Z)>
4.3 Password positive tests String viewat <more than 2 symbols (0-9,a-z,A-
Z,’_’,’-‘,’.’)>
5 Register-Log in Interactions
5.1 Positive tests
Pre-steps:
1. Launch game
2. Create user with email “[email protected]” and password “pass”