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 cases

SRV#0001: Default registry setting requirement, for service mode.

Description.

The server shale run without crashing with a minimal set of settings in the registry.

Expected result.

The server shale connect to the lobby server, set in the registry and display the setting set for this game server.

Dependent test cases.

PLACE HOLDER, the test case is not made yet or there are no test cases dependent prior to this test case.

System requirements.

A Windows OS version XP,XP64 or 2003, in general the same requirement listed in the Running_a_server

Knowledge requirements.

In general this test require the knowledge of a server setup: Server_configuration

Some specific knowledge on how to alter the registry to handle a beta version enviroment, which is using the 1.1 branch of the registry main branch for Allegiance.

General knowledge on how to install the server enviroment and files associated to this enviroment.

Common knowledge on building beta server. This is optional if the server executable and other files are given by a developer.

Components used for the test.

As noted in the Server_configuration there are some configuration files needed for the server to start.

Procedure for recreation.

If the registry keys that are listed are not set in the registry see the Server_configuration for details and syntax.

1. Set the key "EXE Path" in the registry, with Value The Exe path for the server executable file.
2. Set the key "ArtPath" in the registry, with Value The Art path for the server artwork folder.
3. Set the key "LocalAddress" in the registry, with Value "Moon"
4. Set the key "Location" in the registry, with Value "TestArea51"
5. Set the key "MaxGames" in the registry, with Value "00000002"
6. Set the key "CfgFile" in the registry, with "http://fazdev.alleg.net/FAZ/FAZR5.cfg", this value is for R5 test and the value differs from version to version, if in doubt ask a developer. The value set in this version can however be used for most versions since the content is the same and just point to the Beta server lobby! But you never know..
7. Set the key "ASGS_ON" in the registry, with Value "00000001"
8. Set the key "ASGS_RANKS_ON" in the registry, with Value "00000001"
9. Check that any other mandatory Keys are set in registry as by direction in Server_configuration .
10. Check that the dependent files for the server is located as by direction in Server_configuration .
11. If the service is installed proper, the service can now be started.
12. Start a Beta client which accesses the Beta lobby server.
13. Check that the server is listed in the Create Game menu.
14. Check that the Values set in registry correspond to the values set in the list above.
15. If the Values is listed as they are set in registry then the test ends. If they are false check the registry configuration and restart the service.

Associated Test cases.

None at the moment.

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.