Thread: CSS Testing Checklist

This is the same checklist as TF2. Since CSS still uses a different game engine from TF2 (or now DoD) there is the possibility that some of these might not work. Thus we must test everything we tested in TF2.

I am not a CSS admin nor even a player so I am a little in the dark here. I will do as much as I am able but I am going to look to Panic to help me since he is much more familiar with the game.

The list:

• Make sure the admin menu pops up using the command ls_admin_menu
• Make sure the admin menu pops up using the chat command "adminmenu"
• Kick someone from the admin menu
• 1 hour ban someone from the admin menu, and make sure the ban sticks for exactly one hour
• Permanent ban someone from the admin menu, and make sure the ban sticks for a day (then remove the ban using rcon)
• Use ls_ban to ban someone for 1 minute and make sure it sticks
• Use ls_ban to ban someone permanently and make sure it sticks (same as above)
• Use ls_tempban to ban someone for 1 minute and make sure it sticks
• Use ls_tempban to ban someone for 2 hours (120 minutes) and make sure it sticks
• Use ls_tempban to ban someone for 3 hours and make sure it FAILS
• Use ls_tempban to ban someone permanently and make sure it FAILS
• Use ls_kick to kick someone
• Use ls_reload_configs to make sure changes in admins.txt are applied (admin->reg and reg->admin)
• Use ls_reload_configs to make sure changes in reservists.txt are applied (reservist->reg and reg->reservist)
• Use ls_reload_configs to make sure changes in mapcycle.txt are applied
• Change the map to make sure changes in admins.txt are applied (admin->reg and reg->admin)
• Change the map to make sure changes in reservists.txt are applied (reservist->reg and reg->reservist)
• Change the map to make sure changes in mapcycle.txt are applied
• Configure the server to have 8 reserved slots (so only 2 public slots), and get 4 people to make sure that (1) non reservists are rejected properly, (2) reservists can get on, (3) admins can get on. You need to do different combinations to prove it's really working. Like all admins, all reservists, all regs, 1 reservist 3 reg, 1 admin 3 reg, 1 admin 1 reservist 2 reg, etc
• If an admin doesn't have power "config" he cannot use "ls_reload_configs", and if he does he can
• If an admin doesn't have power "kick" he cannot use "ls_kick" and the kick option does not show up in his menu
• ls_ban only works when you have the "ban" power. Make sure that if the admin has power "tempban" but not "ban", ls_ban does not work
• ls_tempban only works if you have the power "ban" or "tempban".
• The permanent ban menu option only shows up when you have the "ban" power. Make sure that if the admin has power "tempban" but not "ban", the option still doesn't show up
• The 1 hour ban menu option only shows up when you have the power "ban" or "tempban".
• Make sure the player menu pops up using the console command "ls_player_menu"
• Make sure the player menu pops up using the chat command "menu"
• Make sure the map information in the player menu is accurate
• chat command "nextmap" works and seems to be accurate. Change the maps to verify this. Edit the map timelimit to 5 minutes so it will rotate on it's own so you can observe it naturally as well
• chat command "stopmusic" works
• chat command "timeleft" works
• admin chat works (when an admin does team chat with @)
• got chat works (when an admin does normal chat with @)
• admin pm works (when a non-admin does normal chat with @). Make sure the player sees his special chat message ("Sent to Admins: message") and the admins see the PM ("To Admins: player: message")

That's all I thought of for now. If you notice something missing, post it up and I'll add it.

Originally Posted by Arreo

