Volunteers Needed - Early Release Testing Group
-
@ssoloff also off topic but hopefully they read here since no one seems to respond in server gitter thread
I restarted the CA bots today after linode did an emergency maintenance and swapped us to a new server
can someone check their open ticket and see if anything is left to be done?
If we open a quarrel between past and present, we shall find that we have lost the future! Sir Winston Churchill
-
@prastle said:
The cursor still disappears in age of tribes round one and the production window still glitches, which can be exited and then loads properly and cursor returns.
I just came across both of these issues in WW2 classic (I haven't played much in the past 1-2 weeks), so it's not map specific. Could you please open a new issue? I'll look into it in the meantime to see if I can figure out what caused this regression.
-
-
@prastle said in Volunteers Needed - Early Release Testing Group:
@ssoloff also off topic but hopefully they read here since no one seems to respond in server gitter thread
I restarted the CA bots today after linode did an emergency maintenance and swapped us to a new server
can someone check their open ticket and see if anything is left to be done?
@prastle better topic for Gitter, the topic here is recruiting testers. Same @ssoloff about bug fix discussions, this is not the pre-release bug thread!
-
I would like to bring this issue up again about glitch reporting being done in the forum by all members.
I think you will get more feed back this way. jmho. Instead of using github to report it. Then the devs can check here and go technical there. Just a thought. Perhaps a new pinned topic in help?
-
@prastle Glitch reporting is a good topic to raise. Though despite some seemingly fond memories of how that worked in Source forge, the evidence showed some real problems. Namely bugs were not always seen in forum, not always moved, they then got lost and secondly a whole new extra layer of duplicate paper tracking was created. In the end we had 300+ bugs in source forge, most of them not useful - you'd be better off reading latest forum posts of playing the game to find something to fix than you would be reading that ticket queue to find something.
If we move all bug reporting to forum, I think that could be workable. Hybrid approach though where a human reads forums and moves issues to github is not efficient. We also basically had that recently when we moved topics from SF forum to github issues before we had this forum. It did not work so well then either... Perhaps your experience was better, but I remember spending a lot of hours doing what was basically paper tracking.
-
This topic is really about introducing a whole new role to the TripleA community. Just as we have "map makers", "map admin", "dev's", and "mods", I''m looking to add a "test" role. Essentially that role would look at early releases and report problems to the dev team. It's nice to be really efficient, and having minimized reproduction steps really helps. The idea here is we formalize this group and expectations and get it up and running.
This is a task that is really important, and it's one of those unsung hero things as it is a lot of work and it's not very glorious. On the other hand it is super useful as TripleA needs a lot of hand testing whenever anything changes, freeing up the dev's alone from having to do that multiple times a week is really valuable.
-
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.
-
@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
-
@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.
-
@LaFayette Thank you, mail address has been sent!
-
@Panther added mod invite
-
@prastle Thanks a lot! Happy to be part of it.
-
@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 .3627Just 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:3304I 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.
-
Please put build number thumbs up or down result here:
https://docs.google.com/spreadsheets/d/1CSZ4s7wBLcvgue_IHwl-CbjQd95qj8hhR8m89ngCzbU/edit?usp=sharingReport 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 : )
-
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.
-
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.
-
Thanks, @LaFayette , I think that will be a good orientation.
-
@Panther sent the invite ah nm guess ya got dans
-
This post is deleted!
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login