Testing process--some document in our testing process.

  Last time,we stop at testing should contain smothly process and strictly regulation.Hence,we should use some frame to control our process well.For example,we should desigh test case in order to test primary function firstly.So,we should build model and make every member follow it.As you know,different people have different point view for same question.In the same meaning,different people have different view for the priority of facotor in the test spec.You think the description is more important,other consider precondition is crucial.And,which should we use for our team?If any one use their own spec.It is undoubt that this is really inconvenience to manage our document.Certainly,there has lots of document need to set down uniform model.Now let's introduce them one by one.

  We can classify two kind of thing related with testing process--Input factor and output factor.For the first one,include test spec,testing assignment;For the second,contain test result,issue report,log,test report for one module,the result of modified issue.Let's beginning from test spec.

  Except I said above,test spec should simple,understand easily,and have well-proportioned coverage.We should base on requirement tracking matrix to design test spec.In each spec,we should have unique form to write our spec.There must include some factors that must be write down,like spec name,priority,depends on,traceability,precondition,description,writen by(this will convenience for team to follow in case requirement changed),view(positive or negative) or something like that.After requirement is settled down.Test team should decide what factor should be displayed in this system.And,for every step,it should include action,input value and expected result.After designing test spec,writer should hold review meeting which should invite developer and analysisor attend.(This has been talked in the former archive).

  For testing assignment report,it is used to inform every person what should they do,when they should do,the request of different work.Manager should assign exhaustive work to everyone before each testing cycle through effiency communicate mechanism.It should be better to use testing task to everyone.I think this also need a module,at least,it should include tested by,time spend(this will good for after work,like automatically testing),module,full request.In this way,I hold that anyone can understand what should they do,even a freshman in our system.