Beta testing advice?
Bad wolf Guy
Member Posts: 206
Really new to this beta testing, was wondering what do you do or get people to look for when testing your game.... Besides bugs.
Do you ask them sets of questions or is it just feedback of what they feel they should mentioned.
Is there a way that's worked well for you that could help me?
Do you use people who you don't really know or friends or people from GS community!
Many thanks
Do you ask them sets of questions or is it just feedback of what they feel they should mentioned.
Is there a way that's worked well for you that could help me?
Do you use people who you don't really know or friends or people from GS community!
Many thanks
Comments
Personally I use a mixture of friends and the community, around a 50/50 split. To manage beta testing I use https://testflightapp.com As not only dose it allow you to track who is installing the updates it keeps it easier for the beta testers who are not so technical.
I tell my beta testers that any feedback is useful and greatly appreciated, and with each release I often ask a few questions about aspects that i am looking to improve. Such are the adverts too frequent.
Developing games I have also found that sitting next to my 5 year old cousin while getting him to play it is invaluable as you really get to see what makes sense to the user and not. He can play the a lot of games on the app store without needing to ask what to do, like doodle jump or angry birds. So if he asks me what he needs to do, that normally means it is not clear enough and needs some tweaking. For example I have vastly changed the tutorial on one of my games from what was just text to getting the user to actually do it with a few on screen overlays for pointers.
Hope that helps
siwel : )
1.0.0 is the starting, then it's 1.0.1
Now having young kids test it all the time helps alot, I do it throughout the whole development.
So when I reach 1.1.0 or 1.2.0 ect means thats time for the young ones to test it.
They are screen recorded while playing through the game. This let's me know and shows when something wrong is occurring. Very helpful.
It also shows me what is confusing about the game. Are the buttons in the correct order and position for a more easier friendly way. It also helps with what needs to be added ect. As well I also get a ton of feedback. All of which is bad and I love it. It tells me I am doing it wrong. It's not appealing enough.
So with this new information I go and I do a other ten updates with new tweaks and features and repeat again.
By the time I reached 1.2.0 I get teenagers and adults to have ago. Their feedback is not as good but they do mention straight forward things such as the colours don't match. I don't k ow how to play. And of course making it easier to use.
I am now at 3.0.0 and I still get them to test. No so much for bugs an such but ways to make it better. The younger ones went from 1.1.0 saying it's bad and saying nothing nice to 3.0.0 where they actually say I like what you have done with that good job. It makes it worth it that at least some are enjoy playing. Which as a developer is my main goal.
However, this is my second major project. My first when didn't make it to the end. And I look back now and i think thank goodness it didn't. During that time I didn't take thier ideas and feedback seriously. I had a vision and I was going to stay with that. Finally I got them to play and the truth just came out. I tried ignoring it but if they were t goin to like it. Who would.
So a few days in I was talking with @FryingBaconStudio about honest feedback and finally decided I am going to have it all the way through development, not just at the near end. And so far it seems to be paying off.
However for actually beta testing for bugs and such, that gets done at the end using testflight with a group of ,
5 close people, 5 friends, 5 strangers, and 2 GS forums users.
That way I have larger range of feedback to go from.
Bit long but hope it helps or gives insight
Elfizm