The sentiment for write spec.

  I spent several days to write some specs.Although there are some existed specs I can refer,it is really difficult to cover almost instances.I wonderful use different path to test different function.In this way,we have no neccessary to execute all paths use each role.Some function is duplicated,we can use crossing testing.That means use one role to implemented one function,use the other role to run the other path.In this way,we can implement same function use different role and different method.I believe that this way can cover most circses to test if there is no error occur.That can test what the system have done and what have not been done sufficiently.As you know,as a freshman,thinking all instances clearly,it's still have a difficult,although I'm familiar wiht the system.It is easy to mistake which spec is use first path and which is use another path.Then I talk with my colleague,he gave me a nice suggestiong.That is write the description clearly and understanding.Actually,in lots of document,we always saw how to design a test case.That also emphasize the importance of writing description,it is same with developer write understanding code.All these are supply a convenient way to us and other people.As you know,following with the growing of system,maintaince is more important.That need we have a clear enough document to record our spec and other thing.In this way,we can handle some urgent things as soon as possible.I'll remember this point,I claim that it will have more help for my coming work.