Test Plan for: (Game Name, version, [publisher])

Summary Information

Summary (Summarize the project and the functions of the software to be tested)

Environment/User Community (Identify user community and where testing will be performed)

Test Objectives (State objectives to be accomplished by testing)

Acceptance Criteria (Estimated number of defect or internal test acceptance criteria)

References (List any reference documents)

#

Plan

Test Description (Briefly describe what is being tested and any inputs needed for testing)

Test Team (Who is on the team and what is their role/assignment)

Milestones (Testing Locations, events, test phases and dates of testing

Budgets (Funds allocated to testing by task)

Testing (Requirements)

Resource requirements, equipment, software/hardware, tester with special skill set○Testing Materials/Test Tools

Documentation you will use or produce or testing tools used○Test Training

Personnel training, types of training/training staff- could include acceptance testing or playtesting

#

Specifications and Evaluations

Requirement Specifications (Business Rules/Functions)

List any business requirements (list) (Software/Game Functions)

List any software requirements (list) (Test/Function Relationships)

Match individual tests or test suites to requirements (this is usually a table)

Beginning stages of developing your test suites○Test Progression

Describe how progression is made from one test to another

Methods and Constraints (Test Methodology)

Describe testing strategy/types of testing or any other methodology○Extent of Testing

Full or partial testing and explanation○Constraints

Describe any test condition constraints such as interfaces or data