Ricebug on 23/7/2013 at 13:07
Each time I do a FM, I try different things during the beta-testing phase. For instance, I do a post that says, "All Mission One Comments Go Here." Invariably, however, things sooner or later start falling off the grid and I feel like a one-legged man in an ass-kicking contest.
I was curious how other FM authors manage this part of the process.
Couple of things I've learned to do:
1. Copy/paste everything into a hard document. Line out each finding as I fix it.
2. Do detailed reports and post them for the beta team so they know I've at least acknowledged them.
3. Explain why I'm not fixing something, in the rare case that it happens.
4. Update the mission files when everyone has posted their feedback.
5. Keep PMs to an absolute minimum.
MysteryMan on 23/7/2013 at 13:18
Quote Posted by Ricebug
Each time I do a FM, I try different things during the beta-testing phase. For instance, I do a post that says, "All Mission One Comments Go Here." Invariably, however, things sooner or later start falling off the grid and I feel like a one-legged man in an ass-kicking contest.
I was curious how other FM authors manage this part of the process.
Couple of things I've learned to do:
1. Copy/paste everything into a hard document. Line out each finding as I fix it.
2. Do detailed reports and post them for the beta team so they know I've at least acknowledged them.
3. Explain why I'm not fixing something, in the rare case that it happens.
4. Update the mission files when everyone has posted their feedback.
5. Keep PMs to an absolute minimum.
1. I have an
On Going Fix List that is locked so I can mark off everything that has been reported.
When all of the beta's have been tested, the obvious problems have been fixed. Then comes the pre-release edition, so that a run through can be checked against the fix list.
2. I let all of the testers create their own threads for their reports, for each phase of beta testing, then lock the old ones as the new beta's progress.
3. I am consistently repairing between betas, and always stay ahead of the testers if possible. This makes it less tedious on everyone, and makes the testing go quickly.
bbb on 23/7/2013 at 19:47
Great question.
I keep a squential word doc of all comment from testers (I use bullets for each point). I list out who the comments are from and the date on each heading. I then put my remarks below each comment (list the change I made if I made one, note that I will pass on the change, etc.). When I issue a new release to testing, I also issue the latest word doc as well. That way the testers can see what I changed/did not change. It works for me in that it keeps me organized, especially if you have good testers who notice even little issues. ou can be dealing with a lot of comments.
BBB
LarryG on 23/7/2013 at 21:29
* I use a forum @ shalebridgecradle (Thanks Dussander)
* I create a "Welcome To My Beta Test" thread where I thank my volunteers for their help and lay out my ground rules to keep everything organized:
Quote:
I just want to take a second and thank you for helping me with my mission.
Don't hesitate to tell me what you don't like. I want to hear it. I may not agree with everything you say, but I promise to listen and think about it. And if a couple of you join forces, I'll really listen hard! If you have a suggestion to make the mission better, please let me know. If you like something, I'd like to hear that too, but that's just to stroke my ego.
I have set up a
Beta01 Comments thread for the first Beta version. Use it in discussing and reporting on this mission. I have also set up a
Beta01 To Do List thread where I will report on my progress in responding to the issues you have raised in the Comments thread. I will establish fresh Comments and To Do List threads for each subsequent version in order to keep it clear which comment pertains to which version. I also will establish other threads as needed (such as Hints and Loot List) to keep those topics from cluttering up the Comments threads.
If you are new to testing, new to this forum, or just want a little refresher on the forum or about testing, The FAQ has a lot of good information. The section starting with Can I be a beta tester? is particularly worth a read.
Anyhow, thanks again. I really appreciate your help in getting this mission ready for release!
* As the beta testing progresses on each build, I scan the testers' comments in the
Betaxx Comments thread, and pull out all the actionable items to the build's To Do List on an
Open Items post.
* As I complete items on the
Open Items post, I move them to a
Closed Items post. ("This thread is for all reported items which I believe are resolved in the next Beta version." This keeps my progress visible to the Beta testers and minimizes them re-reporting things that I have already fixed for the next build. (I don't mind multiple reports of the same items if I haven't fixed it yet; that gives me an informal sense of how glaring the issue is.)
* When a new Beta version is ready, I open a new
Betaxx Comments thread, with it's own welcome post, such as:
Quote:
Use this thread to report issues and ideas for Betayy.
Please confirm closure on the Betaxx (and earlier) Closed Items.
I've modified the blended game interface screens a little more. Some of the objectives weren't looking right on mission failure. Please take a look at all the screens (loading, objects, map, &tc.) and let me know if you think they are all OK.
And please recheck the readme. I couldn't help but fiddle with it.
And check that all the banners cut properly! :oops:
UPDATED with new interface files (sound and stats) and new keeper doors. Please make sure I didn't screw them up trying to keep the blocking brush from showing.
Download at:
* I also open a new
Betaxx To Do List thread and copy all remaining open items from the prior beta's To Do List
Open Items post, so that they don't get forgotten about.
* As the Foreign Language folk volunteer, I create separate threads for language-specific comments. I try to have at least 3 translators for each language so that they can resolve all of the tricky translation bits by consensus rather than relying on any one individual to understand what is intended everywhere.
That's about it.
R Soul on 23/7/2013 at 21:30
I use the beta testing forum at the Southquarter.
I tend to have a thread for each type of problem (sounds, textures, plot, technical bugs). I also have a stickied thread which serves as my to-do list (bugs to fix, things to add etc). For the current beta version, items start off red, become orange while I'm working on them, and become green once they're done. Anything that won't be done gets a line through it (for good reason I might add).
For some issues (e.g. ones that require a bit of discussion), I'll start a new thread for it.
Another thread I have is one for the latest version.
Things do end up in the wrong places but as long as I keep the to-do list up to date, it's not too hard to keep track.
I also have a Hello thread and another one for people to say if they suddenly find they won't be able to test.
Xorak on 24/7/2013 at 02:41
Wow I feel like a newb. haha
I have everyone post in one thread and then I fix any problems they encounter, while also playing through several times myself and spotting things the testers never did.
Ricebug on 24/7/2013 at 03:38
Quote Posted by R Soul
I use the beta testing forum at the Southquarter.
Really? First time I was aware they had one.
R Soul on 24/7/2013 at 20:01
It is in fact shalebridgecradle that I use. I probably confused it with southquarter because I see that link each time Brethren posts.
john9818a on 25/7/2013 at 16:05
I use shalebridge as well and keep a seperate thread for each beta. As testers post their comments and bug lists I make corrections to my FM ASAP so I don't have to spend much time going back through a long list of posts and bug reports. After each update I quote each tester's comments with my responses and indications of fixing or intent.
