Vinaykumar2882

 Profile Answers by Vinaykumar2882 

• Jan 3rd, 2009

 

When we say the Defect Retest, that means the there has been some change done to the code and the bug is fixed.

Due to this change, it is possible it might have triggered some other functionality to disfunction. That means it might create another bug.

So it is neccessary to test all the functionality related to that Defect which was fixed.

smita_jain78

 Profile Answers by smita_jain78 

• Jan 22nd, 2009

 

To ensure that the issue is fixed properly and the fix has not created some other issues in the related functionality.

vk1978

 Profile Answers by vk1978 Questions by vk1978

• Mar 23rd, 2009

 

Defect will rectified by the developer and change its status to Fixed, but its tester duty to make sure that the application is a quality one, so for the sake he will retest  with the help of Steps to reproduce to check whether the defect is really fixed and on conformation tester will change the status to CLOSED as tester only has the right to close the defect. 

Tru123

 Profile Answers by Tru123 

• Mar 24th, 2009

 

Once the bug is fixed, it is very important to ensure the other part of system haven't disturb or their might change to disturb other functionality therefore retesting is very very important after fixing bug then after bug can be CLOSED by tester

santosh_marne

 Profile Answers by santosh_marne 

• Apr 24th, 2009

 

This is to ensure that the existing functionality is not damaged while fixing the problem/ defect.

This is quite important B'coz developer might not have the impact of other modules while fixing defect for one module. and we never know where & what is the impact of it so it is must to test the existing functionality of the application.

If is it a risk to test the while application then atleast test the main basic flows of each functionality End to End.

Thnx ..Santosh

slagjana.milkovska

 Profile Answers by slagjana.milkovska 

• May 20th, 2009

 

First: Reporting the bug (with appropriate Severity, Priority and Reasons), After that the Defect have a proposed status.
The development are fixed this defect and it become Resolved.
QA team Retested this defect and on the end it become Closed.

mathan_vel

 Profile Answers by mathan_vel Questions by mathan_vel

• May 26th, 2009

 

After Bug fix, the same or different kind of bug may or may not come. So it must be retested with the help of executing the same test cases with different Test Data.

rajmohan23

 Profile Answers by rajmohan23 Questions by rajmohan23

• Aug 25th, 2009

 

               To check whether the defect attains the state fixed and the rectified defect cause any impact on non defective part.this is the main reason to to do the defect retest.

update me if im incorrect

rahulskin

 Profile Answers by rahulskin 

• Sep 10th, 2009

 

It is important to retest a defect after it has been reported closed from the development.  It is testers responcibility to regress the defect, also tester has to test around the functionality for any new defects occured due to the closure of the defect. 

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 21st, 2009

 

It is very important to re-test a defect once its been fixed. 

When a defect is fixed, it is sent back to the tester.  The 'Defect Status' is changed to 'Fixed' and the 'Assigned to' status is changed to the tester's name.  The tester can quickly determine which defects to re-text by querying the defect management database with Defect Status = 'Fixed' and Assigned To = tester's name.  This should display all of the bugs that are fixed and assigned to the tester. 

Once you find defects to re-test, do the following for each issue you re-test:

1) Ensure the environment is set up as described in the defect report

2) Ensure you follow all of the test steps precisely

3) Make sure you understand the differences between expected and actual results

4) If the results satisfy requirements and the problem is resolved, then add your remarks and change the bug status to 'Closed'.

5) If the problem persists, then add your remarks entering any new information that can help the developer resolve the issue and reassign the defect back to the developer.

Swapnil

• Dec 16th, 2011

 

Defect retesting is important, because it is closed from the dev team. but somebody has to approve it that it is really been fixed. On the other hand it is very important to do the regression of it, because it might have created some side effects. :)

mfsi_chinmayb

 Profile Answers by mfsi_chinmayb Questions by mfsi_chinmayb

• Dec 23rd, 2011

 

Hi
The development team fixes the defect raised by the Tester. The the status for that defect will be closed . But the tester need to test it again to confirm that the defect has bee fixed and their is no side effect of that to any other part of that system. The above process can be termed as Defect retesting.