3 thoughts on “The trap of not asking questions”

  1. There are some projects wherein I have experienced that the developers dont like to answer questions as they are very busy and sometimes they do not know the complete functionality, Also there’s no proper documentation and the users are not available. This puts a fear in the minds of testers, and they start testing based on certain assumptions which may not be right.
    Developing a relationship with the developers is one way to do it but how do you deal with developers who keep complaining on your back once you ask questions?

  2. This is a social problem, not a testing problem.

    If your job is to test, and you need information, and someone who has it won’t give it to you, then go to your boss about it. Escalate.

    However, you also need to learn to ask questions politely and effectively.

    And, you should know a variety of ways to get the information you need.

  3. >> There are some projects wherein I have experienced that the developers dont like to answer questions as they are very busy and sometimes they do not know the complete functionality,

    * Get to know what they know.
    * Get to know who know the complete functionality.
    * Alert the stakeholders who matter (the one who gave the task) about this inconsistency and risk.
    * State and highlight your assumptions.
    * Get your assumptions clarified from the stakeholders and negotiate the mission.

    Also there’s no proper documentation and the users are not available.
    * This can be expected in many projects. You are not alone.

    This puts a fear in the minds of testers, and they start testing based on certain assumptions which may not be right.
    * Get to know the inconsistencies early in the project. Be someone who helps the project move forward.
    * Let (the right) people know how you are feeling and how this might affect the project.

    Developing a relationship with the developers is one way to do it but how do you deal with developers who keep complaining on your back once you ask questions?
    * Help them to help you. Do they like most of the issues to be found early?
    * Do they want less bugs opened on their name?
    * Do they want the severity to be reduced?
    * Do they want devices and machines which only you have access to?

    Help them, make sure they feel that you are helping their code look beautiful.
    Once you gain their trust and prove your credibility, your inputs will be appreciated.

    Your final goal must be to help the project move forward than to be popular among the developers.

Leave a Reply

Your email address will not be published.