Scenario Testing

[Mr Grumpy]

I was only writing about scenarios that sit in the H2H section. If they are small, untested, and unsupported why not just purge them "from the H2H testing" area, after a set amount of time?
I would give the larger ones more time because they take more time. Unless the designer is not involved.
Seems that Foul has a list of those that are being played and by whom?

Ed, indeed i do purge 'deadwood' scenarios after maybe six(ish) months and would do this more often if the test page needed space freed up (only happened once at CM), the new H2H will automatically delete scenarios after a set period unless the designers respond to a automated email (just like bootcamp) this will free me from this chore and keep only active designers scenarios listed. :)

The largest problem with the H2H area is in communication. If scenarios are "dumped" there and expected to be tested but, they do not draw "flies", why should they take up slots?
My idea on purging was from the thought that scenarios were uploaded to "H2H" without being supported and/or promoted by the designer.

I agree 100%, certain designers (on all ladders) are uploading their scenarios to the test area and then expecting them to be tested without any leg work, this is the number 1 headache for myself and the reason a designer is restricted to only 3 scenarios at any one time.

Early on I thought the H2H area was autonimous and that the head of H2H would be there to shephard or purge the designs. After my experience with mwest and testing I see how it works. I think designer involvement and communication is key.

Indeed after the outstanding success of mwest how could anyone involved doubt the system can work at CS? Mike was active in finding testers and analysing the feedback quickly and using the forum to obtain extra info and ask opinions, he then quickly produced a updated version and tested again, he also liaised with myself when a test had log jammed his progress, the result was two approved scenarios and i believe the testers had a lot of fun and Mike had the satisfaction to see his project completed in good time.

The whole of the H2H is designer driven, they are key, you can improve the H2H area and even offer masses of points to testers, but if the designer is not prepared to put the effort in the whole system just wont work in my experience. ;)

I'm honestly not being sly here. I just had "the light go on" and now see the benefit of the H2H testing area.
RR

Thank you Ed that is sooo good to hear because i feel like i have been banging my head against a brick wall for some time not feeling like i was making progress, i really hope the CS area can get involved with the H2H area as it can be a heck of a lot of fun and very rewarding :)