RegressionTestTable - ac-stef/AC GitHub Wiki

tests to run

  1. build and run client a) on linux 32, b) on linux 64, c) win 32, d) win 64, e) mac
  2. play a) offline, b) on public server, c) on server from same build
  3. edit a) cycle: edit, save, load map b) in coop-edit on server from same build, c)

testers (use lower case to indicate short tests, upper case to indicate extensive testing)
g: grenadier, j: jamz, s: stef,

branch (date) new features 1a 1b 1c 1d 1e 2a 2b 2c 3a 3b special feature test comments
mapmagic 8.5.2014 [xmaps]]](/ac-stef/AC/wiki/S-G --- --- --- --- --- --- --- -s- --- -[[c_15a3)
mapmagic 10.5.2014 [xmaps]]](/ac-stef/AC/wiki/s- --- --- --- --- --- --- --- --- --- -[[c_40d0)

hints

  • feel free to add yourself to the list and start testing...
  • if you run into trouble, either tell me on irc, or create an issue here, or leave a comment in the table (if you need more room than the table provides, just create a new page and link to it - name it c_#### with #### being the first few chars from the commit hash, see example)

more detailed test description (test at least this much, to indicate it as "extensive" in the table)

  1. run from existing config and at least once with no prior config (rename your existing config home directory);
    run the client and try to shoot, load maps, and throw some nades;
    check the sound;
    check the console output for error messages;
    make a note in the comments column, if you compiled a debug binary (in general, testing the debug binary is optional);
  2. a) run some bot modes, try to shoot bots with different weapons, make a headshot (use /idlebots 1, if you are in a hurry);
    b) play some games on public servers - but be aware: development clients may provide slight advantages over the last release client, so don't play competitively with it - also, at some point, the protocol may change, so that public tests will be impossible;
    c) start your own server or join one, that's built from the same sources;
    check server logs for errors;
    record a demo, view it afterwards;
  3. edit geometry (corners, solids, heightfields, raise/lower floors and ceilings), edit/add/delete entities of several types, change textures, change tags;
    check, if the changes were properly saved and loaded again;