Page 1 of 1

Checklist discussion

Posted: Wed Apr 07, 2010 6:33 pm
by pokeman7452
We need to create a checklist of things to test. There will be 2 lists, one to be tested on every version, and one to be tested every month.
Here is what I have so far:

Release:
-Finish a level in D2:CS including a secret level.
-Finish level (TBD) of Pumo Mines.
-Finish light testing level (to be created) with standard, vertex, and PPL.
-Shoot every trigger in the basic trigger testing level (to be created).
-Test automap.
-Test multiplayer for at least 5 mins of combat.
-Browse every menu and change every value.
-Save/load a game.

Monthly:
-Finish a level in PureD2
-Test stereoscopic 3D rendering with all lighting modes and with all effects on.
-Destroy every boss in D1, D2, and D2-vertigo (level select, honestbob and almighty are ok).
-Shoot and test every trigger in the extensive trigger testing level (to be created).
-Test every cheat code, and it's effects.
-Play and finish a game in every multiplayer mode (2 levels in coop).
-Test 12-16 player anarchy.
-Test demo recording and playback.
-Save and load in co-op and anarchy.
-Save and load in a secret level.

Please post any and all suggestions and ideas you have. Try to think of things that are usually bugged easily. Monthly testing should include minor feature testing and tests that take longer than about 20 mins.

Posted: Thu Apr 08, 2010 4:29 pm
by Sirius
Save/reload
Enter secret level (probably using strategically placed savegame), test save/reload there also - might be lower priority test

On the "occasional" thing testing hi-res media would probably be a good idea. Likewise levels with special effects, custom models, briefings, etc. Demo playback is probably in the same category (although since it's easy to test it could be promoted). Definitely test multiplayer savegames in this category - it is easily broken and often is (I recall it hardly ever worked in D2 1.2 for that matter).

Posted: Thu Apr 08, 2010 4:35 pm
by Pumo
Also modding capabilities (checking if custom HAM files are working, per-mission OGG playlists, custom texts, sounds, textures, etc...) should be checked.

Posted: Thu Apr 08, 2010 5:51 pm
by pokeman7452
All good points, thanks. Although, I always play with hi-res textures and models, as do others. So I don't think there is much point in putting them on the list. I think I will change bimonthly into monthly.
I think PM is perfect for testing mods, which level would you suggest?

Posted: Fri Apr 09, 2010 2:29 am
by Sirius
If you always play with hi-res textures, someone needs to play without them too. :)

Posted: Fri Apr 09, 2010 3:53 am
by pokeman7452
PureD2 should cover that.

Posted: Fri Apr 09, 2010 11:57 pm
by Mahona
I'm to assume all of the 3D stuff will be covered in the "adjust all settings" part correct?

Posted: Sat Apr 10, 2010 1:18 am
by pokeman7452
Hmm, I forgot 3D. "change every value" means just change them, not test them. That's to look for bugs in the menus.

Posted: Sat Apr 10, 2010 5:20 pm
by karx11erx
I will try to get more involved in this next week and help you with setting up test check lists and procedures.

Posted: Fri May 21, 2010 8:48 pm
by pokeman7452
We need lighting and trigger levels and to determine a good PM level to test. Sykes and I have not played PM, so we need to know which level to learn.

Posted: Fri May 21, 2010 9:15 pm
by karx11erx
"PM"?

Posted: Fri May 21, 2010 9:59 pm
by pokeman7452
Pumo Mines