It Depends Deciding on the Correct Ratio of Developers to Testers

这是又一篇介绍开发人员和测试人员比例的文章，与上一篇文章阐述的观点是相似的。强调了这个比例是由项目的具体情况而定.”it depends”项目的情况，制定的schedule,公司的文化，产品的期望质量（the quality expectations for the product）…..

测试也是对风险的管理，这些风险包括没有满足客户的需求，也包括测试不充分而不能评估产品的状态。当你向你的上级提出“my testing staff can’t keep up with development. I need more testers. I need some kind of standers to justify my claim”. 那么就要先分析你所做项目的情况，要考虑以下几个方面：

1.       产品因素（需求，产品大小，复杂程度）

2.       项目及其流程（公司是如何开展项目活动，客户对缺陷的容忍程度以及延期的看法）（customer’s tolerance for defects and ship delays）

3.       人的因素（开发和测试人员的能力和责任心的问题）

然后作者根据三个因素列举了项目的实例说明如何去定义测试人员和开发人员的比例问题。

产品因素:larger system? Complex, real-time system? No well-defined API? Data-dependent GUI? Fit un-architected features into the existing product?

项目因素：define and inspect requirements ? Define and inspect the product architecture? Design each component and inspect the design? Developers test code before each build? Plan testing at a sufficiently low enough level(when to do exploratory testing, if and when to automate, what to test under which conditions)? Have a test-infrastructure for easy test development? Review open defects in a cross-functional team to assess impact? Daily build and smoke test? Low customer tolerance for ship delay? Low tolerance for customer reported defects?

人的因素：(the more capable your developers, the fewer testers you need. The more capable your testers, the fewer testers you need. If you hire developers who don’t test their work, or if you hire all one kind of tester, and they can’t test the product in depth, you will need more testers.)

 Developers experience with this kind of the product? General development team experience(able to perform inspections, able to understand designs)? Tester experience with this kind of product? General test team experience(able to perform inspections, able to understand designs, able to perform a large range of testing, including exploratory and automated testing)?