Thread: SDLC process

Hi all,


Am 1.4 yrs experience in software testing..ve come across interviews asking if a bug fix sent to you from a developer reported by some other tester so how do you go about & u don t have a clue about the bug.i was really confused with this..can someone help me out

Hi,

Yes it is a bit confusing to retest bug fixes for bugs logged in by other testers. But it is not really a difficult task incase navigational flow / steps of Bug detection is proper.

• To start off, identify the module under which the bug was logged. Isolate all testcases that pertain to the specified functionality.

• Once this is done, verify the defect reproduction steps. Navigate as per the steps documented and see if you are still able to reproduce the bug. Incase the fix is successful you should see results as per Expected results.

• Once you have verified the bug fix, execute the associated testcase to ensure no regression defects / bugs have resulted as a result of the bug fix

This process should be a good startoff to test bug fixes for bugs logged by other testers.

Cheers....
Bizzzzzare

It's a pain to test bugs reported by others but a bug report and the associated test case helps a lot.

If you have been allocated to retest the bug identified by some others and fixed by developers, then below are some of the steps which will help you:

1. Read the entire Bug notes carefully, which will be logged by the tester when the bug is originally identified and also the developer will mention the action he has done to fix the bug. (Not, the code he has written to fix, but what he has fixed)

2. Read the requirement documents or use cases concerned with the module

3. After reading the bug notes, you are not able to come to a conclusion check with the developer what he had done to fix the bug

4. Check with the Business Analyst who is the point of contact for the module.

5. Still you are not able to getting clear idea on the bug then escalate to your team leader or Manager, regarding the complexity of the bug.

Well, Its not so hard,

If you receive an Bug to re-test which was raised by another tester, Just refer to the notes the tester has written when he reported bug to Developer and before re-testing refer to notes the developer has sent you, If you are using Quality center all the comments are mentioned in the defect log, The Best source for history of that particular bug, If you still un clear what to do refer to Test case or ask the team lead for guidance.

All the best
Ritz

Originally Posted by Rashmachittiappa

Hi all,


Am 1.4 yrs experience in software testing..ve come across interviews asking if a bug fix sent to you from a developer reported by some other tester so how do you go about & u don t have a clue about the bug.i was really confused with this..can someone help me out

Hi Rashmachittiappa,
This is rao from delhi . when ever bug is fixed from developer side he definetly write his/ her comments about the bug & and next the bug is fixed means that bug has definetly unique Bug-Id must be exist. so analyse the history of the bug by using this id .wheater any snap shot s are attached or any application releated information is noted in the bug description. A bug is fired means bug must have Subject and description and all details of that bug so it s useful for you retest the application efficitively.
i think this answer is sufficient if any else let me know thx..