The way to describe bug.

   As you know,whatever developer or tester,all of them can open a issue for a bug.Certainly we should describe the bug,how it produced,what is the environment and something like that.

  But there is an interesting thing,I think.As the aspect of developer and tester is different.For testers,we always write down the reproduce steps,how it occur and what is the expected result and what is the actaul result clearly.I think we describe the phenomena as best as we can.For the sake of developer can understand what is the wrong.But,for developers,I think the way isn't very well.They always state what is wrong only,but they don't describe what is right.Maybe you think that doesn't matter.Suppose,when testers specify this issue.They just see the wrong describe,if they aren't confirm with requiement analysis(RA) or developer,they may consider the describtion should be the right situation possibly.So when other test it,they discover the result is reverse or wrong.If the tester think for a moment,they confirm with who write the spec or steps.And finding the real instance,that would be the best situation because the question can be handled earlier.But we should think the worst situation,right?The tester weren't ask developer or RA.They add the failed comment directly.What the terrible result!After developer see the result,they may rush to tester and shout "the error is modified,you see,how you test".I think this situation is bad.We don't want to occur this and see it.Firsly,they really waste our time.Then,It hurts our good relationship.So,I think,we should find some ways to avoid that occur.

  For testers,I think we should confirm with developers or RAs what is the real situation about that question,if the issue is reported by developer and they aren't write down the expected result.Then we can write steps easily and is convenient for who test it.In this way,we can save some time,right.For developers,I think they'd better write down the actual result,Of course,there are issues difficult for write,just do them best,that's enough!Or could we set down some regulation for some question.Like an old chinese idom,No reuglation,no circle and sqare.(I think we can say it like that,.If you know the right statment,please leave your words,tks a lot!).Maybe you would say we have meeting for feature review,for change request review.But do you think if the question is left for that time,it's a bit little late!Maybe at that moment,all of people will much tired.

  Above these are my own thinking.Are you have some different voice?Agree or disagree?I'm very please can share with your suggestion.Please leave your words,maybe we can discuss for them. Thank you!