Testing builds before release
The final component in the verification step of your final release package is to run some tests as a sanity check. These are standard tests that even developers should do, before handing off to your quality assurance group, when checking in bug fixes or after adding a new feature.
A smoke test
The first test, a smoke test, deals with a relatively straightforward and fast series of steps for covering as much of the game mechanics and features as possible without a lengthy review process.
BludBourne start and main menu
1. Verify we have a Proguard-processed archive BludBourne.jar.
2. Verify we have a Packr-generated native executable BludBourne.exe that references the Proguard-processed archive.
3. Start BludBourne by running the native executable, BludBourne.exe.
4. Verify that the main menu is presented with the appropriate choices.
5. Verify music is playing at the main menu.
6. Select Exit.
7. Verify that BludBourne shuts down correctly.
8. Start BludBourne by running...
