Weekend Test - November 15th-17th

So, are we going to start testing the new version this weekend? I'm available, we just need to set up the meeting.

We still need someone with at least a bare minimal knowledge of Spring and ZK code to filter out our bugs and direct them to the corresponding developers.

Finally, I think we should focus on the engine bugs first. We need a server with the latest git version of Spring and the latest release version of ZK. We should disable all Lua scripts (as suggested by Kloot) and disregard performance issues for now. I don't know how to do this though.

Does the autolog get all our messages in-game? If so, we can report directly from the game, then retrieve the replay and ship it to the Spring devs with our infologs and sprinsettings.

Is anyone else available this weekend?

Probably, we'll lose all AI unit behavior, some effects coded in Lua (but I don't know which), and all gadgets. It will be hell, but that's what debugging means ;D

I am available this weekend. Actually setting a time will be important, otherwise the testing might go the same way as Anarchid's clan war about a month ago. I think about 5 PM UTC should be a reasonable time in most of Europe and America.

Fine by me too... depending on the day. Or do you mean all of them?

If no one volunteers, I'll try to come up with something.

I really prefer that someone with some understanding of Spring code take up the charge, though.

Although I haven't filled out the list I'll try to attend whenever I can.

I was hoping to write up something nice on a wiki page for everyone to work from, but I'm too tied up with my job to get anything written up before this weekend. But maybe I can still offer a few useful ideas in a quick-and-dirty post here.

I'd like to help out this weekend as well. I'll probably only be available for a few hours Saturday morning and afternoon US time, but while I'm online I'd be happy to help Anarchid and everyone else turn in the best QA work we can.

In addition to joining the #zktest chat channel, I suggest we use a collaborative whiteboard to keep track of important stuff during the session. The site board.net provides free real-time web-based whiteboards using EtherPad. It seems to work pretty well. We should use a board name that includes the date of the start of the group session, so for example this weekend we would use http://board.net/p/zktest-2013-11-15 - go check it out now and see what you think.

It would be very helpful for someone to post some instructions somewhere (here in this thread, or on a wiki page, or on the whiteboard above) on how to do some basic things, so that anyone can help test even if they have no prior experience with the technical side of Spring or Zero-K:

*Play a multi-player game with the latest engine
*Play a single-player mission with the latest engine
*Start a private room and play with the latest engine
*Switch from the latest engine to an older one
*Disable luaui and luarules
*Change your configuration
*Change your configuration to "safemode"
*Find a replay/demo file
*Find a infolog file

... and anything else that anyone thinks will be an essential step in helping with testing.

I've put a few other ideas in the whiteboard as starting points for anyone who wants to help test. Anyone can and should add to or modify what's there as you see fit.

Thanks, good luck, see you Saturday, and happy hunting everyone!

should we have multiple test room, each have 2-4 member testing different things?

It seem like a waste of resource to have 5-10 people sitting in the same room, seeing the same thing.

Guys, there's a problem. Currently ZK is running older ZK (ZK 1.1.8.2) which is rebranded as ZK 1.1.11.11 for desync debugging. This is an unexpected event.

For actual latest ZK you guys must use "Zero-K test-12069" or the recent most stable ZK for Spring 95: "Zero-K v1.1.11.9"

If you guys can make the Bleeding Edge room to spawn this version, then its not a problem. :)

For those not living in scientific underdeveloped countries who can't keep what those am/pm things mean (like me) look here for a translation (enter your place or timezone abbreviation).