问题描述
开发iPhone / iPad时
When developing for iPhone/iPad do you
- 进行单元/集成/等测试？
- 你使用什么框架？
- 你尝试了哪些其他框架（如果你决定不使用它们，为什么不呢？）
注意这是基于（此后经过大量编辑）。问题产生了一些有趣的回答，可能有助于聚合在一个地方。
NOTE This is based on a question asked a few days ago (that has since been heavily edited). Question generated some interesting responses that may be useful to aggregate in one place.
推荐答案
这是我目前在测试之前的测试方法app。
Here is my current approach to testing before shipping an app.
1）使用Xcode集成的Clang分析器进行构建和分析。
1) Build and analyze using the Xcode integrated Clang analyzer.
这在许多方面都很有用，它会捕获许多小蠢事和一些内存泄漏（即使有时其结果包含误报）。
This is helpful in many ways, it catches many little stupid things and also some memory leaks (even though sometimes its results contain false positives).
2）彻底检查所有警告。其中一些可能实际上是非常有害的。尽可能删除警告。
2) Check thoroughly all of the warnings. Some of them may actually be really harmful. Remove the warnings where possible.
3）使用Instruments检查内存泄漏，运行时的内存占用等。
3) Use Instruments to check for memory leaks, memory footprint at runtime, etc.
4）当我认为需要时，使用Shark识别性能问题。
4) Use Shark to identify performance problems when I feel it is needed.
5）执行（手动）所有预定义的测试系列，以检查UI和底层代码都按预期工作。在向应用添加新功能时，请务必再次进行回归测试，以确保一切顺利，正常运行。由于设置和运行它们所需的时间难以置信，我很久以前就放弃了单元测试。
5) Execute (manually) all of a predefined series of tests, to check that both the UI and the underlying code works as expected. When adding new functionalities to an app, always do regression tests again to ensure everything runs smoothly and properly. I have discarded unit tests a long time ago, due to the unbelievable amount of time needed to setup and run them.
6）将应用程序的临时版本发送给alpha测试人员，报告正确的错误，然后再将应用程序发送给alpha和beta测试人员并更正报告的错误。
6) Ship an ad hoc version of the app to alpha testers, correct bugs reported, then ship the app again to both alpha and beta testers and correct bugs reported.
7）最终测试是在iPhone 3GS，iPhone 3G和iPod Touch的不同设备上亲自完成的。
7) Final test done personally on different devices, at the moment iPhone 3GS, iPhone 3G and iPod Touch.
这篇关于您测试iPhone / iPad应用程序的方法是什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！