What are we up to?

[Steel Mirage]

Thanks 4Star, that would be helpful to us all.

@Renegade: I was headed in a more more meta-question direction with my spiel up there. I don't think the problem is people playing with Ares, I think the problem is that people look at Ares and say "Holy shit, there's a metric fuckload to possibly test, how can I as just one tester hope to ever put a dent into things?"

My solution would be to set up a resource that would help tester set up their own program so that they can set goals for themselves without feeling like they're completely overloaded. To wit:

1. Does feature X work as intended?
2. Does feature X integrate properly with the rest of Ares?
3. Is Ares as a whole still stable?

To me, this looks like a case of "because it looks simple it should feel simple". Unfortunately, because of the scope of Ares, grand strategy simplicity just doesn't translate into trench tactics.

I think what the testers are asking for is a place to start. And as developers with your above stated objections to directed testing, that not only isn't gonna happen, it would actually be bad if it did happen.

Thats what I am hoping the Testers understand.

But that still leaves the testers without something to cling to, without a place to start for themselves.

My idea revolves around a set of simple questions and procedures that the individual testers could answer and follow for themselves, and generate a unique and random chain of testing.

Example:

Code:

1. Do you know how to test?
If yes, then go to 2,
If no, then go to IRC and make ready to use your ears (or something to that effect.  4Stars video would also be handy).
2.  Do you know what you want to test?
If yes, then get to work,
If no, then go to 3.
3.  Are you familiar with the game?
If yes, then go to 4.
If no, then just play the game for a while and come back later
4.  Are you familiar with rulesmd.ini?
If yes, then go to 5.
If no, then familiarize first and then go to 5.
5.  Are you familiar with the manual
If yes, then go to 6.
If no, then familiarize first and then go to 6.
6.  What kind of feature do you want to test

?
Etc, etc, etc.

Typing that literally took me about three minutes, following it takes even less time, and it gives new and old testers a place to start asking themselves questions.

I see the options for step six being unit types, sw's, building types, etc... This would give a tester a place to focus and then they can go from there.

Its this kind of Socratic questioning that not only gives testers a place to start from, but also starts building analytical competence into the testers process.

Thats where I was headed with that last wall o' text.