Sentiment for write test spec.

  Last week,I finally finish writing some test specs.Although there are some existed specs in our system,our intent this time is optimize them.So it is still a little difficult for me as a freshman.From my side,as you know,I want to write it as well as possible.After all,this is my first time to write spec.Actually there is not only design them,but also maintain them in the future.That would convenient for our future work.

  After finishing it,I have some notions on designing test case.As well known,this part is the most important and difficult part in testing work.Actually,that is the fact.When I wrote them,I always want to write a test case can cover different pathes.I ignore the balance of the accessibility for a test case and the number of steps of it totally.And on the other hand,when i use different pathes,I claim that use different method to design them,like cause-effect gragh,equivalence partitioning and boundary-value analysis.At last,I'm puzzled with which spec is test with which method.I'm not quite sure when I should use equivalence partitioning and when I should use boundary-value,or sometime we can use them together.Actually I think for a textbox this two methods are necessary.For example,for a textbox,its range is from 0-1.Using the equivalence partitioning method,our test data should any number smaller than 0,bigger than 1,and valid value.For boundary-value,We can use 0.001,-0.001,0.9999,and 1.0001,I think.Certainly,we also should consider the instance with letters.And should we write all circuses in one spec or derive them base on the class of value--number or letters.I hold that it will be better in the future.

  Summary for this experience,at next time,I should attention following points.First,make a table or gragh for each function and each path.Designing specs base on the each path,like have a framework first.Then,secondly,add methods to each path,and write down which method use in which path.In this way,I'll keep a clearly thinking for it and it's also convenience for maintain.At last,prepare the test data for each spec.

  Ok,these are some my ideas for this experience,welcom any comments.Thanks!