Answer / nag

Resolution Type:
After receiving defect report from testing team, the
responsible development people are conducting review meeting
and sending resolution type to the responsible testing team.
There are 12 types of resolutions, they are

1. Enhancement: The reported defect is rejected, because
this defect related to future requirements of the customer.

2. Duplicate: The reported defect is rejected, because this
defect raised due to limitations of hardware devices.

3. Hardware Limitations: The reported defect is rejected,
because this defect raised due to limitations of hardware
devices.

4. Software Limitations: The reported defect is rejected,
because this defect is raised due to limitations Software
Technologies (Ms-Access).

5. Not Applicable: The reported defect is rejected because
these defects have improper meaning.

6. Functions as Designed: The reported defect is rejected,
because the coding is correct w.r.p.t design documents.

7. Need More Information: The reported defect is not
accepted / not rejected but the developers are requiring
more information about the defect to understand.

8. Not Re-producible: The reported defect is not accepted &
not rejected, but the developers are requiring correct
procedure to reproduce that defect.

9. No Plan To Fix It: The reported defect is not accepted &
not rejected, but the development people are requiring some
extra time.

10. Open: The reported defect is accepted & the development
people are ready to resolve through changes in coding.

11. Deferred: The reported defect is accepted, but postponed
to future release, due to low severity & low priority.

12. User Direction: The reported defect is accepted, but
developers are providing some valid information about that
defect to customer site people, through our application
build screens.

Defect Tracking Procedure

Large Scale Organizations

1 to 5 --- (Defect reporting)
6 to 10--- (Resolution Type)



Test Manager Project Manager


Test Lead Team Lead


Test Engineer Programmer


Small / Medium Scale Organizations

1 to 4 -------- (Defect Reporting)
5 to 8 -------- (Resolution Type)


P.M


Test Lead Team Lead


Test Engineer Programmer












Bug Life Cycle / Defect Life Cycle

New



Deferred

Open Reject




Closed Re-open


New Open Closed

New Open Reopen Closed

New Reject Closed

New Reject Reopen Closed

New Deferred

Answer / nag

Through Mail or

Defect Tracking Procedure

Large Scale Organizations

1 to 5 --- (Defect reporting)
6 to 10--- (Resolution Type)



Test Manager Project Manager


Test Lead Team Lead


Test Engineer Programmer


Small / Medium Scale Organizations

1 to 4 -------- (Defect Reporting)
5 to 8 -------- (Resolution Type)


P.M


Test Lead Team Lead


Test Engineer Programmer

Answer / jmaes

Hi Nag,
What is 5 ----8, 6--10.Can you please explain

Answer / harry

I dont mind writing the same what I wrote to many people.
That educate yourself NAG.

Please understand that REPORT means you are sending a
summarised information on the bugs. What you have written
above is the definition of different status'es set in the
bug when its logged, or being reviewed by the Change
control board committee etc..

Mostly we send the reports by mail or we upload them at
common shared location etc. But whats most important is you
need to provide that what tool is used for preparing the
defect report? and what contents are there in the defect
report?

generally, rather mostly microsoft Excel tool is used for
generating the defect report. MS word is also used for this
purpose.
The contents of the defect report would carry summarised
information in tabular format with various columns and
rows. The report would be of following kind:
1. Defect found to fixed ratio report
2. Weekly or Buildwise logged bugs report (with newly open,
closed, fixed awaiting test, re-opened)
3. Tester bug report
4. Defects found by Engineering to Testing ratio report.

Columns/rows in these reports would be carrying information
of Status'es, priority, severity, author, Fixed on
Version/Build, Invalid bugs etc..

All these reports could be summarised in separate excel
documents or in one excel document with several sheets or
also can be composed in MS word with the heading Post
Mortem Defect report at the completion of testing.

Answer / mudaseer

we use a tool called bugzilla or bugzero or any other tool.we fill the attributes of the bug like severity,bug number,status,os,assigned to,environment,test data etc if you want to want to know more download bugzilla or bugzero

How is your project connected to the Database...tell the procedure??

2 Answers   SuperValu,

It is not waste of time in preparing the test condition,testcase and testscript

1 Answers  

Test cases for Chat Component

1 Answers   Infospectrum,

why you want 2 join Testing ?

4 Answers   BMC,

can any one tell me wat is dependent and independent scripting?

0 Answers   Cap Gemini,

What is Reliability Testing

3 Answers   FactSet Systems, Genpact,

What metrics will be collected during the Testing i.e from requirement Phase to Maintainance Phase

1 Answers  

what is deferred in defect life cycle

10 Answers   Accenture,

What is the difference between the dropdown and checkbox list??

5 Answers  

Tell me the test cases for the Bank Check?

2 Answers   Cognizant, JPMorgan Chase,

TestCase for White Paper?

5 Answers  

How to explian the V model. Diagram not required but iwant the answer gnerally No Diagram explanation plzzzzzzzzzz..

2 Answers   Accenture, TCS,