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

Explain me software life cycle and SDLC

3 Answers  

Hi, this is sekhar yadav, who is given the seviarity and who is given the priarity

8 Answers   CTS,

which certification we have to complete first? ISTQB or CSTE? in ISTQB which level i have to choose? Foundation level or advanced level? Can any one tell what will be the syllabus and how tough it will be? pls anyone share the experience

4 Answers  

whar are the contents in db testing test case template

0 Answers   Reliance,

Why we give test deliverable to client ? or what is the purpose & necessary for giving test deliverable to client ?

1 Answers   Wincor Nixdorf,

Hi i am srinivas working as testing engineer with one of cmm level3 company. i am looking to change for that i posted my resume in naukri i got mails about requirement but when i replyed mails no one call for interview .I applied from past 4 month but i am not geting any interview call . please tell me where is the problem.

2 Answers  

List out the test matrix

1 Answers  

difference between load testing and stress testing?

4 Answers  

when to start and stop testing?

2 Answers  

Hallow friends, I have put more than 80 questions in QTP sub-category that were asked many reputed companies so that if you know the answers please post answers thank you, padmasekharpediredla

1 Answers   AppLabs, Apps Lab, HVL, IBM, Infosys,

with out any training on domain with out any document only with the help of build screen is it possible to write testcases

5 Answers   Ariba,

How do you go about testing a project?

0 Answers