Defect Tracking

Defect Tracking & Correction
1.    The main steps in defect resolution are Prioritization, Scheduling, Fixing, Reporting

a) True
b) False

2.    The scheduling of fixes should be based primarily on…

a) Defect counts
b) the overall project schedule
c) defect priority

3.    Fixing a defect involves

a) The developers making and unit testing the fix
b) QA retesting the fix and validating it
c) regression testing surrounding the fix
d) QA reviewing scripts, test data, etc to see if updates need to be made
e) all of the above

4.    Which of the following are ways to use the defect log to drive process improvement?

a) Go back to the process which originated the defect and find out what caused it
go back to the validation steps in that phase and find out why it wasn’t caught earlier
b) think about what other kinds of things might have been missed, given that this bug “snuck through”
c) look at the fix history of the bug to find out if it could have been handled more
d) all of the above

5.    The minimum requirements for a defect management process include all but which of these?

a) Defect to risk mapping
b) defect prevention measures
c) defect discovery, naming, and resolution
d) process improvement
e) deliverable baselining

6.    Reducing the impact of a risk, should it occur, is an effective way to minimize risk.

a) True
b) False

7.    Who should be involved in prioritizing fixes for valid defects found during system testing?

a) QA
b) the users
c) the project team
d) Developers

8.    Which of the following techniques is not a common way to minimize expected risks?

a) Training and Education (both the workforce and the customers)
b) ranking risks using Pareto voting
c) Defensive Code
d) Defensive Design
e) Quality Assurance, Methodology and Standards

9.    Which is cheaper, preventing defects or fixing them?

a) Preventing
b) fixing

10.    Deliverable baselining is:

a) baselining at the end of each phase and keeping change control processes in place
b) not counting defects caught and fixed before your phase.
c) identifying key variables and defining standards for each
d) A and C only
e) A, B, and C

11.    Which of these is not a “best practice” for defect managment?

a) Automate the capture and analysis of information wherever possible
b) strive to correct every reported defect before release
c) make defect management a risk-driven process
d) prevent defects or at least contain them within the phase they were discovered
e) use defect measurement to improve development

12.    Which of these is not a valid purpose for reporting defects?

a) to correct the defect
b) to report the status of the application
c) to gather statistics to help develop expectations on future projects
d) to improve the development process
e) to show test coverage

13.    A defect is “discovered” when

a) Development acknowledges a reported defect
b) none of the above
c) a tester observes a failure
d) development begins to work a reported defect
e) a tester reports a defect

14.    ALE stands for

a) Annual Loss Expectation – a formula for judging risk
b) Acceptance Level Error – an error that was not caught until user acceptance testing
c) Audit Legal Effort – the amount of time billed to the project by the legal and audit staff
d) Assertion Loop Estimation – a measure of code complexity

15.    Which of these refers to the “cost” of the risk?

a) Priority
b) severity

16.    When reporting a defect it is important to…

a) Make sure it is reproducible, if possible
b) get it to the developer’s attention promptly
c) attempt to analyze the cause of hte defect
d) B and C only
e) A, B, and C

17.    To estimate a risk’s expected impact, you should…

a) Estimate the expected frequency of the event and the amount of loss that would happen each time
b) try to put a dollar amount on it
c) confer with experts on the probability and severity of the risk
d) a and b only
e) all of the above

18.    Along with a short title for the defect and what phase it was found in, what other data should be part of the defect’s “name”

a) Priority, like Urgent, High, Medium, Low
b) severity, like Critical, High, Medium, Low
c) steps to reproduce the error
d) data used to reproduce the error
e) categorization, like Missing, Inaccurate, Incomplete, Inconsistent