Objective: Ensure that missions being uploaded to the server are functional.
Whereas functional implies:

  1. Adherence to the TG mission naming standard.
  2. Adhere to the TG SOPs in regard to wholesomeness of material – i.e. no racist, offensive or otherwise unacceptable content.
  3. Contains a coherent briefing.
  4. Contains a coherent schema for gameplay.
  5. Loads and appears in the mission browser, without crashing.
  6. Is technically playable. I.e. playable framerates, not prone to headbug, no extremely loud sounds, does not desync server etc.
  7. Can pass a general examination:
    1. Respawn, if implied to be a gameplay feature, works.
    2. Objectives, if implied to be a gameplay feature, work.
    3. ACE medical, if implied to be a gameplay feature, is enabled and medical supplies are made available to players.
    4. Ammo crates, if present, contain appropriate equipment and ammo.
    5. JIP, if implied to be a gameplay feature, works.
    6. Is not prone to localization issues, i.e. the same group of enemies spawning for each client on the server
    7. Vehicle respawn, if implied to be a gameplay feature, works.
    8. Players have weapons/ammo or can access weapons/ammo.
      1. JIP/Respawn players adhere to this rule
    9. Slot screen does not include any test dummies or otherwise incoherent playable slots.

Procedure:

  1. Admin updates Mission Submission Template to include current generation of testing.
  2. Admin unlocks mission submission thread.
  3. Missions added to thread by mission makers.
  4. Admin uploads missions to the server.
  5. Test master confirms that missions are uploaded.
  6. Test master creates new test batch thread with appropriate info from submission thread.
  7. Test master assigns testers in the batch thread.
  8. Tester master clears admin to delete submission posts.
  9. Testing proper begins, as per testing checklist.
  10. Each tester posts a report in the test batch thread recording test history.
  11. Test master reviews test feedback, confirms or denies rejection/acceptance criteria, may at discretion test the mission himself or assign another tester. The idea is that we do not want to reject missions for false reasons, SO TAKE YOUR JOB SERIOUSLY.
  12. Test master confirms that all missions were tested by posting in the batch thread.
  13. Test master sends out messages to ALL mission makers, even those that were accepted, informing them of the status of QA.
  14. Test master posts facsimile of messages to test batch thread.
  15. Test batch thread officially signed by test master as complete.
  16. Admin moves test batch thread to archives.
  17. On discretion test master can re-open mission submission for a new generation of testing, but is only required one generation per week. The idea is that closing the thread can be used to stagger the workload, but if there is little or no workload, we might as well open it up.  

The test master functions to:

  1. Ensure that procedure does not fail; ensure the integrity and vigor of the procedure.
  2. Provide as a point of contact for all mission makers in regard to the QA process. No longer will mission makers have to ask random admins for the status of their QA requests, but may be directed to a single man responsible.
  3. Be responsible for the overall testing process, as well as ensuring that QA standards are enforced and employed.

New mission submission template:
DATE: The date of submission
MISSION NAME: What the mission is called
FILE NAME: This is normally different than the mission, we need the exact .pbo name. Please also name it something along the lines of CO37_FuzzyBunnyV4.aiaktalik.pbo. This tells out of game (on the server box) what the mission is about.
VERSION: Final Version #, we are not accepting missions that are in Beta and/or have not been tested on a dedicated server.
# PLAYER SLOTS: How many can play in game; min and Max
DOWNLOAD LINK: Where it is hosted
* BRIEF DESCRIPTION: What it is all about
TEST GENERATION: # (DO NOT CHANGE THIS NUMBER. IT REFERS TO WHAT BATCH YOUR MISSION WILL BE TESTED WITH. Record this number for future reference.)
For admin reference, test master proposals:

  1. The creation of a forum for testing, with a subforum for archiving old batches.  This will enhance our ability to establish a clear and manageable paper trail. Think long term.
  2. Your compliance with sending out a general request to those in the mission development team with the explicit request of becoming an official tester. I want men I can rely upon when assigned to perform a test. I’m not sure if mass mailing the development group is possible, but if it is, I would like to send out an official request.
  3. Making me admin of the test forum and archive subforum.
  4. Updating or allowing me to update the mission submission template everytime there is a new test generation.
  5. I will mark each testing batch thread with a date in the title