Volunteers Needed - Early Release Testing Group

Panther

In my activity I am focussed on GitHub and axisandallies.org, so I am not a frequent user of forums.triplea-game.org, as I must admit.

However, I am updating TripleA at least once a day and I am always using the latest (pre-) releases. I feel like already filling out the "test" role, as I regularly post bug reports / issues on GitHub. Honestly, I am not a fan of bug reporting to a (another) forum - as we do have those github issues for it.

During the past years I have helped out many players who had issues using TripleA. Not all issues are bug-related. So - if needed - I could help sorting out aspects that could be answered "quickly" on the forum from issues that should be moved to GitHub. Just an idea, of course...

Anyway - in case my activity can be of any help in the context of this thread, please let me know.

prastle

@LaFayette Np was just an idea. Sadly tho many will probably not report bugs on github . So hopefully the test group idea will take off. Also sounds like @Panther is in

LaFayette

@Panther Thanks! In the past you've done a great job testing, this updated process should hopefully feel pretty familiar. PM me your email address, I'll add you to the testing spreadsheet.

Panther

@LaFayette Thank you, mail address has been sent!

prastle

@Panther added mod invite

Panther

@prastle Thanks a lot! Happy to be part of it.

prastle

@Panther @LaFayette
.6242 in lobby quick test with champ = BW42v3 had 0 errors so far as well as revised
v341 seems fine as well except another java error on my side ... he was using .3627

Just still has the chat error when joining but chat worked fine as well as hosting.

triplea.engine.version.bin:1.9
Aug 23, 2017 9:43:55 AM games.strategy.engine.chat.ChatController joinChat
INFO: Chatter:prastle port:3300 ip:24.53.232.198 is joining chat:games.strategy.engine.framework.ui.ServerStartup.CHAT_NAME
host:45.79.144.53 port:3304

I will say it is annoying having to manually unblock the downloaded file in order to install it in windows ten. As well as having to then create a new file folder for the prerelease and bypassing the windows firewall manually.

LaFayette

Please put build number thumbs up or down result here:
https://docs.google.com/spreadsheets/d/1CSZ4s7wBLcvgue_IHwl-CbjQd95qj8hhR8m89ngCzbU/edit?usp=sharing

Report any error messages to github issues.

Let's get a gitter room spun up as well. Please check here for access to gitter, we may need to add people as contributors (ron would have to do that). Check here first: https://gitter.im/triplea-game/social

Additionally, we could use a name for the 'tester group', calling us 'tester' and 'testing' is a bit lame : )

LaFayette

Here is the gitter room: https://gitter.im/triplea-game/QA, please join it

On the tracking sheet, if you mark 'buggy' it means we found a major problem. It's not clear to me if we fixed them, it maybe worthwhile to put issue numbers so we know when we fixed them all.

LaFayette

A test plan seems valuable and as would some expectations.

When testing I think we should look at the latest game as-is, report anything that could or needs to be improved. We need to take a fresh look at the game when we do this and make sure the game would work well for someone that is completely new to it, and would also work well for veterans that use shortcut keys where available.

When testing we should focus on noteworthy changes/areas, anything that has been added or overhauled. Then proceed to regression testing where we check every feature in the game. For anything we find, we should indicate it if it is a 'major' problem, otherwise it can be assumed to be fixed in the next release, in a few days.

Panther

Thanks, @LaFayette , I think that will be a good orientation.

prastle

@Panther sent the invite ah nm guess ya got dans

Panther

This post is deleted!

prastle

@Panther https://gitter.im/triplea-game/QA

Panther

@prastle Yes, I'm in, thanks.

prastle

@Panther check youe email for direct link

prastle

Great !

prastle

@panther and @all the new test lobby is located here

45.79.107.98 port 3304

Some bots are being moved there which will use the 1.9.0.0.6454 pre release

Anyone that wants to use the test lobby just download the latest pre release engine and install to a NEW! folder dont overwrite your current stable. Then open engine preferences and under the testing tab change the ip and port.

LaFayette

@prastle lobby upgrade will likely precede the game client, the test lobby can (should) be checked against the current version

prastle

@lafayette ok
I will ask @roiex to switch them back or do you just want them closed? We were mainly using them to test trains but could not install the map to the bots using filezilla.