• Make sure the admin menu pops up using the command ls_admin_menu
• Make sure the admin menu pops up using the chat command "adminmenu"
• Kick someone from the admin menu
• 1 hour ban someone from the admin menu, and make sure the ban sticks for exactly one hour
• Permanent ban someone from the admin menu, and make sure the ban sticks for a day (then remove the ban using rcon)
• Use ls_ban to ban someone for 1 minute and make sure it sticks
• Use ls_ban to ban someone permanently and make sure it sticks (same as above)
• Use ls_tempban to ban someone for 1 minute and make sure it sticks
• Use ls_tempban to ban someone for 2 hours (120 minutes) and make sure it sticks
• Use ls_tempban to ban someone for 3 hours and make sure it FAILS
• Use ls_tempban to ban someone permanently and make sure it FAILS
• Use ls_kick to kick someone
• Use ls_reload_configs to make sure changes in admins.txt are applied (admin->reg and reg->admin)
• Use ls_reload_configs to make sure changes in reservists.txt are applied (reservist->reg and reg->reservist)
• Use ls_reload_configs to make sure changes in mapcycle.txt are applied
• Change the map to make sure changes in admins.txt are applied (admin->reg and reg->admin)
• Change the map to make sure changes in reservists.txt are applied (reservist->reg and reg->reservist)
• Change the map to make sure changes in mapcycle.txt are applied
• Configure the server to have 8 reserved slots (so only 2 public slots), and get 4 people to make sure that (1) non reservists are rejected properly, (2) reservists can get on, (3) admins can get on. You need to do different combinations to prove it's really working. Like all admins, all reservists, all regs, 1 reservist 3 reg, 1 admin 3 reg, 1 admin 1 reservist 2 reg, etc
• If an admin doesn't have power "config" he cannot use "ls_reload_configs", and if he does he can
• If an admin doesn't have power "kick" he cannot use "ls_kick" and the kick option does not show up in his menu
• ls_ban only works when you have the "ban" power. Make sure that if the admin has power "tempban" but not "ban", ls_ban does not work
• ls_tempban only works if you have the power "ban" or "tempban".
• The permanent ban menu option only shows up when you have the "ban" power. Make sure that if the admin has power "tempban" but not "ban", the option still doesn't show up
• The 1 hour ban menu option only shows up when you have the power "ban" or "tempban".
• Make sure the player menu pops up using the console command "ls_player_menu"
• Make sure the player menu pops up using the chat command "menu"
• Make sure the map information in the player menu is accurate
• chat command "nextmap" works and seems to be accurate. Change the maps to verify this. Edit the map timelimit to 5 minutes so it will rotate on it's own so you can observe it naturally as well
• chat command "stopmusic" works
• chat command "timeleft" works
• admin chat works (when an admin does team chat with @)
• got chat works (when an admin does normal chat with @)
• admin pm works (when a non-admin does normal chat with @). Make sure the player sees his special chat message ("Sent to Admins: message") and the admins see the PM ("To Admins: player: message")

That's all I thought of for now. If you notice something missing, post it up and I'll add it.

The server has no password as of yet.

None of the chat commands (in red) are functioning, the crossed off are fine.

all chat commands are confirmed broken on CSS at the moment. Once their fixed, I'll repost in this thread saying such and we can test them.

I'm not a cs admin; but if you guys need a ban dummy, let me know on steam friends.

Originally Posted by AsO|-Special_K_33

I'm not a cs admin; but if you guys need a ban dummy, let me know on steam friends.

You're probably already an admin on the test servers. Test servers are separate from the public ones.

In fact, I was wondering if I could get mid status on the test servers to test shit that I wouldn't otherwise have access to. Might shave time off everyone's schedules.

done for CSS (your now a "high")

For testers, we do not preserve the "low" "mid" "high" distinction that occurs everywhere else at TTP. Testers are testers and so they have to be able to test every power level.

If you ever need your test server powers tweaked (powers added or removed), either Arreo or I can do it.

Originally Posted by Ewok

all chat commands are confirmed broken on CSS at the moment. Once their fixed, I'll repost in this thread saying such and we can test them.

Chat commands now work

Apparently "hud text" (the text in the middle of the screen when you do god-chat in tf2) is not implemented in CSS or DODS. As LoneStar doesn't implement it (it simply uses it), it means that we can't get hud text in CSS or DODS.

As an alternative, I'll have lonestar use the old-style screen text that mani used which puts it in the top-left corner. LoneStar will use this as a fallback when it's being run under CSS and DODS. I'll post again in this thread once it's implemented and needs testing.