Balance between coverage more function and clear spec.

  As you know,we always found that maybe some customer requirements are influence one function or one place.So how about our test spec should like,should we cover all function in one spec,or write one spec for one function.It's undoubt,that,for the first way,there must have lots of steps to execute and lots of point need our attention.This would puzzle tester,especially  a freshman,as you know,spec with many step can make person feel boring and bother.Additional,this maybe result in missing point,even missing the best time to modify the defect.For the second condition,that would be better for tester.That would be execute easily.And each spec is simple and clearly,we have a low rate to missing function.But,in some extent,these specs are short of continuity.And maybe tester to write spec will pay lots of energy to write duplicated step.Tester maybe can't have a whole conception for whole workflow.

  From developer view,they always develop every function step by step,and commit code everyday.Maybe one of functions can work well today,and next tomorrow.In this way,wrirte spec separately for different function is better,even it's a workflow.But,sometime,as well known,requirement always been updated.How about this situation?Certainly,we still can modify our test spec as soon as possible to according with latest requirement.But,actully,this is a little possible to do this work before release.If we can't delete original spec in time,that would lead to strong puzzle for tester,especially for those who haven't familiar with our system.In this way,it'll waste lots of time and energy both who write spec and who execute them,I think.

  It is seem that each way has its reason.So how we can balance this conflict.Maybe we can just execute those specs for new functions.However,I don't think that this way is good method to settle essential question.Balance spec step and spec coverage,update specs is not easy.In ideality,it's always come forth in some testing BBS or other place,we should control step less than 10,and we should update test spec in good time.I found that this is difficult to implement,especially in one release,different requirement will be brought forward fore and aft.Hence,foregoing spec is possible useless.But write all function together will produce more steps.Let's experience in our work together.