• Havoc
  • Caius
  • redboot
  • Rules
  • Chain of Command
  • Members
  • Supported Ladders & Games
  • Downloads

The Role of the Scenario Developer in H2H Testing
07-27-2012, 08:10 PM, (This post was last modified: 07-27-2012, 08:34 PM by Kool Kat.)
zicon 3  The Role of the Scenario Developer in H2H Testing
Gents: Smoke7

Please note, that as developers of H2H scenarios, once you upload a scenario for testing in the H2H area, you must stay actively involved in the testing of your scenario. This involvement includes recruiting test players, ensuring test games are registered, and staying in contact with your test player team. You, as the developer, must do your part to move your creation through the H2H process in a timely manner Write

Note - I am actively monitoring all H2H test areas... and will contact individual scenario developers (as warranted) with status inquiries. Look

Please contact me if you have any specific questions on the H2H test process or your role as a scenario developer. Smile

I've also copied and pasted the Designer's role (H2H Section) for your reference.


What is the Designer's role?
Once the scenario is moved to the main test page it is the designer's role to arrange for players to test his scenario. This is best achieved by posting for testers on the relevant forums and ensuring the testers register any tests started (see below). You will also need to liaise with your testers to see how things are progressing, every time a test report is submitted you will be notified by email, so ensure your email address is correctly displayed on your member page. The test reports can also be accessed through the scenario listing at the testing area and through the My Scenarios page.

Once you receive feedback and the current round of tests are completed, you can update the scenario file through the My Scenarios (see below) link. Taking feedback and uploading new versions of your scenario is very important to keep your scenario project moving forward.

The greatest issue the H2H Area has is designers uploading scenarios and then not fore filing their role as set out above. Not only does this create a "log jam" of scenarios on the test page it also causes extra admin work for the H2H custodians. Any scenarios found to be abandoned on the test page by their designer will be deleted and that designer may not be allowed to upload new scenarios in the future!
Regards, Mike / "A good plan violently executed now is better than a perfect plan executed next week." - George S. Patton /
Send this user an email
Quote this message in a reply
08-08-2012, 06:12 AM,
RE: The Role of the Scenario Developer in H2H Testing
Sorry Mike,

At the moment am furiously testing the new PLA version so we can proceed with the scenario's!! I can't do any more scenario testing until we are satisfied with the results. They look solid so far, so please be patient, this is a very important step!
Meine Ehre heisst Treue

Quote this message in a reply

Forum Jump:

Users browsing this thread: 1 Guest(s)