Answered Questions

  • Conflict with Developer

    On what issues will a user have conflict with a developer?

    Star Read Best Answer

    Editorial / Best Answer

    kurtz182  

    • Member Since Nov-2009 | Nov 10th, 2009


    Conflicts with developers arise from the lack of patience and empathy; when a tester and developer forget that they are ultimately striving to reach the same goal. 

    Conflicts generally arise through lack of misunderstanding due to miscommunication.  In my organization, this typically occurs when a developer closes a defect stating that it can't be reproduced.  If this situation is not handled carefully, it can lead to conflict.  


    Conflict initiators are:
    1)  Tester did not provide a clear and/or accurate description of the defect.  For example, the tester may report the error name or text and the developer might be looking for an error number. 

    2)  Tester did not provide a thorough description of the defect.  For example, tester may not mention that the defect was found in a particular test environment and the developer assumed it was caused in a different one.

    3)  Developer misinterprets the defect even though it was authored accurately, clearly and thoroughly.  Devs aren't perfect.  Under time constraints to reach milestones, they sometimes overlook key points in defect reports and end up closing bugs that should get fixed. 

    Conflict negators are:
    1)  Establish a standard defect reporting process and get Test and Development to fully understand and adopt it. 

    2) Empathy: Understand that everyone is under pressure to meet deadlines and we are all on the same team to reach a common goal.

    3) Patience: Understand that nobody's perfect.

    Aadit

    • Sep 20th, 2012

    Tester - developer conflict occur when developer say "could not see the reported bug". This could happen when Testers test environment differ from developrs or when the bug is not reproducible, occuri...