Testing process--some document in testing 2.

  It's undoubt that test result is important for our job.However,many people doesn't like to fill it in,even hate.As you know,except test manager,few people see it.Hence,as time passes,they doesn't like this course.Actually,the signification of it isn't like this.It should reflect the quanlity of our production quantificationally in a well-proportioned test spec coverage.Additional,we can estimate the current of our product base on the rate of passed spec within same intensity in different testing cycle.Certainly,passes rate is not only parameter to measure test spec.

  As well know,"pass","fail" and "untested"."pass" isn't meaning that there is no error,function can work,deeply it stand for the design is same with the requirement of customer.Hence,meanwhile,except error,"fail" also represent the function isn't same with requirement.All these need developer to modify.In a way,for another meaning of fail is worse.As,it is illuminate that analysis between developer and requirement analysisor is not good.This will waste more time and resource.Last,there is third situation--untested.This have lots of different reason,like the environment of testing have not been built well,no test data,or function have not been developed.In this case,these specs should be marked "untested".They should be followed in the future.   

  And the rate of each result is important for our work.The rate of fail can tell us the modified current for defect.If the rate of untested is too high,it demonstrate that the preparation for testing is not enough.That must lead to wasting our resource.To reduce this rate,testing team should institute pertinent process to track those untestable spec.For those untestable spec in a long time,tester should discuss and decide if they should be deleted;For those in short time,we should build corresponding test condition,in order to repair this leak.I think this is also one job in our testing process,like developer produce software,modify it.