Game Title Test Plan

Professional's opinion

Good Resource of What Testing is.

Flash Unit Test

Game Testing

x.x.x

This document provides complete details of the testing criteria required for all phases of testing (Alpha, Regression and Compliance Testing).

This document is primarily meant for developers and testers who are responsible for conducting Video Game Compliance Testing. This document assumes the reader has a good technical understanding of video games and software development.

To ensure that project requirements are tested in a complete and credible manner, the document includes two sets of test criteria in the two chapters that follow: the Game Test Criteria and the Server Test Criteria. Testers must set up the environment for both sets of criteria as explained below.

Complete the following tasks while referring to the Game Test Criteria

1. Set up the application and device.

1. Set up the test tool

After completing setup of the test environment, you can conduct the Game Test as follows.

1. Fill out the fields in the Game Testing tool section.

1. Go through all the testing criteria as you are instructed in the tool. Not following the instructions and sequence may cause tests to fail.

Note:  Testers do not have to repeat the steps in the test procedure that have
already been completed (for example, Launch application, Login, and so on).
These steps are described fully in the test procedure in case the application
malfunctions and testers need to redo the steps before continuing testing.

Each test criteria sheet includes the following relevant information so the tester can best understand the test being conducted:

• Criteria Type: Tells you if the criteria are tested with the game or the server.
• Criteria ID: Serves as the reference ID for the criterion and will be used in all test documentation.
• Test Type: Indicates whether the test is manual or automatic. A manual test requires manual input using the device and the test application. An automatic test requires no input from the tester at all.
• Requirement Description: Explains the criterion using the wording directly from the design document
• Test Procedure: Provides detailed logical steps to follow for each criterion in order to meet the requirements of the Requirement Description.
• Expected Result: Describes how the application should behave in order to pass the criterion and meet the requirements given in the Requirement Description.
• Notes: Includes any additional information the developer may need to understand the criterion.
• Exceptions: Lists any circumstances under which the criterion would be considered passed without the software or hardware meeting the full requirements of the individual criterion as written.
• Result: Classifies the outcome as either Pass or Fail depending on the observed behavior.

This will contain n number of forms with a direct corallation to the number of requirements.

Link to a Test form

This will contain n number of forms with a direct corallation to the number of requirements.

Link to a Test form

This criterion is applied when retesting an application after it has failed the previous test round.

Assumption: The application has been tested before but did not pass testing on the previous testing round. The tests executed on the next test round are the tests executed on the previous round, plus the additional criterion, shown below.

The program shall exercise no notion of “regression”; all test cases will be undertaken again to ensure that the resubmitted application adheres to all the requirements of the SNAP Criteria.

This will contain n number of forms with a direct corallation to the number of requirements.

Link to a Test form