The game must be visible within the Games Explorer on Windows Vista and Windows 7. When selected, the game must also display correct metadata. The installation must not create a shortcut to launch the game on the desktop, in the Start menu, or in any other location. Tasks and shortcuts for removal must not be created.

1. After installing the game, open Games Explorer.

2. Verify that the game icon displays in Games Explorer.

3. Right-click the icon and test each application-defined play & support task.

4. Click the icon and verify that the metadata (publisher, developer, genre, release date, version) at the bottom displays and is correct.

5. Verify that the game icon displays Windows Experience Index (WEI) information in Games Explorer.

6. Verify that game hyperlinks for metadata work correctly in Games Explorer. (If hyperlinks don't show up, then this is a possible sign that the exe isn't signed; see section 2.3.)

7. Verify that the game displays accurate parental control rating in Games Explorer. (If it says unrated, then verify that this is an unrated game; otherwise, this is an indicator that the exe isn't signed; see section 2.3.)

8. Verify that the game does not place launch shortcuts on user desktop.

9. Click Start -> All Programs.

10. Verify that the game does not place launch shortcuts in the Start Menu.

11. Verify that the game does not place uninstall shortcuts in Start Menu outside of Control Panel.

12. If the game is distributed digitally, verify that the service provider appears in Windows Games Explorer.

Game must execute within the context of a "Standard User". Parental Controls must be able to block the game. Verify that the GDF has EXE names.

1. Create a Standard User account in Windows Vista or Windows 7 called Toby. Start -> Control Panel -> Add or Remove User Accounts -> Create New Account

2. As Jane, from Administrator account set up Parental Controls for the game. Start -> Control Panel -> Set Up Parental Controls for Any User -> Toby

   1. Verify that the game launches from the Games Explorer icon.

   2. Verify that the game displays accurate Parental Control Rating below the game title in the Parental Controls Control Panel.

   3. Before applying Parental Controls, verify that the game does not prompt for Administrator Credentials on launch.

   4. Set Parental Controls to "On".

   5. In the Windows Settings section, click Games.

   6. Click OK (setting should now be "AO / all games").

   7. Verify that the game runs with these settings as User Jane.

   8. Log off as Jane and log on as Toby.

   9. Verify that the game runs with these settings as User Toby.

   10. Log off as Toby and log on as Jane.

   11. Go back to the previous screen and select "Set Game Ratings".

   12. Select a rating lower than the game's ESRB Rating.

       Note

       If the game is not rated, then skip this step and move onto the next part of this test. It may be necessary to choose a different rating system to find a game rating, depending on the language locale of the SKU being tested.

   13. Log off as Jane and log on as Toby.

   14. Verify that the game does not launch for User Toby when ESRB is blocked by User Jane.

   15. Log off as Toby and log on as Jane.

   16. If changed previously, restore the ESRB settings.

   17. If there are no ESRB settings, then select "Block or Allow Specific Games" and select the game by name.

   18. Log off as Jane and log on as Toby.

   19. Verify that the game does not launch for User Toby when EXE/Name is blocked by User Jane.

   20. Log off as Toby and back on as Jane.

   21. As Jane, open User Controls -> Application Restrictions.

   22. Click "Toby can only use the programs I allow" and click OK (that is, allow no exes).

   23. Go to User Controls | Games Controls and allow the specific game using the ESRB rating.

   24. Log off as Jane, and log on as Toby and try to play the game.

   25. Verify that the game is NOT blocked and that Toby can play it when "allow no exes" is set.

Games that support gamepad controllers must support the Xbox 360 Controller for Windows using the XInput API. All references to common controller triggers and buttons must use the Xbox 360 names.

1. Launch the game.

2. Go into the controller options. **

3. Verify that the game recognizes Xbox 360 Controller for Windows as an input device.

4. Play the game and verify that the game and menu system are controllable with Xbox 360 Controller for Windows.

5. Verify that the Xbox 360 Controller for Windows behaves according to accepted standards. (B for back, A for accept, Start for in game menu/pause or accept, etc.)

6. Verify that the game refers to the controller buttons and triggers using Xbox 360 names.

Note

If the game does not support a game controller and/or only supports keyboard/mouse, then skip this test case.

** Settings for the controller might be located outside of the game.

The game must support at least the following aspect ratios and associated screen resolutions:

• 4:3 "normal" (800×600 or 1024×768)

• 16:9 "widescreen" (1280×720)

• 16:10 "widescreen" (1152×720, 1680×1050, or 800×480)

• Locate the Video Options for the game (this may be in our out of game).

  Note

  The following tests must be done on a widescreen monitor.

  1. In the video resolution section, select 800×600 or 1024×768.

  2. Verify that the game runs at a 4:3 Aspect Ratio resolution.

  3. In the video resolution section, select 1280×720.

  4. Verify that the game runs at a 16:9 Aspect Ratio resolution.

  5. In the video resolution section, select 1680×1050, 800×480, or 1152×720.

  6. Verify that the game runs at a 16:10 Aspect Ratio resolution.

  7. Verify that the game does not stretch the picture and in turn presents a wider area of view.

  8. Verify that the game prompts the user when a change is made to the resolution.

  9. If the user does not accept within 15 seconds, verify that the display reverts to the previous setting.

  10. Verify that the game does not add black bars to the left and right of the game play area. (In this case, you will see the game area still in a 4:3 ratio in the middle of the screen.)

If the game uses Direct3D, then the minimum version supported must be Direct3D 9, and Direct3D must be the default for any display configuration option.

Manual

• Launch the game. In the video options, check to see if there are render options, D3D and/or OpenGL. If there are, verify that the game render options default to Direct3D. If you are unable to verify that D3D9 is the version of DirectX that is being used, then proceed to Automated Test.

Automated Test

• Use tool: Depends.exe

Games and their installers must run correctly without visual problems when DPI scaling is enabled.

Manual

• Set the system to DPI 150%:

  Windows Vista: Control Panel: Personalization, Adjust font size (DPI), Custom DPI. Set to 150%.

  Windows 7: Control Panel: Display, Set to Larger - 150%.

• Run the installation process and game to verify there are no problems with clipped screens or dialog boxes.

Automated Test

• Verify that element <dpiAware>true</dpiAware> is contained in the embedded manifest.

  Use tool: Mt.exe

Every executable file (.EXE extension) included with an application must have an embedded manifest that defines its execution level:

<requestedExecutionLevel level="asInvoker|highestAvailable|requireAdministrator" 
              uiAccess="true|false"/>

Note

For games and game installers, uiAccess should always be set to "false".

1. Verify game executable files contain manifests.

2. Verify game executable file manifest requestedExecutionLevel is "AsInvoker".

Use tool: Mt.exe

To maintain compatibility with x64 versions of Windows:

• Titles and title installers must not contain any 16-bit code or rely on any 16-bit component

• If the game is dependent on kernel-mode drivers for operation, x64 versions of these drivers must be available. The game setup must detect and install the proper drivers and components for 64-bit editions of Windows.

Note

Support for the 64-bit Edition of Windows XP Professional is optional.

Manual Test

1. Run the game on 64-bit editions of Windows. Verify that the game installation process runs normally on 64-bit editions of Windows Vista or Windows 7.

2. Verify that the game does not encounter an error as a result of 16-bit executables on 64-bit editions of Windows Vista or Windows 7. The error will mention the 16-bit application in the error window.

3. If the game has a native 64-bit executable, then use that as well.

All executable code files (for example, .exe and .dll extensions) must be signed with an Authenticode certificate.

If you are using Windows Installer, the installer's package files (.msi files) must be signed.

Manual Test

1. Navigate to the game directory.

2. Locate all of the .exe and .dll files.

3. Right-click Properties on each file.

4. Verify that the game executable files contain a digital signature.

Any kernel-mode driver that is installed by the game must be signed with a publicly valid Authenticode certificate.

Any kernel-mode hardware device driver that is installed by the game must have a Microsoft signature obtained through the Windows Hardware Quality Labs (WHQL) or Driver Reliability Signature (DRS) program.

Manual Test

1. Install the game.

2. Verify that the game install process does not display unsigned driver dialog(s).

Games must not fail to run on future operating systems as indicated by changes in the Windows version number, unless the End User License Agreement prohibits use on future operating systems. If the game is supposed to fail, it must do so gracefully by displaying a message to the user.

Manual Test

1. Install the game on Windows XP, on 32-bit editions of Windows Vista and Windows 7, and on 64-bit editions of Windows Vista and Windows 7.

2. Verify that the game installation process does not encounter an error regarding OS version.

Automated Test

• Use tool: Application Verifier

  1. Launch Application Verifier.

  2. Enable the Compatibility:HighVersionLie test after selecting the INSTALL.EXE.

  3. Install the game and ensure that it does not block installation based on the OS version.

  4. Enable the Compatibility:HighVersionLie test after selecting the GAME.EXE.

  5. Run the game and ensure it does not block execution based on the OS version.

Games must support standard Windows multitasking scenarios.

Create a Standard User account in Windows Vista or Windows 7 called Toby. Start -> Control Panel -> Add or Remove User Accounts -> Create New Account

1. Launch the game as User Jane.

2. ALT+TAB back to the desktop.

3. Verify that the game properly ALT+TABs to the Windows desktop.

4. Click Start -> [arrow to the right of Lock] -> Switch User.

5. Log on as User Toby.

6. Verify that the game launches as User Toby while still running as User Jane.

7. Verify that the game does not encounter errors for User Toby or User Jane during User Switch process.

8. If you can launch another game session, verify that you cannot hear audio from the original game session.

9. Close the game and switch back to the original user and game.

If a game supports saving files, it must be able to save files that have long names and paths. The game must properly handle special file system characters, such as \ / : * ? " < or > in any user input fields used to create file names or paths.

1. Launch the game.

2. Start a new game.

3. Save the game. During the save process, verify that the game saves using the save name: My First Save Game.

4. Exit back to the main menu.

5. Attempt to load the newly saved game.

6. Verify that the game does not encounter errors when handling unsupported file system characters, such as \ / : * ? " < or > If the game allows you, name the saved game.

7. If the user is allowed to name their profile and/or character or save games, verify that the game does not encounter errors when using long file names here as well.

Games with a traditional installation must provide a simplified path in their setup user interface.

1. Insert the game disc.

2. Verify that the game does not display more than one End-User License Agreement (EULA).

3. If the game supports a custom or advanced installation option, verify that this option is accessible during the installation process.

4. Verify that the Default installation option bypasses all user input selections for the installation process (selection of installation folder, components selection, and so on).

5. Verify that the game installation process does not prompt for OS component setup (DirectX setup, Visual C Runtimes, and so on).

6. Verify that the game installation process does not prompt for firewall interaction.

7. Verify that the game automatically runs or that a launcher menu is present at the end of the install process.

8. Verify that the game uninstallation process removes all installed, non-redistributed OS component files and clears all settings. Cleaning up all per-user settings and data (such as saved games) is not required.

The game installer must not assume it is running in the same context as the user. Games must therefore perform per-user tasks on first-run separately from the installation.

1. Verify that you can install the game as User Jane. (This will require elevated rights during the setup/installation process.)

2. Verify that the game installation process prompts User Jane to elevate through Administrator Credentials. (The prompt to elevate will come up when the user attempts to install.)

3. Opt to Autorun the game at the end of installation, if it does not already do so, or launch it from the menu that appears.

4. Once in-game, create a new profile, play and save a game.

5. Exit the game.

6. Restart the game and verify that User Profiles and Saved Games can be accessed by the User Jane account.

Games must be installed to the Program Files folder by default. User data must be written at first run and not during the installation.

1. Install the game using the Default install type.

2. Verify that the game was installed to Program Files.

Note

If this test fails, verify that the game is intended to install for All Users. If so, this is a failure.

Applications must not attempt to install files or registry keys that are protected by Windows Resource Protection (WRP).

• Verify that no Windows Resource Protection WRP dialog boxes appear during the installation process.

The game installer should not assume that installation of Windows components from redistribution packages requires a reboot, unless the reboot is indicated by a return result or by Microsoft documentation.

1. Install the game.

2. Verify that the game does not require the system to be rebooted after installation.

Note

If a Microsoft system update REDIST requires a reboot, then do the following: Complete the game installation, uninstall the game, and reinstall the game a second time. The game installation process should not require a reboot on this second installation.

The game installation program must properly check to ensure that the latest file versions are installed. Installing a game must never regress any files that you do not produce or that are shared by applications that you do not produce.

1. Prior to installing the game, create a pre-install snapshot of System32.

   1. Make a directory called G4Wtest.

   2. Bring up a command Window (Start -> Run -> cmd).

   3. Navigate to c:\windows\system32.

   4. Type dir /o:-g /o:-d >> c:\G4Wtest\pregame.txt.

2. Create a post-install snapshot of System32.

   1. Bring up a command Window (Start -> Run -> cmd).

   2. Navigate to c:\windows\system32.

   3. Type dir /o:-g /o:-d >> c:\G4Wtest\postgame.txt.

   4. Verify that the game does not regress any file versions of files that the game did not produce (...of the files listed in the two documents by comparing pregame.txt to postgame.txt).

For games distributed on CD, DVD, or other removable media that support Autorun, when the disc is inserted for the first time, the application must automatically run or prompt the user to install the game.

Note

Autorun programs that were written for use on versions of Windows prior to Windows Vista should not use the .NET runtime, because this technology is not included with Windows XP or older versions of Windows.

For further guidance, please refer to Games for Windows Technical Requirement 3.7, Support Autorun.

1. Insert the game disc or media.

2. Verify that the install / run dialog box comes up automatically.

3. Windows Vista or Windows 7: Verify that the game Autorun program itself does not prompt User Jane to elevate through Administrator Credentials.

4. Verify that the Autorun executable doesn't need out-of-box REDIST components, such as .NET 3.5, C Run-Time libraries, and so on.

5. Verify that re-inserting the disc in the drive after installation does not cause installation to automatically begin again.

All application installers must take advantage of the Restart Manager APIs to avoid system reboots (see requirement 3.5)

The game must generate no failures running under Microsoft Application Verifier (AppVerifier), version 4.0 or later, in the following tests:

• Basics: Handles, Heaps, Locks, Memory, TLS

• Miscellaneous: DangerousAPIs, DirtyStacks

Use Tool: AppVerifier 4.0 (or later)

1. Install AppVerifier.

2. Launch AppVerifier and select File -> Add Application.

3. Locate the game executable, select it, and click the "Open" button.

4. In the "Applications" section, select the game executable.

5. In the "Tests" section, select the tests listed above under the categories "Basics" and "Miscellaneous" (uncheck ThreadPool and TimeRollOver), and ensure all other tests are not selected.

6. Launch the game.

7. Verify that the game does not generate failures when run under Application Verifier.

Note

Some tests require a debugger to be fully run. This may require an unprotected release version of the game executable, since anti-cheat/anti-piracy technology may interfere with AppVerifer.

Games must handle only exceptions that are known and expected, and Windows Error Reporting must not be disabled. If a fault (such as an Access Violation) is injected into a game, it must allow Windows Error Reporting to report the crash.

Use Tool: Thread Hijacker

• If the application crashes while testing, verify that the game displays Windows Error Reporting properly and collects crash data.

All executable files (for example, .exe or .dll files) must contain an accurate Product Name, Company Name, and File Version.

Manual test:

1. Right-click the game's executable file(s) on both the installation media and those installed to the computer hard drive.

2. Select Properties.

3. Windows XP: Click the Version tab. Verify that the Product Name, Company Name, and File Version fields are properly populated.

4. Windows Vista or Windows 7: Click the Details tab. Verify that the Product name and File Version fields are properly populated. Company Name is not visible in the Windows Vista or Windows 7 properties page.

Automated test:

• Use the Microsoft Games for Windows Test Tool; see section 6.4.

Normal exit of the game must not result in an unknown exception fault.

• After playing the game for a normal gaming session, verify that the game does not generate errors on exit.