Anand

• Jun 3rd, 2006

 

Hi

there is no need to take much process in this. if bug  is found, confirm the bug, take screen shot, explain what to do to get the bug, describe path and send to a copy to developer and P M informing that a bug report has been sent.

BISWAJIT PANI

• Jun 14th, 2006

 

NEW means when a tester will find a defect he/she will mark it as only NEW as this defect has found now and he/she will send it to T.L and D.L

ASSIGN means after getting a Bug from testing Engineer ( which is marked as NEW ) the D.L will verify it whether it is proper to Fix or not. if after verify all the criteria the D.L has agreed to accept that bug for fixing then he will "ASSIGN" that to the bug related Developer.

This is the difference Between NEW and ASSIGN

Regards,

Biswajit Pani (09986183456)

panibiswajit@yahoo.com

sireesha

• Jun 27th, 2006

 

Hi,

For your query answer depends upon the process you follow in your company.

Whenever a new bug you find then change status as new.

2. Send it to PL, he verifies that if it is reasonable then he changes as open or else he can reject that or else he can postpone that bug to next release as deferred.

3. If he changes as open, sends it to developer then he works on it changes status as fixed.

4. Tester checks that if he/she not getting any problem then he closes that or else reopens that bug.

bharathp

 Profile Answers by bharathp 

• Jul 18th, 2006

 

when ever we found the Bug the status Of the Bug will be New

 

Then we will report this new bug to the test lead by giving description,summary, screenshots, steps to reproduce the bug ,and also we will give seviority to the bug

Then the team will give priority to the bug as per the priority they will assign the bug to the Development team

 

Bharath.P

seeethapathik

 Profile Answers by seeethapathik 

• Jul 8th, 2009

 

Tester finds a bug at 1st time, he will put status as NEW and it'll be sent to Test Lead with proper description, Steps, Inputs and Screen shots. He/She will verify wherther is it a Valid / Invalid bug. If its a valid bug, then TL will send it to Dev Lead. DL also will verify once himself. if its a valid bug then DL will put a status as ASSIGNED TO to a Developer to fix a bug. (Mostly he 'll assign a dev who develpoed that madule).  Assigned dev will do code changes to fix a bug. Once he fixed that bug, He'll put a status as FIXED and ill be sent to DL. he ill send it to TL with status PENDING TO RETEST. TL will send it to tester and Tester will do retest/reggression test. Once that bug has really fixed and he gets a expected result then he'll put a status as Test Completed. Then TL will put a status as CLOSED.

If TestLead / DevLead finds that is a invalid Bug, @that instance it'll be rejected with their comments regarding why they rejected.

Hope i have given a brief desc about bug life cycle.

-Seethapathi.K