关于Test Plan

1. Testing shouldbe optimized to find important problems fast, rather than attempting to find all problems with equal urgency.(给予我的经验教训就是不要着急full sweep的测试，先smoke test，然后new feature test（focus on改变的部分），然后important feature testing,最后是function sweep testing。)

 

2.Test strategy should focus most effort on areas of potential technical risk, while still

Putting some effort into low risk areas just in case the risk analysis is wrong.

（之前做过一个项目，因为develop team没有怎么做过REGUID，开发和QA没有沟通好，应该把build兼容测试作为重点进行测试，但是test plan放到了较后，review test plan, PM等也没有提出啥异议，造成项目进行了一段时间，发现了严重的兼容问题，导致很多rework的工作，造成项目延后)

  

3.Test strategy should address test platform. configuration, how the product will be operated, how the product will be observed, and how observations will be used to

Evaluate the product.（就我公司而言，这些信息是PM和客户去沟通确认需求，归档到PRD中，QA按照PRD的需求制定计划。一般这些信息不是很明确，就要QA提出，以免资源浪费或是测试不够）

 

4.Test strategy should be diversified in terms of test techniques and perspectives. Methods of evaluating test coverage should take into account multiple dimensions of coverage,including structural, functional, data, platform, operations, and requirements.（制定测试计划要考虑如何在有限资源的情况下cover更多）

 

No single test technique can reveal all important problems in a linear fashion. We can never know for sure if we have found all the problems that matter.Diversification minimizes the risk that the test strategy will be blind to certain kinds of problems.

 

5.The test strategy should specify how test data will be designed and generated.

It is common for the test strategy to be organized around functionality or code, leaving it to the testers to concoct test data on the fly. (对我公司而言就是测试素材的制作，对于多媒体软件而言，测试素材多而广，有good和bad两种素材，bad素材测试软件的容错性等，这还涉及到素材的管理和更新的问题)

 

6.Not all testing should be pre-specified in detail. The test strategy should incorporate

reasonable variation and make use of the testers’ ability to use situational reasoning to

focuse on important, but unanticipated problems.（要来考虑exploratory和ad hoc testing的时间）

 

7.It is important to test against implied requirements—the full extent of what the

requirements mean, not just what they say.（在制定test plan之前，要和项目相关人员一起review requirements,模糊的问题提早明确）

Heuristic Basis for heuristic

8.The test project should promote collaboration with all other functions of the

project, especially developers, technical support, and technical writing. Whenever

possible, testers should also collaborate with actual customers and users, in order to better

understand their requirements.（项目组各个team的合作很重要,信息的共享与传递更重要,定期的项目会议也许是个比较有效的办法）

 

9.The test project should consult with development to help them build a more testable product.

（什么是testable，Wiki的定义是It means it can be tested, but it also can be proven wrong later.In engineering this refers to the capability of an equipment or system to be tested.） 

10.A test plan should highlight the non-routine, project-specific aspects of the test strategy and test project.（我也在想尽量做到test plan不是个没有内容的的毫无价值文档）

 

11.The test project should use humans for what humans do well and use automation forwhat automation does well. Manual testing should allow for improvisation and on thespot critical thinking, while automated testing should be used for tests that requirehigh repeatability, high speed, and no judgment. （对我而言是欠缺对自动测试的考虑和计划）

 

12.The test schedule should be represented and justified in such a way as to highlight anydependencies on the progress of development, the testability of the product, time required to report problems, and the project team’s assessment of risk.(做好estimation非常重要)

 

13.The test process should be kept off of the critical path to the extent possible. This canbe done by testing in parallel with development work, and finding problems worth fixing faster than the developers fix them.（测试应该尽早进入到项目中工作，critical Path：在一个项目工程中,需要时间最长的路径。这条路径上的工作必须尽可能快地完成,因为它决定完成总任务的时间,即完成该项目总共需要的时间不可能少于沿着关键路径去做所需要的时间）

 euristic Basis for heuristic

14.The feedback loop between testers and developers should be as tight as possible.

Test cycles should be designed to provide rapid feedback to developers about recent

additions and changes they have made before a full regression test is commenced.（定期developer和tester项目会议的召开；测试进展，BUG提交情况信息及时发送给develop team；强制开发fix bug的时候反馈tester详尽的信息，更改的components，risk，如果能有建议如何regression bug那更好）

 

15.The test project should employ channels of information about quality other than formal testing in order to help evaluate and adjust the test project. Examples of these channels are inspections, field testing, or informal testing by people outside of the test team.（尽量多渠道测试产品，这个可能会受客观环境所限）

 

16.All documentation related to the test strategy, including test cases and procedures,should be undergo review by someone other than the person who wrote them. The reviewprocess used should be commensurate with the criticality of the document. （Test plan和test case review，尽量得到别人的建议和反馈）