mfsi_chinmayb

 Profile Answers by mfsi_chinmayb Questions by mfsi_chinmayb

• Apr 27th, 2012

 

According to my experience the most challenging situation with developers is when the bugs you have produced are not producible over their environment . The It will be difficult to covey the exact bug . It becomes more difficult when the T and D are in different geographical region . But you can overcome this by right way of communication .
Sometime you will find a mismatch between T and D when the priority and severity of the Bug comes into account . But it can also be resolver with proper guidance .

The second question is completely context dependent. You cant say by looking at the % of completion .
The factors which comes into account
>Priority of the project .
>Weather you have good masters in Proj-A or Proj-B . Then you can go for Experience based testing , Agile testing on those to save time .
>Sometime Relationship with your client .
>Company policies .

dave3940

 Profile Answers by dave3940 

• Aug 6th, 2014

 

The most challenging situation I have with developers is when I report, what i believe, is a bug, and the developer responds that it is "functioning as designed". Until the software is released, the QA Engineer is the representative of the customer/user. Regardless of what the requirements and specifications say or dont say, if i strongly believe that most users would consider a certain action/response to be a bug, then I have to convince the developers that it is a bug.