What should we do when we find an issue

   Maybe you'll think this is an strange question,including me.However,actually,it appear in real work.Always,as tester,when we find issue,we should ask developer to confirm if it an error or it is generated by other issue.After that,we accept the reason of it,we can decide whether open a bug for that question.In fact,there are lots of realistic questions are puzzling me.

  If we front of an issue,should we open a bug directly or ask developer to affirm if it is a question firstly.Opening it directly,if the issue has opened,that must will increase the workload in virtually.Additional,this is not good for team,especially for outsourcing project.Maybe customer consider the efficiency of team is low,and it is short of good processing managment.Furthermore,it must waste our time on several same issues.But,on the other hand,in this way,tester can concentrate on finding more bugs before release.It is good for guaranteeing the quality of project to customer.It's really paradoxical.Asking developer to confirm,as you know,they always busy on coding or modifing code.They will focus on those big issue naturally,but for those minor or trivial issue,maybe they will ignore or missing to correct.So,what will happen?The small issue cannot be settled for a long time,maybe they will be delayed still next release,even if cutomer discover this question before release,I believe that we don't want to see this instance.On the other side,I hold that if we always ask developer to decide if it's a question,for a long run,we cannot judge independently what kind of question is critical and which can be correct easily.For developer,they have them difficulties.Base on processing,they need run design review,code review with everybody in same group,even for a trivial issue.Although,I acknowledge,that processing is very important for develping software.Hence,maybe they don't like modify them.Additional,those small questions are easily ignored when they engaged critical issue.

  Base on those reasons,what should we do for indermination issue and trivial issue as a tester?For the former question,when we open a bug,we should pay more attention on its quality.The issue may block other function of project.Take an example,a sell system,it can't record which commodity is sold,or the record is displayed,but the number is incorrect,or something like that.They impact the main function of project.These errors must a big question.At this time,we should open it directly and immediately.For the later one,we can open the small one with the big issue together.As developer modify the big one,they can modify in company with the small one.Hopefully,it is a good way to settle this question.
 
  In my mind,that isn't handle it entirly.We still very depend on developer to modify the error.If they doesn't correct them in time,we cann't begin test.We still wait and wait until the question settled.This situation will leave less and less time to test.In this way,how can we gurantee the quality of project?As you know,in a short time,we should test all bugs,run regression testing,and test base on use case,furthermore free testing base on ourself.I hold that we need some technology knowledge for analysing the extent scope of question,although maybe it can't help us much.About the trivial issue,I don't think it is a good way to settle the question,but,actually,we aren't find a better method to instead it.As there are too contradiction factors that impact the two sides.We still need put more effort on this question.