8 replies to this topic

[Anthus]

So when you are testing a quest for someone, how do you like to go about it? Do you want to just jump in, and play it like a regular quest, and find bugs along the way, or are you strictly business, and wants maps/ details about what you are testing to make it a more streamlined process?

[The Satellite]

Blind is usually the best way, of course, if you don't know where to go, a guide would be nice, but otherwise, back when I did test, I did so blindly; it was much easier to find bugs that way. And more fun.

[Ica]

I don't think I will vote for either because I rather try to find the items myself and explore first, and then use maps and etc. to find the rest and test the entire game. Of course it is best to utilize the second method if one does not possess much free time, as it is more objective, but I rather play a beta as a real quest as opposed to a chore.
But hey, what do I know?

[nicklegends]

Maps and guidance are probably most useful for the questmaker seeking feedback, but playing blind is usually more fun.

[MoscowModder]

Playing 'blind' is a more realistic test scenario.

'Nuff said.

[SUCCESSOR]

I don't see any benefit to blind testing. I see potential for hindrances. Especially if the quest is in early development. Trying to figure out where to go and what to do on top of testing is just a needless complication.

Edited by SUCCESSOR, 22 November 2012 - 06:30 AM.

[Anthus]

Thanks

I agree that playing blind is more fun, and realistic. But I suppose it does depend on the status of the beta in question whether or not maps or guides would be appropriate.

For example, if people tested my project, they'd really have no idea where to go because the areas only connect to each other for the sake of testing travel, and do not reflect how they will connect in the final game . In reality, playing this would probably be boring, and unrewarding, unless you were solely playing to test.

[Eddard McHorn Van-Schnuder]

Playing 'blind' is a more realistic test scenario.

'Nuff said.

Yes, when you're a gamer. But when you're a beta tester, playing blind is 'wrong'. It depends on the level of professionalism you want to go for, but if you wanna do proper beta testing, that means playing the game in a way that's not the least bit fun - unless you like walking around actively trying to break the game. Cause that's your job as a tester.

Maps and details should be a given, though it might not be a bad idea to do a blind run before really diving into the testing, just to get a feel of the game.

Real testers are often given one specific area that they'll be working in for weeks, and the most I've talked to have never actually played a game they're beta testing all the way through until it was released, simply because that's not what you're supposed to do as a tester. A lot of people think their job is sitting around playing video games all day - and it is, but it's a lot less fun than it sounds like. Obviously I wouldn't expect people on here to test with the same level of professionalism, but as a quest maker, I'd never want to have a beta tester who simply wants to be one so he can enjoy the game.

So when THP testing comes around, keep that in mind if you wanna test.

[DarkFlameWolf]

I suggest a approach that caters to both. Supply the testers with the necessary guide and maps to properly navigate, but leave it to them to do it blindly and give them the option of utilizing the resources you've given them.