Is in-depth game testing something the community is willing to help with, or is that something that should be handled on the developer’s side? [import]uid: 89724 topic_id: 17159 reply_id: 317159[/import]
If you were a proper Game Development Studio, you would have your own QA department that would provide a thorough testing and might also have a focus group and specialised testing from users.
The community *might* be able to help you with some testing, but generally that is *supposed* to be the developers responsibility.
cheers,
?
[import]uid: 3826 topic_id: 17159 reply_id: 64569[/import]
You can normally get a handful of people to BETA test for you and if you’re also testing carefully yourself, this should be adequate.
Part of being a community is checking out each others apps
Peach
[import]uid: 52491 topic_id: 17159 reply_id: 64576[/import]
Thanks guys.
I don’t ask this because I’m lazy. I test each feature I add at least twice. I ask this because I’m biased. I know how to play, and I rarely change my play style. I’m worried there’ll be some glitch I’ll miss because I’ll never think to try the weird stuff the players might try.
Right now, though, I’m worried my game is too hard on normal mode. I have adjustable difficulty built in, but I’d rather not slow it all down, since the hectic pace of the game is one of the most entertaining features, in my opinion. [import]uid: 89724 topic_id: 17159 reply_id: 64597[/import]
I understand what you are saying and No, you are no lazy, I dunno if this has happened with you as yet or not, like in the old days there was something called Phosphor Burn, the screen would retain the image of a static screen, that’s why they invented the screen savers to save the screen from Phosphor burns.
Similar to that sometimes when you start developing, you can *See* the code in your head, no matter what you are seeing in front of you, you kind of become blind to the code and start using the cached copies in your brain. In cases like it is always best for someone with a new fresh point of view to come in and have a look. They do not have the phosphor burn wrt this code.
It is always better to have ß testers, so put your app out of Test Flight and let a series of developer have a look and give you feedback.
cheers,
? [import]uid: 3826 topic_id: 17159 reply_id: 64599[/import]
I completely understand what you’re saying. I don’t even notice it most of the time. When I’m testing, I see a situation, and I react how I am supposed to react according to the code, not according to my own common sense.
Thanks for telling me about testflight. I’ll definitely look into using that. The app itself isn’t nearly done yet, though, shouldn’t I wait for a semi-finalized product? [import]uid: 89724 topic_id: 17159 reply_id: 64601[/import]
Code testing/functional testing I’d do by yourself. However, play testing - definitely get other people involved! I have app-testing parties with a few trusted friends (bribed with beer and pizza) who I just ask to play. I then see how they interact with the game and what they seem confused/frustrated by.
I can’t stress how important it is to play test. I had the same situation that I had coded the game, so I knew what the game was expecting. Gave it to my friends, and quickly realized just how insane my interface was. It made sense to me, but realized I could code the interface to just use one tap versus three. Also, added indicators or other visual stylings for when I want people to drag things versus tap/touch things.
My $0.02.
Thy [import]uid: 42145 topic_id: 17159 reply_id: 64615[/import]
i test your game if you test mine;) Thats a deal. [import]uid: 86417 topic_id: 17159 reply_id: 64622[/import]