Lesson 6 Bug & Bug reports
Bug reportcorrect answersA bug report is a specific report that outlines information
about what is wrong and needs fixing with software or on a website. The report lists
reasons, or seen errors, to point out exactly what is viewed as wrong, and also includes
a request and/or details for how to address each issue
Rules to write a bug reportcorrect answers1. One bug per report
2. Where were you in the software when the bug occurred? Include the URL of the page
where the bug is located if it's a web application.
3.
Severitycorrect answersBug severity is the extent of the impact a particular defect has
on the software under test. The higher effect this defect has on the overall functionality
or performance, the higher the severity level is.
Prioritycorrect answersBug priority is a way to decide in what order the defects will be
fixed. The higher the priority is, the sooner a development team is going to look into the
problem. Very often, bug priority is determined by its severity. Well, it is reasonable to
start fixing with blockers rather than minor defects.
Bug life cyclecorrect answersNew - Assigned - Open - Fixed - Retest - Reopened -
Verified - Closed
What status can be assigned after developer opens a bug reportcorrect
answersDuplicate — the identical problem was already reported. Rejected — the bug is
not reproducible; a developer can't understand the problem due to the ambiguous
wording; there are no clear requirements; a QA engineer misunderstood the
requirements; improper environment configuration during testing, etc. Deferred — the
issue is not urgent and can be fixed later. Not a bug — the problem does not affect
software functionality (e.g., a suggestion to change a font or background color). Cannot
be fixed — for some reason, this bug has to become a feature, as there is no way to fix
it (for now or at all). Need more info — a developer needs extra information about the
defect to find its root cause.
Bug reportcorrect answersA bug report is a specific report that outlines information
about what is wrong and needs fixing with software or on a website. The report lists
reasons, or seen errors, to point out exactly what is viewed as wrong, and also includes
a request and/or details for how to address each issue
Rules to write a bug reportcorrect answers1. One bug per report
2. Where were you in the software when the bug occurred? Include the URL of the page
where the bug is located if it's a web application.
3.
Severitycorrect answersBug severity is the extent of the impact a particular defect has
on the software under test. The higher effect this defect has on the overall functionality
or performance, the higher the severity level is.
Prioritycorrect answersBug priority is a way to decide in what order the defects will be
fixed. The higher the priority is, the sooner a development team is going to look into the
problem. Very often, bug priority is determined by its severity. Well, it is reasonable to
start fixing with blockers rather than minor defects.
Bug life cyclecorrect answersNew - Assigned - Open - Fixed - Retest - Reopened -
Verified - Closed
What status can be assigned after developer opens a bug reportcorrect
answersDuplicate — the identical problem was already reported. Rejected — the bug is
not reproducible; a developer can't understand the problem due to the ambiguous
wording; there are no clear requirements; a QA engineer misunderstood the
requirements; improper environment configuration during testing, etc. Deferred — the
issue is not urgent and can be fixed later. Not a bug — the problem does not affect
software functionality (e.g., a suggestion to change a font or background color). Cannot
be fixed — for some reason, this bug has to become a feature, as there is no way to fix
it (for now or at all). Need more info — a developer needs extra information about the
defect to find its root cause.
