Gamecreation

Overview

Creating games on a server, with different types of server modes:

• Service
• Console
• LAN Games

This section contain the following Test Cases:

• SRV#0001: Default registry setting requirement, for service mode.
• SRV#0002: Fixed Gamecreation using registry settings, default settings, for service mode.
• SRV#0003: Fixed Gamecreation using registry settings, optional settings, for service mode.
• SRV#0004: Default registry setting requirement, for console mode.
• SRV#0005: Fixed Gamecreation using registry settings, default settings, for console mode.
• SRV#0006: Fixed Gamecreation using registry settings, optional settings, for console mode.
• SRV#0007: Default Game is killed when the last players exit the game, default settings, for service mode.
• SRV#0008: Default Game is killed when the last players exit the game, default settings, for console mode.
• SRV#0009: Registry Game setting is sustained when the last player exit the game, optional settings, for service mode.
• SRV#0010: Registry Game setting is sustained when the last player exit the game, optional settings, for console mode.

Test Case Template

The following is a template for test cases. Pictures and screen dumps: Since the wiki don't necessary support upload of pictures or a 3rd party is hosting pictures, please refrain from using this in case the picture is lost.

Test Case Title

Description.

Brief description of the test case.

Expected result.

A brief description of the result/outcome for a success. If this contain several result or its is found that are several results of the test, there should be a sibling test cases in order for the result to straight forward and not conflicting with the case.

Dependent test cases.

A list of test cases which this test case can be dependent of.

System requirements.

A list or simple requirement needed for the test to be conducted in a target environment.

Knowledge requirements.

Headsup for the tester, if special requirement are needed for the test to be fully understood or conducted.

Components used for the test.

List of possible 3rd part elements used for the test cases, this could be configuration files or other assets needed for the test cases to be completed.

Procedure for recreation.

The essential step by step run for the test to be completed, if there is a complications or missing step descriptions during the courses of the test, there should be notes regarding this and/or links to test cases that will cover the missing steps or sidetracks.

Associated Test cases.

Links to associated Test cases which have similar functionality or possible opposing test cases. The link can also be test cases which is dependent of this test case.