作者：Matthew Burns

我已经开始逐一测试《Kick The Kitties》的16个正在制作中的关卡了。我知道测试是一件单调乏味的事，但也可以变得有趣，毕竟它是开发好游戏的必要环节。

去年开发《Goats R Delicious》时，我创建了一个简单的测试系统，似乎非常有效。在正文开始以前，我得强调一下，我测试的是一款iOS游戏，我使用TestFlight在合适的手机设备上展开测试。

如果关卡还在开发中，我通常从最新的关卡开始测试到第一关。一旦所有关卡完工，拿到最新版本，我就会从游戏的开头开始测试。记住，在通过TestFlight安装游戏的最新版本以前，你要重启手机设备。

testflight(from theverge.com)

当与程序员沟通时，我的经验告诉我，务必保持清楚简洁（至少我是尽量这么做的）。即使你自己就是程序员，你也不会记得所有情形，所以你会希望有一个容易解释的标准格式。

我使用我的iPad做一般测试，因为它能很容易地捕捉图像并存入相册中，以下是我的做法：

1、我玩了整个关卡（我可能挂了好几次），截下出错的、重要的、有疑问的或可改进的场景的图片。

2、完成关卡后，我打开保存图片的相册。

3、每张图片做一个Email，发送给程序员。

4、每封Email都要写明主题、TestFlight的版本、关卡和案例。比如从“Version #56, Level 8 p.3”中，我可以知道这是第8个关卡的第56层的第3张图片。发发送的所有邮件都要保存成文件。

5、最后，每封Email必须加上对图片的解释，因为有时候从图片上看不太问题。

对于实际测试，我的建议是：

1、测试所有墙面或边界，以保证角色不会穿到可操作区域之外。看到自己的角色掉进坑里或卡在缝隙之间是非常令人扫兴的，玩家会注意到。

2、在所有你设计让角色死亡的地方都死亡，确保死亡顺序和画面的一致性。

3、如果你的角色可以跳跃，那么就要在每个地方都跳一跳！否则你永远不会知道可能撞上什么东西。

4、行走或奔跑在任何可通过的表面。没有什么比角色突然掉进坑里更糟糕的事了。

5、保证刷出点能持续刷出。

6、站在所有可操作物品的前面或后面。

7、保证没有任何计划外的死角成为玩家的意外避免所。

8、保证生命值、得分、道具收集等的运算正确。

9、杀死游戏中的所有“对手”，保证所有“对手”的功能正确。

10、毁坏所有按照设计可以毁坏的“道具”，保证所有“道具”的功能正确。

11、使用所用“增益道具”，保证所有“增益道具”功能正确。

12、如果可能，用不同的方式玩同一个关卡6-8次。毕竟每个人通关的方式都不一样。

13、保证音乐循环正确。

14、最后通盘测试UI。

我知道你们还能想到更多测试点，但愿我涵盖了几个基本点。

记住，记忆性玩游戏是测试的大敌，所以你要努力保证每一次玩的方式都与上一次稍有不同。（本文为游戏邦/gamerboom.com编译，拒绝任何不保留版权的转载，如需转载请联系：游戏邦）

How We Test Our iOS Games

by Matthew Burns

Ah yes, I have started to test ‘Kick The Kitties’ as each of its sixteen levels are being hammered out. I know testing can be tedious, but it can be fun and more importantly it is essential to development of a great game. Essential!

I established a simple testing system when developing ‘Goats R Delicious’ last year and it seems to be very effective. Before I continue, remember this is an iOS game and I am utilizing TestFlight on the appropriate mobile devices.

If levels are in the process of being developed, I always start with the latest level and then work my way down to the very beginning of the game. Once all levels are built, upon receiving the latest version, I start from the very beginning of the game. Remember, before installing the latest build via TestFlight, restart your mobile device.

It has been my experience to be clear and concise when communicating with your programmer (or at least I try). Even if you are the programmer, you will not remember every situation and will appreciate a standard format that is easy to decipher.

I use my iPad to do the mundane testing because of its interactive ease in capturing images and placing them in your gallery. This is what I do:

I play the entire level (I probably die several times) and take images of situations were errors, concerns, questions or suggestions appear.

Upon completing a level, I enter my gallery where these images are located.

Each image becomes the basis of one email which is to be sent to the programmer (or self).

Each email has the following in the subject header; TestFlight Versions #, Level # and a number or letter so one can keep track of the many emails from a particular level. For example, “Version #56, Level 8 p.3″ tells me this is the third image from my walk through the eight level on the 56th build upload. Everything I send has to be documented.

Finally, each email has to have a comment about the image because things are just not always obvious.

Here is some advise I have about actual testing:

Test every wall section or boundary to make sure you character cannot penetrate anywhere outside of game play. Having your character falling into the “blue” or being “stuck” can be demoralizing and players will notice!

Die on every spot where you have designated the character’s possible death and make sure the dying sequence and images are consistent. You do not want your images to bleed.

If you character can jump, jump everywhere! You never know where a hidden collider is.

Walk or run on every surface available. There is nothing worse than having your character fall through the floor and into the “blue.”

Make sure your spawning points are spawning consistently.

Stand in front of or behind every object/item available.

Make sure there are not any unplanned “dead” areas that give the players unintended refuge.

Are the mathematics behind health, score, item collections and et cetera working properly?

Kill every “opponent” you have placed in your game. Verify that every “opponent” functions correctly.

Destroy every “item” you have designed as destructible. Verify that every “item” functions correctly.

Use every “facilitating object.” Verify that every “facilitating object” functions correctly.

If possible, do numbers 6 thru 8 in a different order or created other possible progression situations within a level. Not everybody plays a level the same way you do.

Make sure your music is looping correctly.

Finally test your UI extensively.

I know many of you could add things to the list, but hopefully I covered the basics.

Remember, game play memorization is your enemy and therefore try and approach every new upload a little differently than the previous one. Best of luck!(source:gamasutra)