[Goober5000]

With the SCP team getting ready to release 3.6, we're in need of a few dedicated testers who can put our programs through their paces.  It's hard for us to test by ourselves, because we have a limited range of hardware and in any case it's often hard to tell what users will do with the SCP, since we're working within our own assumptions.

We'll also in need of a testing coordinator who can rebuild the tester list and who will be given the responsibility of managing the list long-term.  This way, every time we want to implement a new feature, we'll have a ready-made list of people we can contact, and we won't have to run all over the place looking for people to test (or worse, release a buggy feature).

So who's interested in signing up?  The more testers we get, the more time we can devote to doing what we do best (coding new features and fixing bugs) and the quicker you'll see 3.6.

[Flipside]

I'm willing to lend a hand with testing, TI uses some pretty Engine stretching stuff, so I can just test my models/experiments and the build at the same time

Flipside

[Taristin]

I could always put some of my models in the same mission, to see how it'll run on a low-end system.

[Rga_Noris]

Hrm... I know I'm new, but I think I might be able to manage the list.
I was thinking the list could be maintained by a sticky thread. I would just edit it to make changes.

The info it would include would be:

the tester
Contact info (AIM,ICQ, and obviously e-mail)
Computer info for all the computers that the tester has access to. (Proc type and speed; RAM type, amt, and speed; Vidcard type and RAM; Soundcard; controllers;)
FS2 info (build of FS2_Open, MODs)
Current Test (A list of what features they are already testing)
Full: (Yes or No. This would determine if the tester has time to take on more, so testers dont accidently get overloaded and the workload can be spread)
Any special comment (Such as 'need help' or anything else)

The last three would require a close amount of cooperation between myself and the testers, but I think it would be important so we know who's doing what at all times, and if they are available to do more, or if they want help.  Testers could just e-mail me the information and I could compile/update the list depending on what they need. Sound good? Is my assuming that is what you need correct?

[Unknown Target]

I have a couple high-poly, no-LOD ships I could try out, some tabling junk, decal support, etc. I could do some testing (I could test the new multiplayer [I have DSL], and the multiplayer mod support)

[Goober5000]

Originally posted by Rga_Noris
Sound good? Is my assuming that is what you need correct?

Yes, exactly.  What we need is a list of people who we can turn to that we know will be available.  We don't want people to volunteer to test something once and then disappear off the face of the earth.

Rga_Noris, you seem to have a good grasp on what we want.  Would you be able to keep the list updated, with emails and whatnot?  It doesn't have to be posted on the forum (since it might get in the way) but it should be as up-to-date as possible.

[Taristin]

*is always here, atleast for the next couple of months*

[RandomTiger]

Thankyou to the people signing up for this, you will be hearing from me soon I imagine. You might want to get yourself a mantis account so you are ready to report bugs that cant get fixed straight away.

This *is* really important, we really need as many testers as possible.

[Rga_Noris]

I would be happy to manage the list. Would this list be something that I would e-mail to developers upon request?

Let me know, and we could direct volunteer e-mails to my e-mail addy and I will compile a list.

[Goober5000]

PM sent.

[RandomTiger]

Make sure you start with a fresh list.
The current tester list is worthless.

[Rga_Noris]

Alrighty. Goober5000 has given me the greenlight.

For those that wish to be beta testers, please shoot an e-mail to [email protected] , as is linked in my profile. Please include the following information in your message in the following format:

Name:
Contact: [E-mail, ICQ, MSN, however you prefer to be contacted]
Computer Configuration:
Processor: [Type] [speed] [Frontside bus if know]
RAM: [Amount] [Type]
Video Card: [Type] [Amount of video RAM] [Driver Version]
SoundCard: [Type]
Controllers Used: [Joysticks, Gamepads...]
FS2_Open builds available: [version number]
Fred builds available: [version number]
Media VPs available: [version number]
MODs: [name and version]
Current Test: [author, name, version]
Full: [Yes or No. To determine if you are available to take on more projects]
Any special comment: []


Here's an example:
Name: Rga_Noris
Contact: E-mail: [email protected]
Computer Configuration:
Processor: Pentium 4 2.4Ghz 800Mhz FSB
RAM: 512 DDR433
Video Card: Radeon9800pro 128MB; Drivers: Cat 3.6
SoundCard: Sb Audigy 2ZS
Controllers Used: Microsoft Sidewinder Precision Pro 2
FS2_Open builds available: 01_20_2004
Fred builds available: 01_20_2004
Media VPs available: 3.5.6c, 3.5.5
MODs: none
Current Test: Bobbeus Decals version 1.2
Full: No
Any special comment: I'm not quire full yet, but in the next few days i'll be a little busy, so things might be a little slow.
-----------------------------------------

