Testing design--continuing

  Hi,all:I still have two points with testing design to talk.One is use existing case to cultivate case.The other is reuse cases in different products.Let's beginning.

  For the first point,its meaning is that after we finished the designing of test case,maybe we also can find some valuable points.In other words,maybe they are happened suddenly or when we are testing there is some exception out of our mind.These are worthing reproduce them.So we must  very careful and thinking from the end user whether they'll encounter these questions.This point is very important.As when design test cases,we depend on the customer requirement,in short,the function point.However,the important thing is maybe we'll in front of some questions out of our mind.At that point,we need tester to develop some free tests.I think it is like using product infinitely to assure there isn't bug the end user will front.Maybe we can't find all errors as it's economic issue,but we can do our best.  

  For the other view,it is different with the repetition of cases. Obviously,its meaning is we can use some cases in other products.But as you know,every product has their personel characteristic.For example,for a same function,maybe this product implement in this way,but other product carry out in other way.This is common.Although we can avoid these problems base on two principles. Firstly,we should avoid design specific case.That isn't equivalent with we aren't advocate write every step.I think that is necessary.It's good for us to find every exception and adapt a new system.Actually,I gain lots of good thing from that kind of cases.However,in the other aspect,it is decrease the rate of reuse.Due to some different nameof function,we may have to redesign or modify some cases.I believe that is a waste on human resource and time.Secondly,we should reduce the coverage of a single test case.If we cover many points,maybe it make us find more questions in one case.On certain extent,as it include many points we can't guarantee that every point can be used in other products. Additional,we should aim at the function,but not the spcial product.It is undoubte we can't make every cases be reused.That need team has uniform request.There are two ways.Either base on if the function is pass or depend on the test case.The former is if the core function pass,we consider this case pass although the description maybe different with the description of product.But we also need update case.The later is most simple and straight.If there is any different,we determine the case fail.But this way can't show the real quality of the product exactly.

  Summary above points,I also face on my job.Like cultivate case.When i implement spec,we find some exceptions happened.It is valuable to record and reproduce.I hold that is the reason why tester must keen and careful about any exception.On another aspect,these are base on experiences.Thus,I also need study and accumulate lots of things,like when we suffer one error how senior tester treat it.This must good for my job.I claim that both conclusion and recollect are good methods for imporve myself.And also,search for some language is also beneficial.