| || |
User Praveen (firstname.lastname@example.org) posted:
I apologise for the date in my earlier transmission. In the defect log
template that we have is having the following fields:
and then the defect close, and closed date.
My question is that in a development project who and at what stage one fill
in these columns. Who has got the authority to close a defect.
Thanks in anticipation.
Re: QA Question
User (MMcNaughton@STSSystems.com) posted:
I'm not quite sure what Disposed means, although i'm assuming it means
Our simplified state transition goes
From 'Open' by QA person to 'Fixed' or 'Deferred' or 'Require Info' by some
development person as defined.
If 'Fixed' State, then the defect gets assigned back to the QA person who
originally opened the defect into the State of 'Pending Validation'. At
this point the defect is validated and either 'Rejected' back to development
If 'Deferred' (ie. to be revisited) and QA person is agreable it can be
deferred then it will stay in that state until it can be Opened.
The only experience i've had dictated that only QA closed defects, thus
ensuring that the issue either no longer remains or shall never be fixed.
If it's impossible for a QA person to validate the defect (might be a
developers defect), then QA person ensures that proper fix information
exists and closes it.
Hope this helps,
Re: QA Question
User Tim Gerrells (email@example.com) posted:
Concur with Max:
1. Don't know what you're using the "disposed by" for.
2. Typically, QA verifies a defect has been fixed; usually the QA that
entered it in the first place (of the QA who first validated the behavior
really is a bug, if a customer or other individual external to the
development project submitted the bug report).
3. Normally, only a QA person will close a defect.
We're talking your company's development business rules here. The tool or
database should directly support how your company is set up to function.
I have worked for one firm where there was a very robust release management
organization (because the product had to support over 17 platforms), and
once QA verified a bug fix, the release manager would handle all the CM
tasks and once that was in hand and the fixed code successfully worked in
every supported platform (documented, patched, yada, yada), he would "close"