Anyway, for anyone wanting to beta test, Thanks! As others have said, any help is appreciated and works towards making a great project even better.

A few more things:
UPDATING YOUR LIST STATUS: Once you are on the list, just shoot me an e-mail with any information that needs to be changed or added. You only need to include the information in question. Once you have done so, I will update the list with the appropriat information, and send you your entry back so you can verify that all information is correct.

DEVELOPERS: Just e-mail me for the most current version of the list. I'll have one ready as soon as I recieve emails. Thanks for your hard work!

TESTERS: Please remember that it is up to you to send me information. Also, developers might decide they need more information than the current format model ask for, if so, I will send out an e-mail requesting the info. Other than that, thanks again, and happy bug hunting!

And I need some input: Would we prefer that everything be handled through me, ie Developers tell me who they would like to test, then I e-mail the testers asking them if they are available? This way there is less room for errors within the system. If you would rather that the devs just go straight to the testers from the list, and we leave it up to the testers to inform me of any changes, that is alright too, both can be done. I like the second option because it would strengthen communication between Dev+Testers, so I'm open to either.

--Rga

[RandomTiger]

Originally posted by Rga_Noris
And I need some input: Would we prefer that everything be handled through me, ie Developers tell me who they would like to test, then I e-mail the testers asking them if they are available? This way there is less room for errors within the system. If you would rather that the devs just go straight to the testers from the list, and we leave it up to the testers to inform me of any changes, that is alright too, both can be done. I like the second option because it would strengthen communication between Dev+Testers, so I'm open to either.
 

I'm very impressed with your attitude to this so far, this is good.
However, the way I see it working is, testers test official or specially noted builds only (unless they are bored in which case they can test as much as they want). This general testing could probably work through you as the lead QA or whatever you want to be known as.

The other part should be that if a coder needs to he can contact a tester (or a small group) with a certain spec to test a certain feature or to try and replicate a certain bug. This really requires the coders to talk directly to the tester, although we could cc everything to you aswell.

I opinion is, dont wear the testers out doing general testing all the time. People only have so much time for this and in the end anyone can do general testing. What the list is useful for is locking down specific problems.

Thats my opinon anyway. BTW I set up the original tester list It worked nicely until I went away for a month or two. It was damn useful so I would love to see it back again in some form.

[Rga_Noris]

Originally posted by RandomTiger


I'm very impressed with your attitude to this so far, this is good.
However, the way I see it working is, testers test official or specially noted builds only (unless they are bored in which case they can test as much as they want). This general testing could probably work through you as the lead QA or whatever you want to be known as.

Hmmmm... I think "Grand QA Poomba" would fit. Or just QA Manager

The other part should be that if a coder needs to he can contact a tester (or a small group) with a certain spec to test a certain feature or to try and replicate a certain bug. This really requires the coders to talk directly to the tester, although we could cc everything to you aswell.

[/B]

CC'ing stuff to me would be perfect. I just want to avoid any errors in the list, and keep it as accurate as possible, without becoming the QA Nazi.

I opinion is, dont wear the testers out doing general testing all the time. People only have so much time for this and in the end anyone can do general testing. What the list is useful for is locking down specific problems.

Thats my opinon anyway. BTW I set up the original tester list It worked nicely until I went away for a month or two. It was damn useful so I would love to see it back again in some form.

[/B]

And that's a good opinion. If the developers needed a tester for every little thing, we'd prolly waste of time.

So I guess the only thing I ask regarding the list is that when a dev communicates with a tester, just CC e-mails or e-mail me if any of the required list information changes.

Thanks again, I'm going to enjoy this!

--Rga

[Turnsky]

*raises hand*

[Lightspeed]

Hmm... *goes to email*

[RandomTiger]

Lightspeed is virtually a whole tester list by himself!
Did you get that debug exe?

[Flipside]

Meh, Pipex' mail server is down.... yet again.
I'll Email you as soon as they get their sorry butts into gear and fix it.

I think one problems that needs to be addressed is that a fair percent of the problems encountered by people on the board are on models that are in campaigns etc. A lot of people don't want to show their ships to the community yet because they'd prefer to wait till the campaign comes out, so it leaves them a bit stuck as far as reporting the problem accurately with files/screenshots is concerned?
So if theres no 'safe haven' where people can send their files and know that only SCP coders can see it, they are left to describe the bug etc, but not provide something that may be vital to fixing it.

Flipside

[Taristin]

Originally posted by RandomTiger
You might want to get yourself a mantis account so you are ready to report bugs that cant get fixed straight away.
 

You might want to get mantis to send me an email confirmation.

Or is it Hotmail thinking it's spam?

[RandomTiger]

hotmail does let the confirmation e-mail though.
Contact Goober