今天有时间把Creative的测试流程总结一下,其中有些观点只是个人观点,仅供参考.((不知道测试流程是不是属于公司内部机密,这样做是否会违背当时的保密协议).

1.PM or PE submits MRD(Marketing Requirement Document)

MRD is just like the System Requirement Specification.In Creative ,the whole project is controled by PM(Project Manager),and there is no "real" SQA guy,although they call the testing department as "Software Quality Assurence".

In this stage ,the PM will conduct a meeting and inform the related guys to attend it ,like TestLeads,some testers,s/w lead and developers.

Note: in this stage ,the testers need not to view or review the MRD becasuse it is not necessary to find bugs in MRD.Only  PM has right to modify it .What the testers must do is to read the MRD and know what we would test in the future.

2.Product Kick Off  

In Creative ,the "product kick off " means that a project really begins.

3.Create schedule.(Develop)

It is created by PM completely .Test department has no responsibility to participate

in it. What we can do is waiting and to wait the schedule is completed.

4.Submit TestPlan

SQA leader creates testpaln according to the schedule.

5.Create test cases

Because the limitation of the product ,the test cases can be reusable completely.

For example:the function of the audio cards is almost the same although defferent modle.

6.Test cases view and review

This stage is to assure the test cases are suitable for the product.

7.Assign resources and test cases to testers.

8.Alpha and Beta stage

 Pre-test-->pass-->testing-->log bugs-->bug review-->next stage(Alpha 2)

9.RC stage (There is  no fatal bugs)

 bug fix is complete

10.RTM(Release to manufacture)

In this stage,the code should be frozen.

以上是我自己的总结可能与实际工作还有些差异.可以看出来其实在创新测试人员唯一做的就是测试,在其他的流程上测试人员没有必要去参加,完全是由PM控制.

以下是我感觉流程方面的缺点:

1.测试部门是流程中的最低层人员,他们所做的就是测试再测试.没有参与到需求分析当中去,甚至造成测试人员在产品的最后阶段还 弄不清楚产品的性能.

2.需求文档描述不清楚,仅仅简单的描述客户以及产品的性质.

4.没有风险评估的意识.甚至在产品的最后阶段还要增加一些影响很大的模块.