• Home
  • venkatesh.thangaraj Answers

Answered Questions

  • Dec 11 2009
    10:24 AM
    4075
    21

    Exploratory Testing
    • mathan_vel

    Where does Exploratory Testing Fit? What are the Pros and Cons in Exploratory Testing?

    yuganr

    • Jan 6th, 2011

    Exploratory testing comes in picture due to lack of documentation. When there is no availability of documentation then testing team depends on similar project browsing, contacts with customer site pe...

  • Nov 03 2009
    10:29 AM
    6351
    16

    How will you find the bugs if the application is partially running?
    • geetsjoe

    Star Read Best Answer

    Editorial / Best Answer

    kurtz182  

    • Member Since Nov-2009 | Dec 11th, 2009

    Generally, when an application is partially running, it is no longer in a stable state suitable for testing.  Reboot your system (or reinstall a clean image of the build) and attempt to reproduce the issue, paying particular attention to the steps required to get there. Document your findings in a defect report.  Don't forget to include screen shot(s). If error messages are returned by the application during failure, include this in your report.

    If you want to determine the source of the existing defect, then check the Error Logs on the local and/or serving computers.  The error messages in these logs will often describe the nature and source of the problem. Testers can set the Event Filter of this log if they know the event type or session they wish to examine.  Event Details provides an exception stack trace that can be included in the defect report.



    Nicolaas

    • Jan 15th, 2012

    I have a problem with the question though - Define "partially running". 1) Why would you waste time on testing & troubleshooting something that did not meet the Test Entry Criteria? 2) If the tester ...

  • Mar 20 2009
    11:04 AM
    4187
    27

    Mis-Communication in Bug
    • mathan_vel

    What will you (Tester) do if there is miscommunication in bugs, Every cycle is Ignored from developer side and Re-Opened from tester Side?

    Star Read Best Answer

    Editorial / Best Answer

    kurtz182  

    • Member Since Nov-2009 | Dec 6th, 2009

    In every test cycle, the defect is consistently 'Ignored' by the developer and 'Re-Opened' by the tester.  This problem exists due to a miscommunication somewhere.  What will you do as a tester to rectify this issue?

    1) I would first make sure that I have entered accurate and thorough details in the defect report in order for the developer to reproduce the issue. I would include details about the test environment so the developer can duplicate it.  I would also include screen shots to prove the defect does indeed exist. 

    If the developer 'Ignores' this, then s/he obviously believes there is no defect at all and that the application's functionality is working precisely as it is supposed to.
     

    2) Next, I would cite the requirement in the defect report and describe my interpretation of it.  Then I would describe how the existing functionality does not meet the intended requirement.

    If the developer 'Ignores' this as well, then I begin to consider whether I have misinterpreted the requirement. It is possible that the developer is correct.

    3) I would revisit and study the requirement to determine whether I misunderstood it when creating my test case(s).  If necessary, I would meet with the Business Analyst to gain further understanding about the requirement.  I would discuss my test case and the defect with the Business Analyst to determine whether my understanding and approach is correct.
     
    If my research convinces me that I have fully understood the requirement and that my test case accurately and thoroughly tests it, then I would meet with the developer and discuss the results of my investigation with him/her.  I would explain the requirement in the manner intended by the Business Analyst.  I would reproduce

    the issue in an attempt to prove how the defect fails to satisfy the requirement.  Hopefully, the developer will be encouraged to fix the defect.

    If the developer continues to 'Ignore' this issue, then I will get the Business Analyst involved.

    4) I would set up a meeting with the developer, Business Analyst, and myself in attendance.  I would encourage the Business Analyst to explain the requirement to the developer and explain how the test case and its results properly exercise the requirement and identify a failure. 

    If the developer still 'ignores' this issue, perhaps it is time to replace the developer!

    folasade

    • Feb 18th, 2010

    If a developer is fixing bugs with their own ideas and schedule in mind that means he is not following the test cases, he changing the status to IGNORED, then it is an error on the part of the develop...